Date: Mon, 1 May 2006 19:25:07 -0400 From: "Sean Bryant" <bryants@gmail.com> To: "Mikhail Teterin" <mi+mx@aldan.algebra.com> Cc: stable@freebsd.org, current@freebsd.org Subject: Re: cc can't build 32-bit executables on amd64 Message-ID: <f6791cc60605011625k45ea0d7fwddc7f4780014e429@mail.gmail.com> In-Reply-To: <200605011900.22011.mi%2Bmx@aldan.algebra.com> References: <200605011604.26507.mi%2Bmx@aldan.algebra.com> <200605011739.02920.mi%2Bmx@aldan.algebra.com> <445691FE.6000608@alumni.rice.edu> <200605011900.22011.mi%2Bmx@aldan.algebra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Then why not work on adding the functionality? I'm sure freebsd people would love to have a proper working 32 bit compatibility layer happening. On 5/1/06, Mikhail Teterin <mi+mx@aldan.algebra.com> wrote: > понеділок 01 травень 2006 18:55, Jonathan Noack написав: > > Did you miss the previous reply which mentioned using '-B/usr/lib32 > > -B/usr/local/lib32' in addition to '-m32'? > > I did not miss this work-around. But it is not a proper way -- one need not > specify -B/usr/lib in the 64-bit case. Nor should one need to > specify -B/usr/lib32, when using the -m32 flag. > > The gcc's multilib.h functionality is just for that. We just aren't using it > (although we do for for aout) -- presumably, because there *was* a much > bigger fish to fry to enable such compiles... > > -mi > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- Sean Bryant
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f6791cc60605011625k45ea0d7fwddc7f4780014e429>