Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 31 Aug 2010 13:49:09 +0400
From:      Anonymous <swell.k@gmail.com>
To:        =?utf-8?Q?Ren=C3=A9?= Ladan <r.c.ladan@gmail.com>
Cc:        stast@bsdportal.ru, freebsd ports <freebsd-ports@freebsd.org>
Subject:   Re: devel/sdl12 and gcc -m32
Message-ID:  <86aao3jene.fsf@gmail.com>
In-Reply-To: <AANLkTi=nAAZFb75O5yOvGmfc=TDR=QvocKrUNyudon0N@mail.gmail.com> (=?utf-8?Q?=22Ren=C3=A9?= Ladan"'s message of "Tue, 31 Aug 2010 11:40:03 %2B0200")
References:  <AANLkTi=TX_=NkGdVVUKhbNg_oV0BaK580A%2Buxua7nj2Z@mail.gmail.com> <86tymbjfen.fsf@gmail.com> <AANLkTi=nAAZFb75O5yOvGmfc=TDR=QvocKrUNyudon0N@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Ren=C3=A9 Ladan <r.c.ladan@gmail.com> writes:

>> -m32 is not supported yet, especially not by the ports tree. And even if
>> you manage to compile sources it wouldn't link against 64bit libs.
>>
> Hmm ok, I'll add a NOT_FOR_ARCH / ONLY_FOR_ARCH to the port.

ONLY_FOR_ARCHS/NOT_FOR_ARCHS set IGNORE, not BROKEN for the port.
IIRC, tinderbox has -trybroken option in order to test whether the ports
is *still* broken or not.

>
>> There is a way to compile 32bit ports on amd64 but it involves either
>> using chroot() or different LOCALBASE.
>
> The wine approach.

Nah, wine is mostly useful for running 32bit apps. And wine64 for
running 64bit apps is still experimental. It's only makes sense for it
to have IGNORE for non-i386 archs.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86aao3jene.fsf>