Autoconf 2.69 and mingw

Thomas Dörfler Thomas.Doerfler at
Thu Mar 21 13:43:31 UTC 2013


I don't know about mingw auto* packaging, but for me this is another
indication that we should in the future leave the path of basing our
tools on the host packaging system.

Looking at this auto* version issue, the discussion about libraries not
being present on a certain host etc, we should move to provide our tools
as packaging-independent tarballs.

This means:
- building GCC and tools with statically linked libraries (no more
dependency on DLLs except libc)

What I would expect from this would be:
- have ONE tarball fit all Linux flavours (and for each major host family)
- get less problem reports due to packaging incompatibilites
- have repeatable results when compiling even on different hosts

I know this is a big step, but I don't really see what major reasons
stand against this.



On 21.03.2013 14:35, Gedare Bloom wrote:
> Hi,
> A user has complained that RTEMS fails to bootstrap using mingw on
> account of no existing autoconf 2.69 package being available in mingw.
> Is this the case, and can we either provide a package from RTEMS or
> another suitable workaround?
> I'm also given to understand there may be some issues with m4 on
> mingw, but I do not know the details.
> -Gedare
> _______________________________________________
> rtems-devel mailing list
> rtems-devel at

!!! Neue Adresse !!! New Address !!!
Embedded Brains GmbH
Thomas Doerfler        Dornierstr. 4
D-82178 Puchheim       Germany
email: Thomas.Doerfler at
Phone: +49-89-18 94 741-12
Fax:   +49-89-18 94 741-09

More information about the devel mailing list