From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11616] New: 2018.02.09 fails to build libzlib with full RELRO protection
Date: Fri, 11 Jan 2019 07:39:28 +0000 [thread overview]
Message-ID: <bug-11616-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11616
Bug ID: 11616
Summary: 2018.02.09 fails to build libzlib with full RELRO
protection
Product: buildroot
Version: 2018.02.9
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: mail at kkrach.de
CC: buildroot at uclibc.org
Target Milestone: ---
Created attachment 7911
--> https://bugs.busybox.net/attachment.cgi?id=7911&action=edit
defconfig which fails
Compiling libzlib the given defconfig (powerpc, GCC 7.3, BR2_RELRO_FULL=y)
fails with
sysroot/usr/lib/Scrt1.o: In function `_start':
(.text+0x42): undefined reference to `main'
collect2: error: ld returned 1 exit status
Switching RELRO off or to partial, compiles successfully.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-01-11 7:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 7:39 bugzilla at busybox.net [this message]
2019-01-11 7:44 ` [Buildroot] [Bug 11616] 2018.02.09 fails to build libzlib with full RELRO protection bugzilla at busybox.net
2019-01-11 7:45 ` bugzilla at busybox.net
2019-01-11 7:46 ` bugzilla at busybox.net
2019-01-11 14:16 ` bugzilla at busybox.net
2019-01-12 9:21 ` bugzilla at busybox.net
2019-01-12 13:59 ` bugzilla at busybox.net
2019-01-14 7:49 ` bugzilla at busybox.net
2019-01-14 14:06 ` bugzilla at busybox.net
2019-01-14 21:33 ` 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-11616-163@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 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.