From: Catalin Marinas <catalin.marinas@arm.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: Problem building U-Boot for ARM target
Date: Tue, 11 Oct 2005 15:32:30 +0100 [thread overview]
Message-ID: <tnxirw4xgxt.fsf@arm.com> (raw)
In-Reply-To: <434BC738.1020707@softool.ch> (Paolo Broggini's message of "Tue, 11 Oct 2005 16:07:52 +0200")
Paolo Broggini <pbroggini@softool.ch> wrote:
> Well may be it starts to become out-of-topics here in U-Boot list,
> but just one more thing:
I don't think it is OT as long as the config.mk files are part of
U-Boot and they don't work as expected (unless the bug is definitely
in a different tool).
> I tried the macro cc-option "by hand" (so without $CFLAGS) in a bash
> shell and I got the same results as above, i.e. the check for option
> -mapcs-32 fails but the compiler support it and indeed the
> compilation works fine! May be a bug?
I tried the below file (with CC set to your compiler) and it works as
expected for me (called with the two options as arguments), choosing
-mapcs-32 (but it's a 3.4.0 compiler):
#!/bin/sh
CC=arm-linux-gcc
if $CC $1 -S -o /dev/null -xc /dev/null \
> /dev/null 2>&1; then echo "$1"; else echo "$2"; fi;
You could look for bug in the shell as well
--
Catalin
next prev parent reply other threads:[~2005-10-11 14:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 9:16 [U-Boot-Users] Problem building U-Boot for ARM target Paolo Broggini
2005-10-11 10:38 ` [U-Boot-Users] " Catalin Marinas
2005-10-11 12:14 ` Paolo Broggini
2005-10-11 12:48 ` Catalin Marinas
2005-10-11 13:22 ` Paolo Broggini
2005-10-11 13:44 ` Catalin Marinas
2005-10-11 14:07 ` Paolo Broggini
2005-10-11 14:32 ` Catalin Marinas [this message]
2005-10-11 15:33 ` Paolo Broggini
[not found] <89A528FE6DB0FA44877BB2F05B8467180331C12C@ZIPPY.Emea.Arm.com>
2005-10-12 8:46 ` Paolo Broggini
[not found] <89A528FE6DB0FA44877BB2F05B8467180331C407@ZIPPY.Emea.Arm.com>
2005-10-12 12:26 ` Paolo Broggini
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=tnxirw4xgxt.fsf@arm.com \
--to=catalin.marinas@arm.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.