public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Peter S. Mazinger" <ps.m@gmx.net>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Re: Appropriate toolchain for a SPARC?
Date: Mon, 29 Jan 2007 07:54:08 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.44.0701290751360.6140-100000@lnx.bridge.intra> (raw)
In-Reply-To: <1169470281.5178.4.camel@localhost>

On Mon, 22 Jan 2007, Dimitris Lampridis wrote:

> On Sun, 2007-01-21 at 12:16 +0100, Peter S. Mazinger wrote:
> > On Fri, 19 Jan 2007, Dimitris Lampridis wrote:
> > 
> > > On Thu, 2007-01-18 at 11:47 +0100, Dimitris Lampridis wrote:
> > > > I want to build a cross toolchain on an x86 system, to be able to
> > > > compile for SPARC without hardware floating point support, using uclibc.
> > > > I've done some attempts already but they all fail (for various reasons).
> > > > Up until now, I have not succeeded 100%. So I thought I should do it in
> > > > the proper way, starting from the beginning:
> > > > 
> > > > Could you please let me know if there is a specific combination of
> > > > binutils, gcc, uclibc etc., that is well-known to work for a
> > > > sparc-softfloat-linux-uclibc target? 
> > > > 
> > > > thank you in advance,
> > > > Dimitris
> > > > 
> > > > PS: I currently try with:
> > > > 	binutils-2.17
> > > > 	gcc-4.1.1-r3
> > > > 	linux-headers-2.6.19.2-r1
> > > > 	uclibc-0.9.28-r2
> > > > 
> > > 
> > > nobody yet? Well, I've been trying several combinations of the programs,
> > > and they still all fail. I've had success with binutils-2.17, with gcc
> > > 3.4.1-r3, 3.4.4-r1 and 4.1.1-r3, but no luck with uclibc.
> > > 
> > > I've tried uclibc 0.9.28-r2, 0.9.28-r1 and 0.9.28 (as well as 0.9.27
> > > that apparently does not support sparc?), and every time they fail on
> > > the same problem, complaining about duplicate "_start" symbol in ldso.c.
> > > I've attached my uclibc emerge log, hopefully someone can propose
> > > something?
> > > 
> > > thank you,
> > > Dimitris
> > 
> > you may try to use uclibc-svn (no ebuild for it), some sparc support was 
> > added.
> > 
> > Peter
> > 
> > -- 
> > Peter S. Mazinger <ps dot m at gmx dot net>           ID: 0xA5F059F2
> > Key fingerprint = 92A4 31E1 56BC 3D5A 2D08  BB6E C389 975E A5F0 59F2
> > 
> Hmmm, uclibc from SVN does the trick. I also tried buildroot and I was
> able to produce a working toolchain for softfloat SPARC, out of:
> binutils-2.6.91.0.7
> linux-kernel-2.6.11
> gcc-3.4.2
> latest snapshot of uclibc
> 
> Thank you Peter for your time,
> Dimitris

don't rely though on the svn version for production, the locking is housed 
(many other bugs that I won't even try listing them).

Peter

-- 
Peter S. Mazinger <ps dot m at gmx dot net>           ID: 0xA5F059F2
Key fingerprint = 92A4 31E1 56BC 3D5A 2D08  BB6E C389 975E A5F0 59F2

-- 
gentoo-embedded@gentoo.org mailing list



      reply	other threads:[~2007-01-29  6:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1169117250.4697.12.camel@localhost>
2007-01-19 15:47 ` [gentoo-embedded] Re: Appropriate toolchain for a SPARC? Dimitris Lampridis
2007-01-21 11:16   ` Peter S. Mazinger
2007-01-22 12:51     ` Dimitris Lampridis
2007-01-29  6:54       ` Peter S. Mazinger [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=Pine.LNX.4.44.0701290751360.6140-100000@lnx.bridge.intra \
    --to=ps.m@gmx.net \
    --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