Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] external toolchain --sysroot
Date: Wed, 14 Jan 2009 21:04:34 +1100	[thread overview]
Message-ID: <20090114100434.GA8469@cloud.net.au> (raw)
In-Reply-To: <20090114094308.GA26312@mx.loc>

On Wed, Jan 14, 2009 at 10:43:09AM +0100, Bernhard Reutner-Fischer wrote:
> On Wed, Jan 14, 2009 at 10:11:30AM +1100, Hamish Moffatt wrote:
> 
> >Right. I notice that --sysroot is being used even if gcc is compiled
> >without it. And it appears that sysroot is buggy in gcc 4.1.2, which is
> >what I'm using currently.
> 
> The whole gcc-4.1.x series is discontinued and not maintained anymore.
> You would be better off to use a somewhat current toolchain or at least
> avoid versions that are known to be broken (like sysroot and 4.1.x).
> Sysroot support is deliberately marked as unavailable for anything older
> than the 4.2.x series for good reasons -- see toolchain/gcc/Config.in

Yes it is, but package/Makefile.in doesn't use that setting, but uses
--sysroot regardless for the external toolchain.

Anyway, gcc 4.3.2 / armeb / EABI seems to build. When I first started
with buildroot I couldn't get anything better than 4.1.2 / OABI to
build, so I stuck with it. Mind you, I couldn't build anything else
after the toolchain - still need to debug that.


Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

      reply	other threads:[~2009-01-14 10:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13  4:30 [Buildroot] external toolchain --sysroot Hamish Moffatt
2009-01-13  4:45 ` Eric
2009-01-13  4:46   ` Eric
2009-01-13  4:52     ` Eric
2009-01-13 23:11       ` Hamish Moffatt
2009-01-14  8:30         ` Daniel James Laird
2009-01-14  9:43         ` Bernhard Reutner-Fischer
2009-01-14 10:04           ` Hamish Moffatt [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=20090114100434.GA8469@cloud.net.au \
    --to=hamish@cloud.net.au \
    --cc=buildroot@busybox.net \
    /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