public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas Drueke <tdrueke@gmx.net>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gentoo-embedded@lists.gentoo.org
Subject: [Resolved]: Re: [gentoo-embedded] crossdev problem
Date: Sat, 15 Oct 2011 10:16:16 +0200	[thread overview]
Message-ID: <4E994150.6090403@gmx.net> (raw)
In-Reply-To: <201110131914.21368.vapier@gentoo.org>

Hi Mike,

Thanks for looking into this.
I hadn't much time to investigate this recently but found the issue today.

The problem was that a symlink for /usr was created which caused
some trouble. After moving this to a separate partition and mounting
during boot
crossdev works again (among other things).

Currently the latest versions of gcc,binutils,glibc and kernel are used.
These are the same ones on the host system.

Thomas

On 10/14/11 01:14, Mike Frysinger wrote:
> On Saturday 10 September 2011 12:01:10 Thomas Drueke wrote:
>> I haven't found a log showing the outcome of the compilation making the
>> available information
>> restricted somehow.
> it's farily simple code.  if your gcc can't build this:
>     int foo(int *i) {
>         static __thread int j = 0;
>         return *i ? j : *i;
>     }
>
> it is broken
>
>> then stated the versions of the host system on the command line:
>>
>>     crossdev -t armv7a-softfloat-linux-gnueabi --g 4.4.5 --l 2.12.2 --k
>> 2.6.39 --b 2.21.1
> what version of gcc was actually used ?  the versions you give to crossdev 
> merely say "these are the latest i want to use".  if they aren't available, 
> portage will use whatever is available which is often times older than 
> requested.
> -mike




      reply	other threads:[~2011-10-15  8:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-10 16:01 [gentoo-embedded] crossdev problem Thomas Drueke
2011-10-13 23:14 ` Mike Frysinger
2011-10-15  8:16   ` Thomas Drueke [this message]

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=4E994150.6090403@gmx.net \
    --to=tdrueke@gmx.net \
    --cc=gentoo-embedded@lists.gentoo.org \
    --cc=vapier@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