mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Unable to build with --enable-shared
Date: Sat, 22 Oct 2016 23:58:29 +0200	[thread overview]
Message-ID: <20161022215829.GA5749@port70.net> (raw)
In-Reply-To: <CAJ4e7SU19GkpcqWgwQeDkHmWg4mwHp5YU6VD3xZLEJq2KqXQLQ@mail.gmail.com>

* Samuel Sadok <innovation-labs@appinstall.ch> [2016-10-22 22:37:46 +0200]:
> I am unable to build musl with --enable-shared. Multiple issues in
> unrelated projects (e.g. here: https://bugs.swift.org/browse/SR-1023)
> suggest that the culprit is a change in behaviour between binutils
> 2.25 and 2.26.
> 

that bug is different, that's about object symbols

(swift seems to misuse protected visibility objects,
and instead of fixing the problem they switched to the
gold linker which does not yet have the bfd linker fix,
such incompetence is frustrating..  however the issue
does not affect musl: we don't mark objects protected
to avoid issues with broken toolchains.)

> $ make
> [...]
> x86_64-pc-linux-gnu-gcc  -D_XOPEN_SOURCE=700 -I./arch/x86_64
> -I./arch/generic -Iobj/src/internal -I./src/internal -Iobj/include
> -I./include  -include vis.h -B/usr/local/bin/x86_64-pc-linux-gnu-
> -fPIC -c -o obj/src/process/posix_spawn.lo src/process/posix_spawn.c

some flags are missing here.. e.g. freestanding flags

> [...]
> x86_64-pc-linux-gnu-gcc  -D_XOPEN_SOURCE=700 -I./arch/x86_64
> -I./arch/generic -Iobj/src/internal -I./src/internal -Iobj/include
> -I./include  -include vis.h -B/usr/local/bin/x86_64-pc-linux-gnu-
> -nostdlib -shared -Wl,-e,_dlstart -o lib/libc.so obj/src/aio/aio.lo [a
> ton of objects] obj/ldso/dynlink.lo
> /usr/local/bin/x86_64-pc-linux-gnu-ld: obj/src/process/posix_spawn.lo:
> relocation R_X86_64_PC32 against protected symbol `execve' can not be
> used when making a shared object
> /usr/local/bin/x86_64-pc-linux-gnu-ld: final link failed: Bad value
> collect2: error: ld returned 1 exit status
> make: *** [lib/libc.so] Error 1
> 

execve is a protected function symbol, so it should be bound locally,
i think R_X86_64_PC32 is ok for that, so it's not clear to me what
goes wrong..


  reply	other threads:[~2016-10-22 21:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-22 20:37 Samuel Sadok
2016-10-22 21:58 ` Szabolcs Nagy [this message]
2016-10-23  0:22   ` Samuel Sadok
2016-10-23 16:17     ` Rich Felker
2016-10-23 22:20       ` Samuel Sadok
2016-10-24  0:19         ` Laine Gholson
2016-10-24  0:28           ` Rich Felker
2016-10-24 10:22             ` Samuel Sadok

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=20161022215829.GA5749@port70.net \
    --to=nsz@port70.net \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).