From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12801] Flag '-Wa, --noexecstack' is missing when building uclibc with newer binutils
Date: Wed, 22 Apr 2020 11:15:19 +0000 [thread overview]
Message-ID: <bug-12801-163-KyLP8XJXwa@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12801-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12801
Marcel Patzlaff <m.patzlaff@pilz.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Product|buildroot |uClibc
Component|Other |Other
Assignee|unassigned at buildroot.uclibc |unassigned at uclibc.org
|.org |
CC| |uclibc-cvs at uclibc.org
--- Comment #3 from Marcel Patzlaff <m.patzlaff@pilz.de> ---
I finally found what the problem is. The check_as macro in uclibc/Rules.mak
does not function with newer binutils versions anymore. Executing the check
manually yield:
$ /opt/debug/buildroot_toolchain/usr/bin/arm-se-linux-uclibcgnueabihf-gcc
-Wa,--noexecstack -Wa,-Z -c -o /dev/null -xassembler /dev/null || echo "WTF"
Assembler messages:
Fatal error: The input '/dev/null' and output '/dev/null' files are the same
So basically, this seems to be uClibc bug.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-04-22 11:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 7:55 [Buildroot] [Bug 12801] New: Flag '-Wa, --noexecstack' is missing when building uclibc with newer binutils bugzilla at busybox.net
2020-04-22 8:05 ` [Buildroot] [Bug 12801] " bugzilla at busybox.net
2020-04-22 8:05 ` bugzilla at busybox.net
2020-04-22 8:22 ` bugzilla at busybox.net
2020-04-22 11:15 ` bugzilla at busybox.net [this message]
2020-04-22 12:37 ` bugzilla at busybox.net
2020-04-24 12:19 ` bugzilla at busybox.net
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=bug-12801-163-KyLP8XJXwa@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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