Mail Archives: djgpp-workers/2003/09/27/06:51:43
Hello.
I don't think I can maintain the DJGPP packages of automake anymore for two
reasons:
* I don't really have much time to spend on DJGPP these days. I'm going to
have to restrict my time to getting DJGPP 2.04 and coreutils 5.0 out,
otherwise it'll never happen. (Actually, I'll probably have to concentrate on
just DJGPP 2.04.)
* I don't have the necessary copyright paperwork to contribute to GNU projects
from my new company. I think it's unlikely I'll get that paperwork anytime
soon.
automake 1.7.7 shouldn't require much work to package. To package automake
1.7.x, I usually only have to:
* write new DSMs, so they can be installed with DJGPP's package managers;
* run the test suite, to check everything is OK;
* re-run a couple of tests by hand, since a couple fail due to bugs in our
port of autoconf 2.57 (*).
(*) I don't know what the bug is, but spurious ^M characters appear sometimes.
Note that I haven't tested automake 1.7.x with short filenames.
I expect that automake 1.8 (currently automake CVS trunk) will require some
changes to work with DJGPP. Alexandre Duret-Lutz (the automake maintainer) is
very DJGPP-friendly, so it probably won't require many changes. I haven't
tried it with DJGPP, so maybe it will work out of the box. ;)
automake 1.8 will be a big release. libtool 1.6 will depend on automake 1.8
which will depend on autoconf 2.58. These will all need porting, so that we
don't fall behind on autotools again. (I originally ported autoconf 2.57 (**)
and automake 1.7.x, so I could modify & build coreutils 5.0 with DJGPP.)
(**) Tim van Holder did most of the work. I just patched it a little bit more
and packaged it.
So does anyone fancy taking over maintainership of the DJGPP packages of
automake?
Thanks, bye, Rich =]
Alexandre Duret-Lutz wrote:
>
> We're pleased to announce the release of Automake 1.7.7.
>
> Automake is a tool for automatically generating `Makefile.in's
> suitable for use with Autoconf, compliant with the GNU Makefile
> standards, and portable to various make implementations.
>
> This is a bug fix release. The list of bug fixes is appended.
>
> You can find the new release here:
>
> ftp://sources.redhat.com/pub/automake/automake-1.7.7.tar.bz2
> ftp://sources.redhat.com/pub/automake/automake-1.7.7.tar.gz
>
> within a few days it should also appear at
>
> ftp://ftp.gnu.org/gnu/automake/automake-1.7.7.tar.bz2
> ftp://ftp.gnu.org/gnu/automake/automake-1.7.7.tar.gz
>
> as well as on the sources and GNU mirrors listed here:
>
> http://www.gnu.org/order/ftp.html
> http://sources.redhat.com/mirrors.html
>
> Finally, here are the MD5 checksums:
>
> 4323c25644ed092c3d4fdfef434ab28d automake-1.7.7.tar.bz2
> dd7dab16f5d3f30d3e3724cde71cc4c7 automake-1.7.7.tar.gz
>
> This release is also GPG signed. You can download the signatures
> by appending ".asc" to the URLs.
>
> Please report bugs to <bug-automake AT gnu DOT org>.
>
> Bugs fixed in 1.7.7:
> * The implementation of automake's --no-force option is unreliable,
> so this option is ignored in this version. A real fix will appear in
> Automake 1.8. (Debian Bug #206299)
> * AM_PATH_PYTHON: really check the whole list of interpreters if no
> argument is given. (PR/399)
> * Do not warn about leading `_' in variable names, even with -Wportability.
> * Support user redefinitions of TEXINFO_TEX.
> * depcomp: support AIX Compiler version 6.
> * Fix missing rebuilds during `make dist' with BSD make.
> (Could produce tarballs containing out-of-date files.)
> * Resurrect multilib support.
> * Noteworthy manual updates:
> - Extending aclocal: how to write m4 macros that won't trigger warnings
> with Automake 1.8.
> - A Shared Library: Rewrite and split into subsections.
>
> --
> Alexandre Duret-Lutz
>
> ------------------------------------------------------------------------------
> Part 1.2Type: application/pgp-signature
--
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]
- Raw text -