Possible bug with cross compiling (i386 on amd64 host).
tom at tomjudge.com
Thu Oct 21 11:01:24 EDT 2010
On 10/21/2010 04:34 AM, Guido Falsi wrote:
> I just recently got interested in tinderbox.
> I'm using it at home to build packages for my older, slower computers,
> which are also i386 machines mostly.
> The machine running the builds is an amd64 system, and cross compiling.
My current usage of cross building is also for home systems, and my
personal development systems. I am just setting up a system at work
that I hope will replace 2 aging 5U servers with 1 2U system that can
build packages for all 8 of my production builds.
> I'm writing in this thread to report that, for the package subset I'm
> building here, I have had success in cross compiling.
> I have the folowing lines in the i386 build env:
> export ARCH=i386
> export MACHINE_ARCH=i386
> export UNAME_m=i386
> export UNAME_p=i386
I'm not sure you need the UNAME_[mp] lines as when I chroot into my i386
build and run uname -[mp] I get i386 returned from both.
I once I extract the list of ports I will be building I will ack them
for MACHINE_ARCH to see if that will cause me an issue.
> Apart from these I just forced the architecture to i386 when making
> the jail.
You used -a i386 with createJail correct?
> One thing I have found a little hard to work with was making the ports
> use the dependencies I wanted them to. This is more a ports system
> problem perhaps, but what has been hard is that tinderbox seems to
> define the dependency tree before letting me specify port options.
> Sometimes changing options changes the dependencies.
> This is especially true if one is trying to make packages which honor
> the WITHUT_X11 flag. It required me to add the ports, define options,
> remove them, clean the port_dependencies tables for them and then readd
> them. At this point the correct options where read from the start and
> dependencies where correct and not pulling in libX11 or the like.
> This is not a critique, just something I observed and which, perhaps,
> could be improved.
> If any other information is needed feel free to ask.
More information about the tinderbox-list