public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "i at maskray dot me" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/29835] Error compiling glibc multilib with --enable-static-pie option turned on
Date: Fri, 02 Dec 2022 22:02:25 +0000	[thread overview]
Message-ID: <bug-29835-131-dBNHCfhwBz@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29835-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29835

Fangrui Song <i at maskray dot me> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |i at maskray dot me

--- Comment #3 from Fangrui Song <i at maskray dot me> ---
How do you configure your build?


mkdir -p out/arm && cd out/arm
../../configure --prefix=/tmp/glibc/arm --host=arm-linux-gnueabihf
--enable-static-pie --enable-hardcoded-path-in-tests
make -j 60  # good

% grep pie_supported config.log
libc_cv_pie_supported=yes
libc_cv_static_pie_supported=no

Note that sysdeps/arm/configure.ac doesn't say `AC_DEFINE(SUPPORT_STATIC_PIE)`,
so I think static-pie for sysdeps/arm is unsupported.


% cat a.c
const char *foo (void)
{
  extern const char _DYNAMIC[] __attribute__((visibility("hidden")));
  return _DYNAMIC;
}
% arm-linux-gnueabihf-gcc -fpic  -nostdlib -static-pie a.c
# good. Both -shared and -pie have .dynamic and define _DYNAMIC

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-12-02 22:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 12:00 [Bug build/29835] New: " linzhuorong at huawei dot com
2022-11-29 12:23 ` [Bug dynamic-link/29835] " linzhuorong at huawei dot com
2022-11-29 12:24 ` linzhuorong at huawei dot com
2022-11-29 12:54 ` schwab@linux-m68k.org
2022-12-02  9:52 ` schwab@linux-m68k.org
2022-12-02 22:02 ` i at maskray dot me [this message]
2022-12-05  1:50 ` linzhuorong at huawei dot com
2022-12-06 10:56 ` schwab@linux-m68k.org
2022-12-06 12:14 ` linzhuorong at huawei dot com
2022-12-06 12:38 ` schwab@linux-m68k.org
2022-12-07 12:50 ` linzhuorong at huawei dot com
2022-12-18  0:33 ` i at maskray dot me

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-29835-131-dBNHCfhwBz@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).