From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] toolchain-external: Fix EABIhf check
Date: Tue, 28 Jan 2014 22:57:31 +0100 [thread overview]
Message-ID: <20140128225731.103edf8a@skate> (raw)
In-Reply-To: <1389687696-4824-1-git-send-email-stefan.sorensen@spectralink.com>
Dear Stefan S?rensen,
On Tue, 14 Jan 2014 09:21:34 +0100, Stefan S?rensen wrote:
> Currently the check for EABI/EABIhf toolchains looks for the
> Tag_ABI_VFP_args attribute in the crt1.o file which gcc adds
> in a EABIhw toolchain. The crt1.o is however often not compiled
> from c but assembler, and will then always failt he EABIhf check.
Do you have details about this? Because the crt1.o trick was actually
tested by me on several toolchains, and it was indeed working.
> + TEMP_C_FILE=`mktemp --tmpdir --suffix=.c`; \
> + touch $${TEMP_C_FILE}; \
> + $${__CROSS_CC} -c -o $${TEMP_C_FILE}.o $${TEMP_C_FILE}; \
If all you need is build an empty source file, then you do not even
need to create a temporary .c file:
gcc -x c -c -o toto.o /dev/null
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-01-28 21:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 8:21 [Buildroot] [PATCH 1/3] toolchain-external: Fix EABIhf check Stefan Sørensen
2014-01-14 8:21 ` [Buildroot] [PATCH 2/3] toolchain-external: Fix ld.so naming with uClibc and EABIhf Stefan Sørensen
2014-01-15 21:52 ` Peter Korsgaard
2014-01-14 8:21 ` [Buildroot] [PATCH 3/3] protobuf-c: Don't require protobuf on target Stefan Sørensen
2014-01-15 21:24 ` Peter Korsgaard
2014-01-28 21:57 ` Thomas Petazzoni [this message]
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=20140128225731.103edf8a@skate \
--to=thomas.petazzoni@free-electrons.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