Possible bug with cross compiling (i386 on amd64 host).

[Guido Falsi]

On Thu, Oct 21, 2010 at 12:08:52AM -0400, Joe Marcus Clarke wrote:
> On 10/20/10 7:44 PM, Tom Judge wrote:
> > 
> > Joe, Ade,
> > 
> > 
> > Sorry my last reply was a little bit blunt.
> > 
> > I was just a little frustrated by the way things panned out in this thread.
> > 
> > What I am really interested in is some feedback on the implications of
> > the work around that I am using here.
> > 
> > I will start a new thread in the next few days with the results of my build.
> 
> Our responses were not trying to deter you.  They were simply statements
> of fact.  I am very much interested in documentation people may produce
> about making this work.  I would happily put it on the TB website.

Hi.

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.

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

Apart from these I just forced the architecture to i386 when making
the jail.

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.

-- 
Guido Falsi <mad at madpilot.net>