ARCH in i386 jail
kamikaze at bsdforen.de
Wed Sep 15 18:27:09 EDT 2010
On 11/09/2010 13:47, Dominic Fandrey wrote:
> On 10/09/2010 13:29, Dominic Fandrey wrote:
>> I recognized that ARCH in the i386 jails is set to amd64, which
>> confuses graphics/libGL, because it determines the machine type
>> and assembly code to use from ARCH.
>> The bsd.port.mk states:
>> # ARCH - The architecture of the target machine ...
>> To my understanding it means it /should/ say i386 in an i386 jail
>> and the behaviour of graphics/libGL is correct.
> The most simple solution to this problem, that allows me to build
> libGL and other ports using ARCH, is to remove ARCH from
> scripts/lib/tinderbox.env .
> This way ARCH will be populated by the ports tree, which runs
> "uname -p" inside the jail, which will yield the correct ARCH instead
> of the machine architecture.
An interesting bit of information, I recently had a chat with
someone who just set up a Tinderbox on RELENG_8_1, where my
/solution/ apparently does not work. It seems some COMPAT_FREEBSD32
improvements made it into RELENG_8 in the mean time. He says he
also has to set UNAME_p for his i386 jails to work, so maybe that
should be added to the tinderbox.env file as well.
Is there any way of setting ARCH (and UNAME_p) to the architecture
of the jail?
I tried ^^ARCH^^, which did not work and my perl foo is - well,
there really is no perl foo (shame on me).
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
Q: What is the most annoying thing on usenet and in e-mail?
More information about the tinderbox-list