From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 755de2: elf2flt: use CT_ARCH to set target CPU, not CT_TAR...
Date: Thu, 09 Feb 2017 07:19:00 -0000 [thread overview]
Message-ID: <589c17e7b4bca_6d493ffdca833c3870784@hookshot-fe1-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 2249 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 755de234cb50aa786e7e6821e14d611775650cb6
https://github.com/crosstool-ng/crosstool-ng/commit/755de234cb50aa786e7e6821e14d611775650cb6
Author: Carlos Santos <casantos@datacom.ind.br>
Date: 2017-02-06 (Mon, 06 Feb 2017)
Changed paths:
M scripts/build/binutils/binutils.sh
Log Message:
-----------
elf2flt: use CT_ARCH to set target CPU, not CT_TARGET
CT_TARGET is composed as "${CT_ARCH}${CT_ARCH_SUFFIX}", so CT_TARGET may
become something like "armv7", for example. This is used by the configure
script to set the "CPU" variable in the Makefile, leading to a commad line
containing
-DTARGET_armv7 -DTARGET_CPU="armv7"
In this case the compilation of elf2flt.c fails with "Don't know how to
support your CPU architecture??". Passsing "CPU=${CT_ARCH}" in the make
command line overrides the configured value and solves the problem.
Signed-off-by: Carlos Santos <casantos@datacom.ind.br>
Commit: 308c6b9a145cbfbd3e9a4b09aef5935572cce6ab
https://github.com/crosstool-ng/crosstool-ng/commit/308c6b9a145cbfbd3e9a4b09aef5935572cce6ab
Author: Alexey Neyman <stilor@att.net>
Date: 2017-02-07 (Tue, 07 Feb 2017)
Changed paths:
A samples/armv6-nommu-linux-uclibcgnueabi/crosstool.config
A samples/armv6-nommu-linux-uclibcgnueabi/reported.by
Log Message:
-----------
Add a contrived ARM with elf2flt sample
... that exhibited the issue with elf2flt configuration. Original reported
did not provide the config, and did not respond.
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: df555a65dbea7aedcef462590230da639fb6a421
https://github.com/crosstool-ng/crosstool-ng/commit/df555a65dbea7aedcef462590230da639fb6a421
Author: Alexey Neyman <stilor@att.net>
Date: 2017-02-08 (Wed, 08 Feb 2017)
Changed paths:
A samples/armv6-nommu-linux-uclibcgnueabi/crosstool.config
A samples/armv6-nommu-linux-uclibcgnueabi/reported.by
M scripts/build/binutils/binutils.sh
Log Message:
-----------
Merge pull request #580 from stilor/arm-elf2flt
ARM with arch suffix - elf2flt fix
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/18775775e53f...df555a65dbea
reply other threads:[~2017-02-09 7:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=589c17e7b4bca_6d493ffdca833c3870784@hookshot-fe1-cp1-prd.iad.github.net.mail \
--to=stilor@att.net \
--cc=crossgcc@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).