Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for building i386 releases/packages on amd64 #1

Open
GoogleCodeExporter opened this issue Jun 21, 2015 · 3 comments
Open

Comments

@GoogleCodeExporter
Copy link

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

@GoogleCodeExporter
Copy link
Author

Er, that's /libexec/ld-elf32.so.1 and /libexec/ld-elf.so.1

Original comment by [email protected] on 13 Aug 2008 at 1:20

@GoogleCodeExporter
Copy link
Author

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 comment by [email protected] on 15 Aug 2008 at 8:26

@GoogleCodeExporter
Copy link
Author

Jayme reports that "the tftp boot loader is the i386 version on both i386 and 
amd64"

Original comment by [email protected] on 19 Dec 2008 at 1:18

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant