From: Mikael Magnusson <mikachu@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh workers <zsh-workers@zsh.org>
Subject: Re: Effectiveness of --disable-dynamic-nss?
Date: Fri, 7 Nov 2014 00:27:26 +0100 [thread overview]
Message-ID: <CAHYJk3QoOWOSHLUMJJtG+ug91cTD8Bp4zFK_=C2u2mvkKju20Q@mail.gmail.com> (raw)
In-Reply-To: <141106081701.ZM3756@torch.brasslantern.com>
On Thu, Nov 6, 2014 at 5:17 PM, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Nov 6, 3:11pm, Mikael Magnusson wrote:
> }
> } Someone was mentioning on the #zsh channel that $USERNAME was empty
> } when they compiled statically and I vaguely remembered glibc doesn't
> } support name lookup statically
>
> I build a fully-static zsh all the time and have never had a problem
> with USERNAME not being set. Is this platform-specific, or is the
> "when they compiled statically" specific to dynamic-nss ?
Well, they said they tried on both debian and gentoo, and that it
seemed disable-dynamic-nss was used on the debian build but not in the
gentoo build. I'm not sure if that's 100% trustworthy though. The
gentoo ebuild specifies only --disable-dynamic but also adds -static
to ldflags manually. They found this semi-old gentoo bugzilla entry
about it as well, https://bugs.gentoo.org/show_bug.cgi?id=412301 but
it's not very informative.
[I tried to test this locally, but I don't have a static ncurses
installed, which causes the test for boolcodes to return negative
failing to link, which in turn causes a double declaration compilation
failure.]
--
Mikael Magnusson
next prev parent reply other threads:[~2014-11-06 23:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 14:11 Mikael Magnusson
2014-11-06 14:55 ` Peter Stephenson
2014-11-06 16:17 ` Bart Schaefer
2014-11-06 23:27 ` Mikael Magnusson [this message]
2014-11-08 17:11 ` Clint Adams
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='CAHYJk3QoOWOSHLUMJJtG+ug91cTD8Bp4zFK_=C2u2mvkKju20Q@mail.gmail.com' \
--to=mikachu@gmail.com \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).