Re: [PATCH] Always create lib32 and lib64 symlinks

[Anthony Foiani <anthony dot foiani at gmail dot com>]

On Wed, Sep 29, 2010 at 8:40 AM, Ralf Corsepius <rc040203@freenet.de> wrote:
>
> On 09/29/2010 04:33 PM, Anthony Foiani wrote:
>>
>> Always create lib32 and lib64 symlinks.
>>
>> Since we always remove them without checking CT_HOST, we need to
>> create them without checking CT_HOST either.
>>
> Again, this is all wrong on multi-arch'ed systems (e.g. Fedora).
>
> You must not symlink 32bit libraries to 64bit libraries and vice versa.

Ralf --

This is actually creating a place for the crosstool-NG tools to put
build libraries as they're built; it's not the system libraries
themselves.

And, once again, my build completed with this patch, and it died
without it. Note that these symlinks are deleted without any
conditional in do_finish:

ÂÂÂ # Remove the lib* symlinks, now:
ÂÂÂ # The symlinks are needed only during the build process.
ÂÂÂ # The final gcc will still search those dirs, but will also search
ÂÂÂ # the standard lib/ dirs, so we can get rid of the symlinks
ÂÂÂ for d inÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ \
ÂÂÂÂÂÂÂ "${CT_PREFIX_DIR}"ÂÂÂÂÂÂÂÂÂÂÂÂÂ \
ÂÂÂÂÂÂÂ "${CT_SYSROOT_DIR}"ÂÂÂÂÂÂÂÂÂÂÂÂ \
ÂÂÂÂÂÂÂ "${CT_SYSROOT_DIR}/usr"ÂÂÂÂÂÂÂÂ \
ÂÂÂÂÂÂÂ "${CT_PREFIX_DIR}/${CT_TARGET}" \
ÂÂÂ ; do
ÂÂÂÂÂÂÂ CT_DoExecLog ALL rm -f "${d}/lib32"
ÂÂÂÂÂÂÂ CT_DoExecLog ALL rm -f "${d}/lib64"
ÂÂÂ done

When I tried to use the stock version of crosstool-NG.sh.in, the build
failed at the end because the lib64 directory was created and had
"libiberty.a" within it.

Thanks,
t.

--
For unsubscribe information see http://sourceware.org/lists.html#faq