Mailing List Archive: Building libgpg-error/libgcrypt/libtasn1/gnutls/gsasl without autoconf on uClinux

Building libgpg-error/libgcrypt/libtasn1/gnutls/gsasl without autoconf on uClinux

Aug 21, 2007, 4:14 AM

Post #1 of 3 (1902 views)

Hi all,

Sometimes it can be useful to build things without the autoconf
./configure machinery, and just use a simple and hand-maintained
makefile and config.h. This is needed to build things in older uClinux
environments.

I wrote some instructions on how to achieve this, see:

http://josefsson.org/uclinux/old/

The makefile/config.h aren't specific to uClinux, so if you for some
reason need to build these projects in some other environment, without
autoconf, the files may be useful.

Note that instructions for how to get these projects to work under a
modern uClinux (which supports the autoconf-machinery) is still
available, and is the preferred way to build under uClinux, see:

http://josefsson.org/uclinux/

Thanks,
Simon

_______________________________________________
Gcrypt-devel mailing list
Gcrypt-devel@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gcrypt-devel

Re: Building libgpg-error/libgcrypt/libtasn1/gnutls/gsasl without autoconf on uClinux [ In reply to ]

wk at gnupg

Aug 22, 2007, 3:04 AM

Post #2 of 3 (1781 views)

Permalink

On Tue, 21 Aug 2007 13:14, simon@josefsson.org said:

> Sometimes it can be useful to build things without the autoconf
> ./configure machinery, and just use a simple and hand-maintained
> makefile and config.h. This is needed to build things in older uClinux
> environments.

Is this due to libtool? Back in 2003 I was able to build gpg on uCLinux
for Coldfire; the configure invocation is still available in autogen.sh.

Salam-Shalom,

Werner

--
Die Gedanken sind frei. Auschnahmen regelt ein Bundeschgesetz.

_______________________________________________
Gcrypt-devel mailing list
Gcrypt-devel@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gcrypt-devel

Re: Building libgpg-error/libgcrypt/libtasn1/gnutls/gsasl without autoconf on uClinux [ In reply to ]

simon at josefsson

Aug 22, 2007, 3:21 AM

Post #3 of 3 (1803 views)

Permalink

Werner Koch <wk@gnupg.org> writes:

> On Tue, 21 Aug 2007 13:14, simon@josefsson.org said:
>
>> Sometimes it can be useful to build things without the autoconf
>> ./configure machinery, and just use a simple and hand-maintained
>> makefile and config.h. This is needed to build things in older uClinux
>> environments.
>
> Is this due to libtool? Back in 2003 I was able to build gpg on uCLinux
> for Coldfire; the configure invocation is still available in autogen.sh.

I didn't even get to libtool, I couldn't get the m68k gcc compiler from
2003 to work in ./configure -- it didn't use a.out as the default output
name, it didn't link to the proper libc by default, and there were many
more problems.

All those problems have been solved in modern versions of the toolchain
and uClinux. All our packages build fine using a simple ./configure
approach.

The only reason for anyone to want to look at this work if they are
using very broken toolchains that can never be supported by proper
./configure usage. Unfortunately, that situation seems to happen often
enough for me that it became useful to try and publish something
re-usable.

/Simon

_______________________________________________
Gcrypt-devel mailing list
Gcrypt-devel@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gcrypt-devel