From: solar <solar@gentoo.org>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] crossdev conflict between sys-libs/glibc and cross-arm-unknown-linux-gnueabi/glibc?
Date: Tue, 26 Apr 2011 17:57:49 -0700 [thread overview]
Message-ID: <1303865869.8732.2.camel@here> (raw)
In-Reply-To: <d060c365076c91c0c79d7db2a82ca861@basementcode.com>
On Tue, 2011-04-26 at 14:13 -0500, chris@basementcode.com wrote:
> I installed the following toolchain with crossdev:
> arm-unknown-linux-gnueabi
> which installs glibc into /usr/arm-unknown-linux-gnueabi/ under the
> name cross-arm-unknown-linux-gnueabi/glibc
>
> I then installed udev, which depends on sys-fs/glibc
>
> As far as I know sys-fs/glibc is already installed into SYSROOT, except
> with a different name as mentioned above.
>
> I noted that the two installs of glibc had the same version, so I went
> ahead with the installation anyway. Sure enough portage reported a bunch
> of file collisions.
We disable collision-protect iirc for the wrappers crossdev now
provides.
--
solar <solar@gentoo.org>
Gentoo Linux
next prev parent reply other threads:[~2011-04-27 1:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 19:13 [gentoo-embedded] crossdev conflict between sys-libs/glibc and cross-arm-unknown-linux-gnueabi/glibc? chris
2011-04-27 0:57 ` solar [this message]
2011-04-27 1:07 ` Christopher Harvey
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=1303865869.8732.2.camel@here \
--to=solar@gentoo.org \
--cc=gentoo-embedded@lists.gentoo.org \
/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