From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] gcc breaks when compiling in final-stage
Date: Thu, 2 Aug 2007 20:02:05 +0200 [thread overview]
Message-ID: <20070802180205.GL11697@aon.at> (raw)
In-Reply-To: <20070802091021.GD4820@firebird.dresden.micronet24.de>
On Thu, Aug 02, 2007 at 11:10:21AM +0200, Benjamin Tietz wrote:
>Hi all,
>
>when building the internal toolchain with, at least, gcc 4.1.2 it breaks
>in the final stage. Complaining about that there is no rule to build
>/usr/bin/i686-linux-uclibc-as. As you can see, there is the
>$(STAGING_DIR) missing. Looking into the Makefile, it turns out that a
>lot of variables named like ORIGINAL_(TOOL)_FOR_TARGET are defined that
>way; replacing (TOOL) with AS, LD, NM.
>There where already installed into the correct lcation, under
>$(STAGING_DIR)/usr/bin; just these variables are mistakenly generated.
>
>What would be the fastest way to fix this?
revert that ORIGINAL_(TOOL)_FOR_TARGET stuff.
Ulf, until this stuff works, please create yourself a branch to work on.
next prev parent reply other threads:[~2007-08-02 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 9:10 [Buildroot] gcc breaks when compiling in final-stage Benjamin Tietz
2007-08-02 18:02 ` Bernhard Fischer [this message]
2007-08-03 19:20 ` Benjamin Tietz
-- strict thread matches above, loose matches on Subject: below --
2007-08-03 5:54 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=20070802180205.GL11697@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