mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "Андрей Аладьев" <aladjev.andrew@gmail.com>
To: musl@lists.openwall.com
Subject: Re: [musl] Static linking is broken after creation of DT_TEXTREL segment
Date: Thu, 30 Jan 2020 00:35:52 +0300	[thread overview]
Message-ID: <CAMw0szKYTWd2vbBi7M1Zs7ik=Vi6tWxuNASxtsVwghdi=_zdXA@mail.gmail.com> (raw)
In-Reply-To: <20200129211024.GY23985@port70.net>

[-- Attachment #1: Type: text/plain, Size: 1839 bytes --]

"readelf -d main | grep TEXTREL" returns the same text on both musl and
glibc containers:

0x0000000000000016 (TEXTREL) 0x0
0x000000000000001e (FLAGS)     TEXTREL

"gcc -no-pie" is another workaround for musl container like Rich said. But
I think that 'set(CMAKE_EXE_LINKER_FLAGS "-static")' will be best cross
platform solution. As I know "-static" implies "no-pie".

> i'm also surprised that it was only a warning, i think gcc default pie
toolchain passes -z text nowadays exactly to make this a link time failure.
this is probably a gentoo toolchain bug.

What do you mean "-z text"? We can report improvement for gentoo.

чт, 30 янв. 2020 г. в 00:10, Szabolcs Nagy <nsz@port70.net>:

> * Rich Felker <dalias@libc.org> [2020-01-29 15:53:30 -0500]:
> > On Wed, Jan 29, 2020 at 09:41:46PM +0300, Андрей Аладьев wrote:
> > > So I think that bug is inside musl itself. Glibc container is the same
> > > situation works fine. I see no way to create a workaround for this
> issue.
> >
> > musl only has limited support for TEXTRELs as a legacy feature, and
> > only on some archs. It does not support them in PIE executables or
> > other "new settings".
>
> i would like to see why this works on glibc.
>
> glibc can process some text relocs but even then
> the elf image will not be shared when multiple
> instances of the same binary are executed
> potentially wasting a lot of ram and icache.
>
> so i don't think the glibc behaviour is desirable.
>
> if the glibc binary does not have textrel (it can
> be checked using readelf -d binary) it would be
> nice to know why.
>
> i'm also surprised that it was only a warning,
> i think gcc default pie toolchain passes -z text
> nowadays exactly to make this a link time failure.
> this is probably a gentoo toolchain bug.
>

[-- Attachment #2: Type: text/html, Size: 2436 bytes --]

  reply	other threads:[~2020-01-29 21:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-29 18:41 Андрей Аладьев
2020-01-29 19:19 ` Markus Wichmann
2020-01-29 19:38   ` Markus Wichmann
2020-01-29 20:48     ` Rich Felker
2020-01-29 20:08   ` Андрей Аладьев
2020-01-30 17:02     ` Markus Wichmann
2020-01-31  4:24       ` Rich Felker
2020-01-31 14:47         ` Markus Wichmann
2020-01-31 16:35           ` Rich Felker
2020-01-31 15:16       ` Андрей Аладьев
2020-01-31 16:40         ` Rich Felker
2020-01-31 17:51           ` Андрей Аладьев
2020-01-31 18:01             ` Rich Felker
2020-01-31 19:11               ` Андрей Аладьев
2020-02-03  3:10       ` Rich Felker
2020-02-03  4:05         ` Rich Felker
2020-02-03  4:32         ` Markus Wichmann
2020-02-03  4:40           ` Rich Felker
2020-01-29 20:53 ` Rich Felker
2020-01-29 21:10   ` Szabolcs Nagy
2020-01-29 21:35     ` Андрей Аладьев [this message]
2020-01-29 21:46       ` Rich Felker
2020-01-29 23:10         ` Андрей Аладьев
2020-01-29 23:20       ` Szabolcs Nagy
2020-01-29 21:14   ` Андрей Аладьев
2020-01-29 21:43     ` Rich Felker

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='CAMw0szKYTWd2vbBi7M1Zs7ik=Vi6tWxuNASxtsVwghdi=_zdXA@mail.gmail.com' \
    --to=aladjev.andrew@gmail.com \
    --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).