[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: master branch --- build problems
From: |
lfinsto |
Subject: |
Re: master branch --- build problems |
Date: |
Thu, 29 Jul 2010 16:45:48 +0200 |
User-agent: |
SquirrelMail/1.4.20 |
On Thu, July 29, 2010 4:07 pm, Simon Josefsson wrote:
> address@hidden writes:
>> I had considerable difficulty getting the master branch to build, but I
finally succeeded, though I had to comment some things out, which isn't
so
>> good.
> This is strange, I have bootstrapped GnuTLS on completely freshly
installed Debian and Ubuntu systems without problems.
I'm not actually very satisfied with OpenSuse and I dislike Suse
Enterprise Edition, but I have to use them. It doesn't surprise me that
I'm having problems.
> Instead of looking at patches to solve some intermediate problem, can
you quote the complete output you get by doing the steps describe by
README-alpha on your machine? I.e:
> $ # install all dependencies according to README-alpha
> $ git clone git://git.savannah.gnu.org/gnutls.git
> $ cd gnutls
> $ make
> $ make
git clone git://git.savannah.gnu.org/gnutls.git master_test
[...]
address@hidden:~/gnutls_dev/master_test> make bootstrap
for f in lib/po/*.po.in; do \
cp $f `echo $f | sed 's/.in//'`; \
done
mv lib/build-aux/config.rpath lib/build-aux/config.rpath-
test -f ./configure || autoreconf --install
configure.ac:66: error: AC_CHECK_SIZEOF: requires literal arguments
../../lib/autoconf/types.m4:765: AC_CHECK_SIZEOF is expanded from...
lib/m4/hooks.m4:23: LIBGNUTLS_HOOKS is expanded from...
configure.ac:66: the top level
autom4te: /usr/bin/m4 failed with exit status: 1
aclocal: /usr/bin/autom4te failed with exit status: 1
autoreconf: aclocal failed with exit status: 1
make: *** [autoreconf] Error 1
address@hidden:~/gnutls_dev/master_test>
Commented-out AC_CHECK_SIZEOF(void *) in
~/gnutls_dev/master_test/lib/m4/hooks.m4
address@hidden:~/gnutls_dev/master_test> make bootstrap
for f in lib/po/*.po.in; do \
cp $f `echo $f | sed 's/.in//'`; \
done
mv lib/build-aux/config.rpath lib/build-aux/config.rpath-
mv: cannot stat `lib/build-aux/config.rpath': No such file or directory
make: *** [autoreconf] Error 1
address@hidden:~/gnutls_dev/master_test> autoreconf
gl/m4/intl.m4:242: warning: macro `AM_ICONV' not found in library
configure.ac:34: required file `build-aux/config.guess' not found
configure.ac:34: `automake --add-missing' can install `config.guess'
configure.ac:39: required file `build-aux/config.rpath' not found
configure.ac:34: required file `build-aux/config.sub' not found
configure.ac:34: `automake --add-missing' can install `config.sub'
configure.ac:29: required file `build-aux/install-sh' not found
configure.ac:29: `automake --add-missing' can install `install-sh'
configure.ac:37: required file `build-aux/ltmain.sh' not found
configure.ac:29: required file `build-aux/missing' not found
configure.ac:29: `automake --add-missing' can install `missing'
gcrypt/Makefile.am: required file `build-aux/depcomp' not found
gcrypt/Makefile.am: `automake --add-missing' can install `depcomp'
Makefile.am: required file `./INSTALL' not found
Makefile.am: `automake --add-missing' can install `INSTALL'
configure.ac:41: required file `./ABOUT-NLS' not found
autoreconf: automake failed with exit status: 1
address@hidden:~/gnutls_dev/master_test>
I didn't remember, but this is why I switched to `libtoolize', `aclocal',
etc.
>> In /lib/Makefile.am, I had to remove `po' from SUBDIRS. The error that I
>> got when it was included was this:
>> config.status: error: cannot find input file: `po/Makefile.in.in'
configure: error: ./configure failed for lib
> It's generated by the bootstrap process. There must have been an
earlier problem. Most of your problems also seems to be a consequence
of broken bootstrapping.
> Yep. Before working on fixing warnings, I suggest using the most recent
> GCC version to make sure you aren't fixing broken compiler warnings.
I'm using gcc (SUSE Linux) 4.3.2 [gcc-4_3-branch revision 141291].
I've read that installing glibc is somewhat of a challenge, but I suppose
I could try to install the current stable of release (or releases?) of
glibc and GCC in a non-standard location.
>> I would also be interested to know what versions of autoconf, automake and
>> libtool you have installed on the systems you're using. I assume
everything works together smoothly on your systems.
> I have autoconf 2.65, automake 1.11.1, and libtool 2.2.6b. Straight
from > Debian testing.
So, nothing obviously old.
Laurence
-------------------------------------------------------------
Laurence Finston
Gesellschaft fuer wissenschaftliche Datenverarbeitung mbH
Am Fassberg 11
37077 Goettingen
Telefon: +49 551 201-1882
E-Mail: address@hidden