[haiku-development] Re: Haiku build fails on HAIKU_NO_DOWNLOADS: updated
- From: Ingo Weinhold <ingo_weinhold@xxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Thu, 07 Aug 2014 12:29:09 +0200
On 07.08.2014 02:25, Thomas Mueller wrote:
2014-08-06 11:43 GMT+02:00 Thomas Mueller <mueller6723@xxxxxxx>:
GeneratedRepositoryPackageList1
/home/nbarlene/haiku/haiku/nbgenerated/objects/haiku/x86_gcc2/packaging/repositories/HaikuPorts-packages
ChecksumFileSHA256
/home/nbarlene/haiku/haiku/nbgenerated/objects/haiku/x86_gcc2/packaging/repositories/HaikuPorts-checksum
DownloadLocatedFile1
/home/nbarlene/haiku/haiku/nbgenerated/download/zlib-1.2.8-4-x86_gcc2.hpkg
--2014-08-05 10:00:59--
http://packages.haiku-os.org/haikuports/master/repo/x86_gcc2/1098775574/packages/zlib-1.2.8-4-x86_gcc2.hpkg
Resolving packages.haiku-os.org (packages.haiku-os.org)...
2a01:4f8:190:64c3:1::1, 78.46.189.219
Connecting to packages.haiku-os.org
(packages.haiku-os.org)|2a01:4f8:190:64c3:1::1|:80... failed: No route to host.
Connecting to packages.haiku-os.org
(packages.haiku-os.org)|78.46.189.219|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2014-08-05 10:01:00 ERROR 404: Not Found.
>From a quick glance, it seems the generated checksum is wrong,
1098775574 should actually be something more like
651cdd6daffc8f85f177a9148a8226eb307a9c0cb5187cfbdd52f76f95988c44
Be sure to check your HOST_SHA256 and HOST_EXTENDED_REGEX_SED
variables to see why it generates such a checksum.
https://github.com/haiku/haiku/blob/master/build/jam/FileRules#L510
I see in nbgenerated/build/BuildConfig
HOST_EXTENDED_REGEX_SED ?= sed -r ;
HOST_SHA256 ?= sha256sum ;
I see in NetBSD-current "man sed" sed -r means extended regular expressions,
same as sed -E .
I could set HOST_SHA256 = cksum -a SHA256 ;
I don't know if it would make any difference.
Please have a look at the ChecksumFileSHA256 actions [1] and verify on
the command line that whatever HOST_EXTENDED_REGEX_SED and HOST_SHA256
values you use actually work in this situation.
Maybe I do better to config --bootstrap ... ?
The bootstrap build is something else entirely. The regular build uses
pre-built packages for a lot of third-party software. The bootstrap
build is meant for ABI compatibility changes, a port to a new hardware
architecture etc., where the pre-built packages don't exist yet. It
cross-compiles a minimal set of packages that is needed to bootstrap the
build of all packages and builds a simplified Haiku image for that purpose.
The whole bootstrap build process is a lot more complex (and less
actively maintained) than the regular build. Given the problems you
already have with the latter, I would recommend to stick with that one
for now.
Generally it is not possible to build Haiku without internet access. The
--no-downloads option doesn't make things magically work without having
to download stuff that is otherwise needed. It was introduced mainly as
a check that the bootstrap build actually doesn't download any pre-built
stuff. However, even in that case the sources for the packages that need
to be cross-compiled still have to be downloaded.
But I could try with what I already have to see if setting HOST_SHA256 makes
any difference.
Another concern is that if I upgrade NetBSD-current, version number will change
from 6.99.44 to 6.99.49 or later version number since the right component of
NetBSD-current version number changes rather frequently though not with every
little change. This number appears in some but not many files:
ls -lR | grep "6.99.44" yields
drwxr-xr-x 3 nbarlene wheel 512 Jul 30 01:57 x86_64-unknown-netbsd6.99.44
/home/nbarlene/haiku/haiku/nbgenerated/cross-tools-x86_gcc2/x86_64-unknown-netbsd6.99.44:
/home/nbarlene/haiku/haiku/nbgenerated/cross-tools-x86_gcc2/x86_64-unknown-netbsd6.99.44/i586-pc-haiku:
/home/nbarlene/haiku/haiku/nbgenerated/cross-tools-x86_gcc2/x86_64-unknown-netbsd6.99.44/i586-pc-haiku/include:
/home/nbarlene/haiku/haiku/nbgenerated/cross-tools-x86_gcc2/x86_64-unknown-netbsd6.99.44/i586-pc-haiku/lib:
You'll have to look at the build system of the legacy gcc, why the
complete version number is included and whether that can/should be
changed. Anyway, I doubt that there are any ill-effects of the version
number being included in these file names.
I am in NetBSD-current with graphic interface (modular-xorg from pkgsrc) not
starting, and no copy-and-paste; using vi with split screen. Quoted-printable
and base64, rendered in Mutt, revert to raw form when using vi.
Please just omit information that is irrelevant. Also, instead of
sending a revised version of an earlier mail, please reply to the
original one and add new information.
CU, Ingo
[1]
http://cgit.haiku-os.org/haiku/tree/build/jam/FileRules?id=4b0b03de1df95f52e1e9e391f45c7f1b42b9ecd8#n508
Other related posts:
