[haiku-development] Haiku build fails on HAIKU_NO_DOWNLOADS: updated
- From: "Thomas Mueller" <mueller6723@xxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Fri, 08 Aug 2014 02:22:11 +0000
from Ingo Weinhold:
> 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.
Different (quasi-)Unixes have different names for sha1 and related.
Haiku build system assumptions don't fit all.
> 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.
If I try the bootstrap build, I'd use a separate "generated" directory and
would thus not burn my bridges on returning to the regular build.
Documentation with FreeBSD system and ports, and NetBSD system and pkgsrc, is
easier to follow than documentation for building Haiku.
Haikuports, like NetBSD pkgsrc and FreeBSD ports, are recipes rather than
completed packages; source distfiles still have to be downloaded.
I didn't think originally that haikuports were necessary to build the base
system.
Reason for wanting --no-downoads is the flaky internet connection with FreeBSD
on this motherboard. This is also the reason for using NetBSD, where the
Ethernet works consistently.
> 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 try to build for x86_64 and x86; x86_64 does not use legacy gcc. I suppose,
if necessary, I could try to build for x86 with gcc4 only, and if successful,
use that to natively build Haiku x86 with gcc2 and gcc4.
Or of x86_64 build succeeds, use that to build for x86 gcc2-gcc4 hybrid.
> 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.
Relevance of this is to point out the difficulties involved in keeping up with
this emailing list and why formatting could suffer.
Tom
Other related posts:
