Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Effectiveness of --disable-dynamic-nss?
- X-seq: zsh-workers 33610
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh workers <zsh-workers@xxxxxxx>
- Subject: Re: Effectiveness of --disable-dynamic-nss?
- Date: Thu, 06 Nov 2014 08:17:01 -0800
- In-reply-to: <CAHYJk3TpyqP-RvumAQbzwhd8f=TGTjfP6LATAU_VZ=+9oHp5ng@mail.gmail.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <CAHYJk3TpyqP-RvumAQbzwhd8f=TGTjfP6LATAU_VZ=+9oHp5ng@mail.gmail.com>
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 ?
} Is there a reason they were left alone or does the switch not work?
} If they're all meant to be disabled, why not just have it #undef the
} HAVE_* defines instead of defining new things and changing every user,
} and hope nobody ever introduces new HAVE_* #ifdefs?
I think the idea here is that multiple lookup methods may be compiled
in, and you can choose to use different subsets of them, so it may be
the case that HAVE_* is true while desiring to prefer some other way
if available vs. never use some other method even if it is available.
I can imagine this logic got confused somewhere along the way, or that
certain cases were missed. I think Clint Adams still reads this list
and it looks like --disable-dynamic-nss was his patch, so maybe he can
speak to it more directly.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author