From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: vfprintf.c:(.text+0xc6c): undefined reference to `__signbitl'
Date: Wed, 10 Apr 2013 02:21:29 -0400 [thread overview]
Message-ID: <20130410062129.GB20323@brightrain.aerifal.cx> (raw)
In-Reply-To: <1365570853.18069.61@driftwood>
On Wed, Apr 10, 2013 at 12:14:13AM -0500, Rob Landley wrote:
> On 04/08/2013 03:41:28 PM, meres5@alpha.tmit.bme.hu wrote:
> >Also Linux dropped the concept of static linking in practivce.
> >Goodby kiss to
>
> No it didn't. Ulrich Drepper, the ex-glibc maintainer, had a
> personal grudge against static linking. But the community did one of
> this gcc->egcs things and abandoned glibc in droves for eglibc until
> Ulrich bogged off to The Bank of Evil (Goldman Sachs), and now less
> crazy people are in charge of glibc.
To set the record straight, the current glibc maintainership considers
static linking supported. I don't have the citations right off, but
there have been several threads in which issues of current breakage
with static linking, or avoiding future breakage, came up, and each
time the position seems to have been that static linking is supported.
I could probably dig them up if anybody's interested.
Rich
next prev parent reply other threads:[~2013-04-10 6:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 19:39 meres5
2013-04-08 20:05 ` Szabolcs Nagy
2013-04-08 20:41 ` meres5
2013-04-08 21:26 ` Szabolcs Nagy
2013-04-09 20:15 ` meres5
2013-04-09 22:38 ` Szabolcs Nagy
2013-04-10 1:18 ` Rich Felker
2013-04-10 10:55 ` meres5
2013-04-10 8:24 ` John Spencer
2013-04-10 9:47 ` Szabolcs Nagy
2013-04-10 14:14 ` Isaac Dunham
2013-04-10 14:31 ` Rich Felker
2013-08-11 21:30 ` Justin Cormack
2013-04-10 5:14 ` Rob Landley
2013-04-10 6:21 ` Rich Felker [this message]
2013-04-08 20:09 ` Rich Felker
2013-04-08 20:47 ` meres5
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=20130410062129.GB20323@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).