Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] AVR32 misery
Date: Fri, 28 Sep 2007 21:14:40 +0200	[thread overview]
Message-ID: <20070928191440.GS20951@aon.at> (raw)
In-Reply-To: <1191005626.5322.216.camel@elrond.atmel.sweden>

On Fri, Sep 28, 2007 at 08:53:46PM +0200, Ulf Samuelsson wrote:
 
>> We don't need to pass --with-gnu-ld nor --with-gnu-as. If sombody finds
>> a different assembler or linker, then this is a consequence of something
>> going wrong previously. The target is linux and not irix or something
>> like that.
>
>Well gcc-4.1.2 doesn't find anything apparently 
>unless you bombard it with information during configure.
>-with-as=$(CROSS_COMPILE)as seems absolutely neccessary.
>or ORIGINAL_AS_FOR_TARGET will be empty.
>
>Empty ORIGINAL_AS_FOR_TARGET is why sysroot fails.

Yea, I know. This and the fact that gcc-4.1.x is not the current release
series, so i decided to leave it alone.

>Still gcc-4.1.2 has problems with libtool.

4.1 has lots of problems, and lots of problems were thusly fixed in the
current (and upcoming) release(s). Trying to fix 4.1 it doesn't make
sense to me, there's enough to do in current stuff that is way more
interresting, at least IMO.

But i'm digressing..

  reply	other threads:[~2007-09-28 19:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-28  0:08 [Buildroot] AVR32 misery Ulf Samuelsson
2007-09-28  5:20 ` Hans-Christian Egtvedt
2007-09-28  6:42   ` Ulf Samuelsson
2007-09-28 16:24     ` Bernhard Fischer
2007-09-28 18:53       ` Ulf Samuelsson
2007-09-28 19:14         ` Bernhard Fischer [this message]
2007-09-28 21:03           ` Ulf Samuelsson
2007-09-28 21:27             ` Bernhard Fischer
2007-09-28  7:35 ` Ulf Samuelsson

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=20070928191440.GS20951@aon.at \
    --to=rep.dot.nop@gmail.com \
    --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