From: Roger Pau Monne <roger.pau@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v2] libxl/build: print a warning if flex/bison are needed
Date: Wed, 25 Apr 2012 11:46:48 +0100 [thread overview]
Message-ID: <4F97D618.5010807@citrix.com> (raw)
In-Reply-To: <20375.54724.573559.470745@mariner.uk.xensource.com>
Ian Jackson escribió:
> Roger Pau Monne writes ("[PATCH v2] libxl/build: print a warning if flex/bison are needed"):
>> This patch adds better support for both Flex and Bison, which might
>> be needed to compile libxl. Now configure script sets BISON and FLEX
>> Makefile vars if bison and flex are found, but doesn't complain if
>> they are not found.
>>
>> Also, added some Makefile soccery to print a warning message if
>> Bison or Flex are needed but not found.
>
> Marvellous. I have applied this. I altered the warning message
> slightly:
>
> +ifeq ($(FLEX),)
> +%.c %.h:: %.l
> -+ $(warning Flex is needed to compile libxl, please install it and rerun \
> -+ configure)
> ++ $(warning Flex is needed to rebuild some libxl parsers and \
> ++ scanners, please install it and rerun configure)
> +endif
> +
> +ifeq ($(BISON),)
> +%.c %.h:: %.y
> -+ $(warning Bison is needed to compile libxl, please install it an rerun \
> -+ configure)
> ++ $(warning Bison is needed to rebuild some libxl parsers and \
> ++ scanners, please install it an rerun configure)
> +endif
> +
>
> I trust that's OK.
Sure, thanks!
> Thanks,
> Ian.
prev parent reply other threads:[~2012-04-25 10:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 9:14 [PATCH v2] libxl/build: print a warning if flex/bison are needed Roger Pau Monne
2012-04-25 10:45 ` Ian Jackson
2012-04-25 10:46 ` Roger Pau Monne [this message]
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=4F97D618.5010807@citrix.com \
--to=roger.pau@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.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.