All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: john.levon@sun.com, xen-devel@lists.xensource.com
Subject: Re: [PATCH] Fix xenmon/xentrace compile on Solaris
Date: Tue, 07 Aug 2007 14:48:38 +0100	[thread overview]
Message-ID: <C2DE36C6.13B58%keir@xensource.com> (raw)
In-Reply-To: <ae465d2d2b2ec9ab3159.1186492441@xenbld>

That's a lot of code to include verbatim in our repository, especially for
two non-essential build targets.

There are two potential better alternatives:
  1. Don't use argp at all in xentrace/xenmon -- do they really need
super-advanced argument parsing such that getopt will not suffice? As
low-level not-usually-user-visible daemons I would say that porting them to
getopt would be acceptable even if the command-line option syntax needs
changing a little to cleanly do so.
  2. Is libargp available separately from libc? If so you could require
users to install it if they wish to build xentrace/xenmon. Or you could
maintain the libargp you posted out-of-tree.

 -- Keir

On 7/8/07 14:14, "john.levon@sun.com" <john.levon@sun.com> wrote:

> # HG changeset patch
> # User john.levon@sun.com
> # Date 1186492378 25200
> # Node ID ae465d2d2b2ec9ab31598511fb35814ba6ab5602
> # Parent  1ddb3b21f4d8a6b449580ae45cf707f4b43198f9
> Fix xenmon/xentrace compile on Solaris
> 
> The argp interface is only present in GNU libc. Include a local copy when
> compiling on Solaris, and fix a couple of a trivial compile problems.
> 
> Signed-off-by: Tariq Magdon-Ismail <tariqmi@sun.com>

  reply	other threads:[~2007-08-07 13:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-07 13:14 [PATCH] Fix xenmon/xentrace compile on Solaris john.levon
2007-08-07 13:48 ` Keir Fraser [this message]
2007-08-07 13:56   ` John Levon
2007-08-09  3:24     ` Mark Williamson

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=C2DE36C6.13B58%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=john.levon@sun.com \
    --cc=xen-devel@lists.xensource.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.
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.