Re: [MinGW-dvlpr] FW: src/winsup/mingw ChangeLog configure

[Keith Marshall <keithmarshall@us...>]

Danny Smith wrote, quoting Chris Sutcliffe:
> > Does AC_CONFIG_AUX_DIR even need to be set?  In the
> > sourceware src directory, ../.. would be the root src
> > directory.  However, since I don't really care about the rest
> > of the src directory (other than w32api), and the files are
> > present in the runtime directory, shouldn't srcdir be sufficient?
>
> I've just regenerated configure  with AC_CONFIG_AUX_DIR line removed
> completely and rebuilt and installed  with no problem.  So I think your
> right.  I'll do a few more tests to make syre that it rebuilds under
> cygwin as well.

Danny, Chris,

Quoting the autoconf-2.59 manual (texinfo):
|  Packages that do manual configuration or use the `install' program
|might need to tell `configure' where to find some other shell scripts
|by calling `AC_CONFIG_AUX_DIR', though the default places it looks are
|correct for most cases.
|
| - Macro: AC_CONFIG_AUX_DIR (DIR)
|     Use the auxiliary build tools (e.g., `install-sh', `config.sub',
|     `config.guess', Cygnus `configure', Automake and Libtool scripts
|     etc.) that are in directory DIR.  These are auxiliary files used
|     in configuration.  DIR can be either absolute or relative to
|     `SRCDIR'.  The default is `SRCDIR' or `SRCDIR/..' or
|     `SRCDIR/../..', whichever is the first that contains `install-sh'.

Most packages seem to distribute install-sh in the top srcdir, which 
means that AC_CONFIG_AUX_DIR would not be required; certainly, adding it 
with only a reference which matches any of the stated defaults would seem 
rather superfluous.

If configure.ac, (or configure.in, if we haven't updated to modern 
semantics), invokes AC_PROG_INSTALL, then configure will complain if it 
can't find install-sh.  If it doesn't do so, when AC_CONFIG_AUX_DIR is 
not used, then it is not required.

Regards,
Keith.

Re: [MinGW-dvlpr] make 3.81

[Chris Sutcliffe <ir0nh34d@gm...>]

> > Yes, go ahead.  I was thinking of a mingwPORT and then decided against
> > that as it is one of the base utilities needed.  As for -j I remember
> > on the make-gw32 list there was talk of some patches to try to make it
> > work for windows.  It does require multiple CPU in the box to make it
> > worth doing though.
>
> Done.  Before I upload it to SourceForge, can I get someone to please
> check the packaging to confirm that's it acceptable?
>
> http://emergedesktop.org/mingw/mingw32-make-3.81-1-src.tar.gz
> http://emergedesktop.org/mingw/mingw32-make-3.81-1.tar.gz
>
> Like version 3.80.0-3, I've added a 'doc/PORTNOTES' in the binary
> tarball explaining how the binary was produced.

I'm assuming that no news is good news, and the packaging is fine.
Barring an emails stating the opposite, I'll upload these builds to
SourceForge tomorrow.

Chris

-- 
Chris Sutcliffe
http://ir0nh34d.blogspot.com
http://emergedesktop.org

Re: [MinGW-dvlpr] FW: src/winsup/mingw ChangeLog configure

[Chris Sutcliffe <ir0nh34d@gm...>]

> > I've just regenerated configure  with AC_CONFIG_AUX_DIR line removed
> > completely and rebuilt and installed  with no problem.  So I
> > think your
> > right.  I'll do a few more tests to make syre that it rebuilds under
> > cygwin as well.
>
> Committed to cvs.
>         * configure.in (AC_CONFIG_AUX_DIR): Remove.
>         * configure: Regenerate.
> >  Danny

Cheers!

Chris

-- 
Chris Sutcliffe
http://ir0nh34d.blogspot.com
http://emergedesktop.org