From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] i686-buildroot-linux-gnu-as does not work
Date: Mon, 27 Jan 2014 23:23:34 +0100 [thread overview]
Message-ID: <52E6DC66.6040105@mind.be> (raw)
In-Reply-To: <1848702296.4768001.1390826907232.JavaMail.root@openwide.fr>
On 27/01/14 13:48, Romain Naour wrote:
> I meant that usually in buildroot, Makefile's variables are overwritten in foo.mk
>
> I removed my patch and added AS="$(TARGET_CC) -c" in infozip.mk
>
> $(MAKE) $(TARGET_CONFIGURE_OPTS) -C $(@D) AS="$(TARGET_CC) -c" -f unix/Makefile generic
>
> infozip compiles fine by doing that.
Actually there's a deeper cause I'm afraid...
The make command calls unix/configure to find out some things about the
platform, but the configure script sets CPP to /usr/bin/cpp or /lib/cpp
if either of these exist. But those host tools obviously have the wrong
predefined symbols, so the configure script will test if it is possible
to use assembly for the host, not for the target...
I think there are two possible "right" solutions:
1. fix unix/configure;
2. bypass unix/configure by using the generic_gcc target instead.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2014-01-27 22:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 10:23 [Buildroot] i686-buildroot-linux-gnu-as does not work Кирилл Луценко
2014-01-26 17:12 ` Alexander Lukichev
2014-01-26 19:33 ` Кирилл Луценко
2014-01-27 7:37 ` Кирилл Луценко
2014-01-27 10:59 ` Romain Naour
2014-01-27 11:47 ` Alexander Lukichev
2014-01-27 12:48 ` Romain Naour
2014-01-27 22:23 ` Arnout Vandecappelle [this message]
2014-01-30 22:20 ` Romain Naour
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=52E6DC66.6040105@mind.be \
--to=arnout@mind.be \
--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