Hi,
> >> "awkward fit" because you are using Autoconf in an awkward way.
> >> Using a tool an an un-intened way.
> >
> > It's really not that "unintended" IMHO. After all, Autoconf is all
> > about generating a Makefile from a template (Automake-generated or
> > handwritten) adjusted with some con
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
<[EMAIL PROTECTED]> writes:
>> "awkward fit" because you are using Autoconf in an awkward way. Using
>> a tool an an un-intened way.
>
> It's really not that "unintended" IMHO. After all, Autoconf is all about
> generating a Makefile from a template (
Hi,
> | Somewhere early during ./configure, the host type is checked. If it
> is | GNU (Hurd), an ordinary build is prepared. (Checking libs, using
> | automake-generated makefile etc.) However, if it's Linux, the
> behaviour | changes completely: All the ordinary checks are skipped;
> instead of
Hi,
> "awkward fit" because you are using Autoconf in an awkward way. Using
> a tool an an un-intened way.
It's really not that "unintended" IMHO. After all, Autoconf is all about
generating a Makefile from a template (Automake-generated or
handwritten) adjusted with some configuration options (p
"awkward fit" because you are using Autoconf in an awkward way.
Using a tool an an un-intened way. Like sweeping a walkway with
a beach towel when you have a broom nearby - it would work buy
it would be a bit awkward.
You would be making to much work for yourself and the result would
not be as rob
On 14-Feb-2005, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
| I'd like to know whether the following scenario is possible with
| Autoconf:
|
| Somewhere early during ./configure, the host type is checked. If it is
| GNU (Hurd), an ordinary build is prepared. (Checking libs, using
| automake-gene
On Thu, Feb 17, 2005 at 07:53:36PM +0100, [EMAIL PROTECTED] wrote:
> Hi,
>
> > > Somewhere early during ./configure, the host type is checked. If it is
> > > GNU (Hurd), an ordinary build is prepared. (Checking libs, using
> > > automake-generated makefile etc.) However, if it's Linux, the behavio
Hi,
> > Somewhere early during ./configure, the host type is checked. If it is
> > GNU (Hurd), an ordinary build is prepared. (Checking libs, using
> > automake-generated makefile etc.) However, if it's Linux, the behaviour
> > changes completely: All the ordinary checks are skipped; instead of an
On Mon, Feb 14, 2005 at 10:06:21PM +0100, [EMAIL PROTECTED] wrote:
> I'd like to know whether the following scenario is possible with
> Autoconf:
>
> Somewhere early during ./configure, the host type is checked. If it is
> GNU (Hurd), an ordinary build is prepared. (Checking libs, using
> automake
Hi,
I'd like to know whether the following scenario is possible with
Autoconf:
Somewhere early during ./configure, the host type is checked. If it is
GNU (Hurd), an ordinary build is prepared. (Checking libs, using
automake-generated makefile etc.) However, if it's Linux, the behaviour
changes co
> -Original Message-
> From: Akim Demaille [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 26, 2000 2:35 PM
> To: APatche; Autoconf List
> Subject: Re: More macro dispatching
>
>
>
> In order to properly implement the proposal of Alexandre (expr=fal
In order to properly implement the proposal of Alexandre (expr=false
when we can't trust it), more responsibility should be moved into
Mash, in particular things like _AC_INIT_PREPARE_ENVIRONMENT. It is a
good thing, it is independent from Autoconf and useful to any Mash
project (understand `aut
12 matches
Mail list logo
