public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Vergien <daniel.vergien@rrz.uni-hamburg.de>
To: gentoo-embedded@lists.gentoo.org
Subject: [gentoo-embedded] Problems using crossdev
Date: Wed, 31 Mar 2010 14:32:43 +0200	[thread overview]
Message-ID: <4BB340EB.6050906@rrz.uni-hamburg.de> (raw)

Hi list,

I just try to use sys-devel/crossdev. I follow the embedded handbook 
(http://www.gentoo.org/proj/en/base/embedded/handbook/index.xml)

I've created a toolchain with:

crossdev -t i686-pc-linux-uclibc

Using the i686-pc-linux-uclibc-gcc also worked like in the handbook.

As the next step I wanted to get the cross-emerge like in section 3.

I've set:
CBUILD=i686-pc-linux-gnu
CHOST=i686-pc-linux-uclibc
SYSROOT=/usr/i686-pc-linux-uclibc
ROOT=$SYSROOT
PORTAGE_CONFIGROOT=$SYSROOT

and added sys-devel/crossdev ~* to my package.keywords

but "emerge crossdev" fails like this:

gentoo-dev ~ # emerge --verbose --pretend crossdev


!!! /usr/i686-pc-linux-uclibc/etc/make.profile is not a symlink and 
will probably prevent most merges.
!!! It should point into a profile within /usr/portage/profiles/
!!! (You can safely ignore this message when syncing. It's harmless.)


!!! If you have just changed your profile configuration, you should revert
!!! back to the previous configuration. Due to your current profile being
!!! invalid, allowed actions are limited to --help, --info, --sync, and
!!! --version.


Have I done something wrong with the environment settings? Since It's 
not really clear to me if I have to have them all.

Regards

Daniel



             reply	other threads:[~2010-03-31 13:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31 12:32 Daniel Vergien [this message]
2010-03-31 16:28 ` [gentoo-embedded] Problems using crossdev Mirage ha
2010-04-01  6:00   ` Daniel Vergien
2010-04-06  8:04     ` Mirage ha

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=4BB340EB.6050906@rrz.uni-hamburg.de \
    --to=daniel.vergien@rrz.uni-hamburg.de \
    --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