From: Hans-Christian Egtvedt <hcegtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] AVR32 misery
Date: Fri, 28 Sep 2007 07:20:02 +0200 [thread overview]
Message-ID: <1190956802.18129.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1190938123.5322.54.camel@elrond.atmel.sweden>
On Fri, 2007-09-28 at 02:08 +0200, Ulf Samuelsson wrote:
> I think I have found one problem
> "toolchain_build_avr32/gcc-4.1.2-initial/gcc/as" is a script file
> which should call the assembler.
>
> It contains
>
> #!/bin/sh
> exec "$@"
>
> and should contain:
> #!/bin/sh
> exec <buildroot>/build_avr32/staging_dir/bin/avr32-linux-uclibc-ld "$@"
This should really not mather, because the PATH variable should be set
before starting to compile the cross-compiler.
Perhaps this is as easy as a missing TARGET_CONFIGURE_OPTS?
--
With kind regards,
Hans-Christian Egtvedt, Applications Engineer
next prev parent reply other threads:[~2007-09-28 5:20 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 [this message]
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
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=1190956802.18129.2.camel@localhost.localdomain \
--to=hcegtvedt@atmel.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