autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Expanded rules for scripts


From: Bernard Dautrevaux
Subject: RE: Expanded rules for scripts
Date: Fri, 15 Dec 2000 15:20:59 +0100

> -----Original Message-----
> From: Pavel Roskin [mailto:address@hidden
> Sent: Friday, December 15, 2000 1:56 PM
> To: Akim Demaille
> Cc: Alexandre Oliva; Bernard Dautrevaux; address@hidden
> Subject: Re: Expanded rules for scripts
> 
> 
> Hello!
> 
> Let's finally move the discussion from autoconf-pathes.
> 
> > Well there was much left in ``properly''.  My understanding was that
> > Pavel found a host where make was very happy with just those suffix
> > rules, but broken when we introduced extra dependencies.  I don't
> > remember whether it was
> >
> > .sh: configure.in
> >         # do sth
> 
> Even GNU make would not let you do it.

This is indeed definitely wrong and I don't know of any make where I've seen
this working but, to be honest, discovering once it was not working I
stopped trying :-)

> 
> > .sh: configure.in
> >         # do sth
> > autoconf.sh: some-other-dependency
> 
> This was used in Autoconf.

Are you sure? the ".sh: configure.in" dependency bothers me...

Anyway the right way to go, and I've never seen a make where it fails, would
be:

.sh:
        # do sth

autoconf: configure.in some-other-dependency

What I know cause problems with some (old?) makes is listing "autoconf.sh"
as an explicit dependency for "autoconf"; some makes could then no more
expand the suffix rule.

Regards,

        Bernard

--------------------------------------------
Bernard Dautrevaux
Microprocess Ingenierie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel:    +33 (0) 1 47 68 80 80
Fax:    +33 (0) 1 47 88 97 85
e-mail: address@hidden
                address@hidden
-------------------------------------------- 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]