Building under mock (rawhide)

[seth vidal]

On Mon, 2010-07-12 at 22:21 +0000, Ben Boeckel wrote:
> In article <1278968533.22421.0.camel at rosebud> you wrote:
> > On Mon, 2010-07-12 at 15:51 -0500, Clark Williams wrote:
> >> I'm thinking we need to catch this early in mock. Any suggestions on
> >> how we should detect that we're on a 32-bit arch and the selected
> >> config is 64 bit? Brute force is just to have a dictionary that rejects
> >> certain configs.
> >> 
> > 
> > The list is the only way I could come up with to determine what could
> > run/build on what.
> > 
> > -sv
> 
> How about an arch-dependent package that contains the 64bit configs?
> mock can then have an x86_64 Requires: on that package. Could probably
> do the same with ppc and other architectures that don't have
> cross-compilers available.

It can't install the pkgs sanely, though - b/c it doesn't know how to
run the arch's pre and post install scripts (from the pkg)

it's not just about compiling - it is also about setting up the chroot.

-sv