From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14876] New: arm-trusted-firmware can no longer be compiled with fPIE
Date: Mon, 27 Jun 2022 10:09:40 +0000 [thread overview]
Message-ID: <bug-14876-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=14876
Bug ID: 14876
Summary: arm-trusted-firmware can no longer be compiled with
fPIE
Product: buildroot
Version: 2022.02.3
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: alexandru.apostolescu@keysight.com
CC: buildroot@uclibc.org
Target Milestone: ---
After a recent commit the rule for fPIE was removed and supposedly replaced
with flag "ENABLE_PIE" but it can not be found.
commit hash: 467836357943f3a08a2ee3686e2878c51f9c4453
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-06-27 10:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 10:09 bugzilla [this message]
2022-06-27 10:13 ` [Buildroot] [Bug 14876] arm-trusted-firmware can no longer be compiled with fPIE bugzilla
2022-06-27 20:06 ` bugzilla
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-14876-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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