From: Christian Franke <Christian.Franke@t-online.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Use getopt_long() instead of argp_parse() in grub-emu
Date: Sat, 10 Nov 2007 22:45:42 +0100 [thread overview]
Message-ID: <47362686.6030407@t-online.de> (raw)
In-Reply-To: <87wssqf39h.fsf@xs4all.nl>
Marco Gerards wrote:
> Christian Franke <Christian.Franke@t-online.de> writes:
>
>
>> Unlike the other GRUB2 utils, grub-emu uses the glibc extension
>> argp_parse(). It is unavailable on Cygwin, which might also be the
>> case for other platforms where glibc is not the native runtime.
>>
>
> This has been brought up before, BSD has the same problem. The
> outcome of the discussion was (IIRC) that we will use argp. When argp
> is not available we can use gnulib or a standalone argp parser
> ("argp-standalone") to support this. In that case it will mean
> changing configure.ac.
>
>
Will argp_parse() be a pre-requisite for building GRUB2 or will
argp-standalone be included (some other projects do) ?
If you really want argp, why is it used only for the few trivial options
of grub-emu ? The other utils still use getopt_long().
grub-emu does not benefit much from argp, but introduces another
portability issue.
Christian
next prev parent reply other threads:[~2007-11-10 21:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 15:26 [PATCH] Use getopt_long() instead of argp_parse() in grub-emu Christian Franke
2007-11-10 16:56 ` Marco Gerards
2007-11-10 21:45 ` Christian Franke [this message]
2007-11-18 11:04 ` Marco Gerards
2007-11-18 18:16 ` Christian Franke
2008-01-13 17:52 ` Marco Gerards
2008-01-14 21:37 ` Christian Franke
2008-01-15 11:13 ` Marco Gerards
2008-01-15 11:49 ` Robert Millan
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=47362686.6030407@t-online.de \
--to=christian.franke@t-online.de \
--cc=grub-devel@gnu.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.