You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As it stands now, it is not possible to build i386 releases or packages on
amd64 farbot build
servers without some tweaking. When using binary releases packages cannot be
built unless
ARCH i386 is set in the release's PackageBuildOptions, and this should be
automatic.
Furthermore it is necessary to symlink /libexec/ld-elf.so to
/libexec/ld-elf32.so in the package
build chroot before farbot chroots there and starts building packages. An
option should be
added to the farbot.conf file to just specify that the architecture of the
release is something other
than what the build server runs to make this happen automatically.
I've not yet tested cross-building a release from source using a different
architecture, but I
suspect that TARGET and TARGET_ARCH will need to be set to i386 for building
the kernel and
world.
Cross compiling for other architectures would be cool, but supporting that I'm
sure will be
harder if possible at all. Plus I don't have any non-i386/amd64 hardware to
test with. For now
let's try just being able to build i386 on amd64.
Original issue reported on code.google.com by [email protected] on 13 Aug 2008 at 1:14
The text was updated successfully, but these errors were encountered:
Also, farbot currently only uses a single tftproot directory, so the boot
loader and kernel will be the same for all
releases. It would be better probably to use a tftproot directory for each
release, or at least each architecture.
This will make it trickier to configure the DHCP server since it will have to
use different root-path and filename
settings for machines with different desired releases, probably requiring an
administrator to put MAC addresses
directly into the DHCP configuration file.
Original issue reported on code.google.com by
[email protected]
on 13 Aug 2008 at 1:14The text was updated successfully, but these errors were encountered: