From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gcc-final: Drop obsolete code for handling lib64
Date: Wed, 28 Aug 2013 13:18:59 +0200 [thread overview]
Message-ID: <20130828131859.7bbd1fd6@skate> (raw)
In-Reply-To: <1377687378-19688-1-git-send-email-markos.chandras@imgtec.com>
Dear Markos Chandras,
On Wed, 28 Aug 2013 11:56:18 +0100, Markos Chandras wrote:
> Since 5628776c4a4d29d0715633ea463b64cc19e19c5a
> "toolchain-external: fix lib64 symlinks"
>
> lib64 is a symlink to lib so there is no reason to copy the libraries
> to lib64 anymore. This fixes multiple building problems
> for buildroot toolchains:
>
> [...]
> mv: 'output/host/usr/mips64-buildroot-linux-uclibc/sysroot/lib64/libuClibc-0.9.33.2.so'
> and 'output/host/usr/mips64-buildroot-linux-uclibc/sysroot/lib/libuClibc-0.9.33.2.so'
> are the same file
> mv: 'output/host/usr/mips64-buildroot-linux-uclibc/sysroot/lib64/libutil-0.9.33.2.so'
> and 'output/host/usr/mips64-buildroot-linux-uclibc/sysroot/lib/libutil-0.9.33.2.so'
> are the same file
> mv: 'output/host/usr/mips64-buildroot-linux-uclibc/sysroot/lib64/libutil.so.0'
> and 'output/host/usr/mips64-buildroot-linux-uclibc/sysroot/lib/libutil.so.0'
> are the same file
> rmdir: failed to remove
> 'output/host/usr/mips64-buildroot-linux-uclibc/sysroot/lib64': Not a directory
> [...]
>
> Signed-off-by: Markos Chandras <markos.chandras@imgtec.com>
Reviewed-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Thanks.
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-08-28 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 10:56 [Buildroot] [PATCH] gcc-final: Drop obsolete code for handling lib64 Markos Chandras
2013-08-28 11:18 ` Thomas Petazzoni [this message]
2013-08-28 14:17 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130828131859.7bbd1fd6@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox