From: orc <orc@sibserver.ru>
To: musl@lists.openwall.com
Subject: Re: Priorities for next release?
Date: Sun, 12 Aug 2012 01:55:36 +0800 [thread overview]
Message-ID: <20120812015536.3caa3999@sibserver.ru> (raw)
In-Reply-To: <20120811165049.GI27715@brightrain.aerifal.cx>
On Sat, 11 Aug 2012 12:50:49 -0400
Rich Felker <dalias@aerifal.cx> wrote:
> On Sat, Aug 11, 2012 at 06:35:12PM +0200, Daniel Cegiełka wrote:
> > >> argv[0]
> > >
> > > I meant program_invocation_name or whatever ugly thing glibc
> > > calls it. Of course if the goal is to make BSD programs happy,
> > > that won't really help. I really wish somebody would just fix
> > > these programs to save argv[0] themselves if they need it (or to
> > > hard-code their own names as a string literal...) rather than
> > > keeping around the historical practice of poking at
> > > implementation internals of the original libc they used..
> >
> > That's what I do now (patches for __progname). Unfortunately some
> > linux distributions forcing __progname, even Owl:
> >
> > in Owl's popa3d we have a #ifdef, which really helps.
> >
> > #ifdef HAVE_PROGNAME
> > extern char *__progname;
> > #define progname __progname
> >
> > http://cvsweb.openwall.com/cgi/cvsweb.cgi/Owl/packages/popa3d/popa3d/startup.c?rev=1.4;content-type=text%2Fplain
> >
> > but for Owl's msulogin we need a patch for musl:
> >
> > http://cvsweb.openwall.com/cgi/cvsweb.cgi/Owl/packages/msulogin/msulogin/sulogin.c?rev=1.4;content-type=text%2Fplain
>
> Couldn't this code just be fixed to add an argument to usage() and
> call usage(argv[0]) or even usage(basename(argv[0])) if preferred?
>
> Rich
Or even progname = basename(argv[0]) with global char *progname ?
next prev parent reply other threads:[~2012-08-11 17:55 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 19:12 Rich Felker
2012-08-10 19:23 ` Nathan McSween
2012-08-10 19:39 ` Unit/regression testing (was Re: [musl] Priorities for next release?) Rich Felker
2012-08-10 22:03 ` Priorities for next release? Luca Barbato
2012-08-11 0:05 ` Rich Felker
2012-08-11 0:54 ` Luca Barbato
2012-08-11 1:07 ` Rich Felker
2012-08-11 2:21 ` idunham
2012-08-11 2:36 ` Rich Felker
2012-08-11 12:21 ` Daniel Cegiełka
2012-08-11 12:27 ` Rich Felker
2012-08-11 12:35 ` Daniel Cegiełka
2012-08-11 16:09 ` Rich Felker
2012-08-11 16:35 ` Daniel Cegiełka
2012-08-11 16:50 ` Rich Felker
2012-08-11 17:55 ` orc [this message]
2012-08-11 18:41 ` Daniel Cegiełka
2012-08-11 18:47 ` orc
2012-08-11 19:05 ` Daniel Cegiełka
2012-08-11 19:28 ` Rich Felker
2012-08-11 19:56 ` Rich Felker
2012-08-11 20:26 ` Daniel Cegiełka
2012-08-11 20:51 ` Rich Felker
2012-08-11 20:56 ` Rich Felker
2012-08-11 21:22 ` Rich Felker
2012-08-12 12:52 ` Daniel Cegiełka
2012-08-11 22:25 ` Rich Felker
2012-08-12 12:40 ` Szabolcs Nagy
2012-08-13 8:40 ` Luca Barbato
2012-08-13 13:41 ` Rich Felker
2012-08-13 15:49 ` Szabolcs Nagy
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=20120812015536.3caa3999@sibserver.ru \
--to=orc@sibserver.ru \
--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).