mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: i686 with -fPIE and -fstack-protector-all
Date: Sat, 22 Mar 2014 13:42:32 -0400	[thread overview]
Message-ID: <20140322174232.GP26358@brightrain.aerifal.cx> (raw)
In-Reply-To: <532D913C.7080407@opensource.dyc.edu>

On Sat, Mar 22, 2014 at 09:33:48AM -0400, Anthony G. Basile wrote:
> On 03/22/2014 09:06 AM, Szabolcs Nagy wrote:
> >* Anthony G. Basile <basile@opensource.dyc.edu> [2014-03-22 08:53:07 -0400]:
> >>I've hit a bug with 1.0.0 on i686.  When building with
> >>-fstack-protector-all and -fPIE, I get an undefined reference to
> >>`__stack_chk_fail_local'.  I do not get this on x86_64:
> >>
> >
> >may be this gcc bug should be in the faq
> >
> >http://gcc.gnu.org/ml/gcc/2012-01/msg00012.html
> >http://git.alpinelinux.org/cgit/aports/tree/main/musl/__stack_chk_fail_local.c
> >
> 
> Thanks it.  I was going to adopt a patch like alpines but hesitated
> in csae I was missing something.
> 
> Aside: it looks like alpine is hitting a lot of the same issues i am
> with gentoo+musl and adopting similar approaches, like getent and
> ldconfig.

Can ldconfig just be an empty script? Or does it need to make plain
.so symlinks to all the .so.X.Y.Z files so that ld can find them? I'm
not clear on whether most packages (e.g. libtool based) do the symlink
themselves or expect ldconfig to do so. It doesn't affect runtime
usage but it does affect linking programs against the library.

If we can figure out all this stuff, it would be great if someone
could make a clean git repo of replacements for all of the glibc
binaries that one could use with musl. Do you (or anyone else) have a
list of programs we'd need to make dists happy?

Rich


  reply	other threads:[~2014-03-22 17:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-22 12:53 Anthony G. Basile
2014-03-22 13:06 ` Szabolcs Nagy
2014-03-22 13:33   ` Anthony G. Basile
2014-03-22 17:42     ` Rich Felker [this message]
2014-03-22 20:44       ` Anthony G. Basile

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=20140322174232.GP26358@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --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).