public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "H Hartley Sweeten" <hartleys@visionengravers.com>
To: <ng@piments.com>
Cc: <crossgcc@sourceware.org>
Subject: RE: crosstool-ng: cross compiler for -mach=arm4vt (Cirrus Logic EP93xx target)
Date: Wed, 09 Sep 2009 17:26:00 -0000	[thread overview]
Message-ID: <BD79186B4FD85F4B8E60E381CAEE190901CBEADF@mi8nycmail19.Mi8.com> (raw)
In-Reply-To: <4AA7B01D.7070407@piments.com>

On Wednesday, September 09, 2009 6:40 AM, ng@piments.com wrote:
> H Hartley Sweeten wrote:
>> Hello all,
>> 
>> I have been trying to get CodeSourcery's arm-none-linux-gnueabi (Sourcery
>> G++ Lite 2009q1-203) 4.3.3 toolchain to work with Buildroot and an EP93xx
>> based target.  Unfortunately Buildroot is not setup to handle the multilib
>> feature of that toolchain (default libraries are for ARMv5T).  I have
>> tried a number of ways in Buildroot to get that that toolchain to work but
>> my resulting filesystem always dies due to an unrecognized instruction.
>> 
>> Today I downloaded crosstool-ng to try and build a sysroot toolchain
>> specifically for the armv4t.  I think I have everything setup correctly
>> but the build always dies at:
>> 
>
> I have made an eabi toolchain for TS boards based on the Cyrus chip 
> using a fairly recent ct-ng.
>
> You could try this .config as a basis.
>
> HTH.

My .config was very similar.  The only real difference is:

CT_THREADS="nptl"
CT_THREADS_NPTL=y

I had:

CT_THREADS="linuxthreads"
CT_THREADS_LINUXTHREADS=y

I'm trying the build now using nptl instead of linuxthreads.  So far it looks
good.  It appears something is wrong with the linuxthreads support.

Regards,
Hartley

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

  reply	other threads:[~2009-09-09 17:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-08 20:42 H Hartley Sweeten
2009-09-08 21:17 ` Yann E. MORIN
2009-09-08 21:31   ` Matthias Kaehlcke
2009-09-09  8:39 ` Steve Papacharalambous
2009-09-09 11:21   ` Martin Guy
2009-09-09 15:30     ` Steve Papacharalambous
2009-09-09 13:42 ` ng
2009-09-09 17:26   ` H Hartley Sweeten [this message]
2009-09-11 10:29     ` Martin Guy
2009-09-08 22:48 H Hartley Sweeten
2009-09-09 11:01 ` Martin Guy
2009-09-09 18:06   ` H Hartley Sweeten
2009-09-09 19:26     ` wino
2009-09-11 19:33     ` Martin Guy
2009-09-11 21:57       ` ng
2009-09-11 22:12         ` wino
2009-09-11 22:20         ` Martin Guy
2009-09-12 20:18           ` Khem Raj
2009-09-13 13:15             ` Martin Guy
2009-09-13 15:55               ` Khem Raj

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=BD79186B4FD85F4B8E60E381CAEE190901CBEADF@mi8nycmail19.Mi8.com \
    --to=hartleys@visionengravers.com \
    --cc=crossgcc@sourceware.org \
    --cc=ng@piments.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).