From gp at familiehaase.de Fri Sep 17 00:05:15 2004 From: gp at familiehaase.de (Gerrit P. Haase) Date: Fri, 17 Sep 2004 00:05:15 +0200 Subject: [Help-gnutls] cannot build outside the source directory Message-ID: <1181369777.20040917000515@familiehaase.de> gcc -DHAVE_CONFIG_H -I. -I/ftproot/pub/gnome/gnutls/gnutls-1.0.20/lib -I.. -I../libextra -Iminitasn1/ -I../libextra/openpgp/ -I../libextra/opencdk -Ix509/ -I../includes -I/usr/include -I/usr/include -g0 -O3 -D_REENTRANT -D_THREAD_SAFE -O2 -finline-functions -pipe -MT gnutls_handshake.lo -MD -MP -MF .deps/gnutls_handshake.Tpo -c /ftproot/pub/gnome/gnutls/gnutls-1.0.20/lib/gnutls_handshake.c -o .libs/gnutls_handshake.o /ftproot/pub/gnome/gnutls/gnutls-1.0.20/lib/gnutls_handshake.c:49:21: ext_srp.h: No such file or directory make[3]: *** [gnutls_handshake.lo] Error 1 $ find . -name "ext_srp.h" ./gnutls-1.0.20/libextra/ext_srp.h This are the bad INCLUDE flags: -I.. -I../libextra -Iminitasn1/ -I../libextra/openpgp/ -I../libextra/opencdk -Ix509/ -I../includes Please use no relative paths, use full paths like this in your Makefile.am: INCLUDES = -I$(top_srcdir)/libextra -I$(top_srcdir)/lib/minitasn1/ -I$(top_srcdir)/libextra/openpgp/ -I$(top_srcdir)/libextra/opencdk -I$(top_srcdir)/lib/x509/ -I$(top_srcdir)/includes $(LIBOPENCDK_CFLAGS) $(LIBTASN1_CFLAGS) $(LIBGCRYPT_CFLAGS) Why do you force the user to build inside the source tree? Do you build inside the source tree? Why??? Gerrit -- =^..^= From jas at extundo.com Fri Sep 17 00:37:31 2004 From: jas at extundo.com (Simon Josefsson) Date: Fri, 17 Sep 2004 00:37:31 +0200 Subject: [Help-gnutls] Re: cannot build outside the source directory References: <1181369777.20040917000515@familiehaase.de> Message-ID: "Gerrit P. Haase" writes: > gcc -DHAVE_CONFIG_H -I. -I/ftproot/pub/gnome/gnutls/gnutls-1.0.20/lib -I.. -I../libextra -Iminitasn1/ -I../libextra/openpgp/ -I../libextra/opencdk -Ix509/ -I../includes -I/usr/include -I/usr/include -g0 -O3 -D_REENTRANT -D_THREAD_SAFE -O2 -finline-functions -pipe -MT gnutls_handshake.lo -MD -MP -MF .deps/gnutls_handshake.Tpo -c /ftproot/pub/gnome/gnutls/gnutls-1.0.20/lib/gnutls_handshake.c -o .libs/gnutls_handshake.o > /ftproot/pub/gnome/gnutls/gnutls-1.0.20/lib/gnutls_handshake.c:49:21: ext_srp.h: No such file or directory > make[3]: *** [gnutls_handshake.lo] Error 1 > > $ find . -name "ext_srp.h" > ./gnutls-1.0.20/libextra/ext_srp.h > > This are the bad INCLUDE flags: > > -I.. -I../libextra -Iminitasn1/ -I../libextra/openpgp/ -I../libextra/opencdk -Ix509/ -I../includes > > Please use no relative paths, use full paths like this in your > Makefile.am: > INCLUDES = -I$(top_srcdir)/libextra -I$(top_srcdir)/lib/minitasn1/ -I$(top_srcdir)/libextra/openpgp/ -I$(top_srcdir)/libextra/opencdk -I$(top_srcdir)/lib/x509/ -I$(top_srcdir)/includes $(LIBOPENCDK_CFLAGS) $(LIBTASN1_CFLAGS) $(LIBGCRYPT_CFLAGS) > > > Why do you force the user to build inside the source tree? > Do you build inside the source tree? Why??? Hello, and thanks for the report. I believe this has been fixed in the development branch. If you need it fixed in the stable branch too, please send a (tested) patch to speed up the process. Thanks, Simon From gp at familiehaase.de Fri Sep 17 01:42:55 2004 From: gp at familiehaase.de (Gerrit P. Haase) Date: Fri, 17 Sep 2004 01:42:55 +0200 Subject: [Help-gnutls] Re: cannot build outside the source directory In-Reply-To: References: <1181369777.20040917000515@familiehaase.de> Message-ID: <114477797.20040917014255@familiehaase.de> Hello Simon, nice to meet you;) >> Why do you force the user to build inside the source tree? >> Do you build inside the source tree? Why??? > Hello, and thanks for the report. I believe this has been fixed in > the development branch. If you need it fixed in the stable branch > too, please send a (tested) patch to speed up the process. Ok, a patch against the currenty release tarball is attached. I compiledand installed outside the source directory with this patch applied. I have not done much testing of the binaries, but sionce here only the build procedure is affected, I think it should be ok. Gerrit -- =^..^= -------------- next part -------------- A non-text attachment was scrubbed... Name: gnutls-1.0.20.patch Type: application/octet-stream Size: 5653 bytes Desc: not available URL: From gp at familiehaase.de Fri Sep 17 02:38:29 2004 From: gp at familiehaase.de (Gerrit P. Haase) Date: Fri, 17 Sep 2004 02:38:29 +0200 Subject: [Help-gnutls] Re: cannot build outside the source directory In-Reply-To: <114477797.20040917014255@familiehaase.de> References: <1181369777.20040917000515@familiehaase.de> <114477797.20040917014255@familiehaase.de> Message-ID: <451099384.20040917023829@familiehaase.de> Hallo Gerrit, Am Freitag, 17. September 2004 um 01:42 schriebst du: > Hello Simon, > nice to meet you;) >>> Why do you force the user to build inside the source tree? >>> Do you build inside the source tree? Why??? >> Hello, and thanks for the report. I believe this has been fixed in >> the development branch. If you need it fixed in the stable branch >> too, please send a (tested) patch to speed up the process. > Ok, a patch against the currenty release tarball is attached. I > compiledand installed outside the source directory with this patch > applied. I have not done much testing of the binaries, but sionce > here only the build procedure is affected, I think it should be ok. Hmm, what is interesting about the patch is, that libgnutls-openssl doesn't need to include libcrypto for the link, I wonder why there is 'openssl' in the name. Gerrit -- =^..^= From jas at extundo.com Fri Sep 17 11:16:22 2004 From: jas at extundo.com (Simon Josefsson) Date: Fri, 17 Sep 2004 11:16:22 +0200 Subject: [Help-gnutls] Re: cannot build outside the source directory References: <1181369777.20040917000515@familiehaase.de> <114477797.20040917014255@familiehaase.de> Message-ID: "Gerrit P. Haase" writes: > Hello Simon, > > > nice to meet you;) > >>> Why do you force the user to build inside the source tree? >>> Do you build inside the source tree? Why??? > >> Hello, and thanks for the report. I believe this has been fixed in >> the development branch. If you need it fixed in the stable branch >> too, please send a (tested) patch to speed up the process. > > Ok, a patch against the currenty release tarball is attached. I > compiledand installed outside the source directory with this patch > applied. I have not done much testing of the binaries, but sionce > here only the build procedure is affected, I think it should be ok. There were some unrelated changes in your patch that added -no-undefined to LDFLAGS, so I improved the development branch and back ported it. I'll roll a release candidate eventually, so you can test it, or you could try CVS. Thanks, Simon From gp at familiehaase.de Fri Sep 17 11:41:03 2004 From: gp at familiehaase.de (Gerrit P. Haase) Date: Fri, 17 Sep 2004 11:41:03 +0200 Subject: [Help-gnutls] Re: cannot build outside the source directory In-Reply-To: References: <1181369777.20040917000515@familiehaase.de> <114477797.20040917014255@familiehaase.de> Message-ID: <1825570344.20040917114103@familiehaase.de> Hello Simon, >> Ok, a patch against the currenty release tarball is attached. I >> compiledand installed outside the source directory with this patch >> applied. I have not done much testing of the binaries, but sionce >> here only the build procedure is affected, I think it should be ok. > There were some unrelated changes in your patch that added > -no-undefined to LDFLAGS, so I improved the development branch and > back ported it. I'll roll a release candidate eventually, so you can > test it, or you could try CVS. The -no-undefined flags should do no harm if you have the required libraries in place since they are needed to test the binaries anyway. Generally I think adding -no-undefined to all shared library builds leads to fewer errors, i.e. when a package should be portable across several platforms. Gerrit -- =^..^= From jas at extundo.com Fri Sep 17 12:09:32 2004 From: jas at extundo.com (Simon Josefsson) Date: Fri, 17 Sep 2004 12:09:32 +0200 Subject: [Help-gnutls] Re: cannot build outside the source directory References: <1181369777.20040917000515@familiehaase.de> <114477797.20040917014255@familiehaase.de> <1825570344.20040917114103@familiehaase.de> Message-ID: "Gerrit P. Haase" writes: > Hello Simon, > >>> Ok, a patch against the currenty release tarball is attached. I >>> compiledand installed outside the source directory with this patch >>> applied. I have not done much testing of the binaries, but sionce >>> here only the build procedure is affected, I think it should be ok. > >> There were some unrelated changes in your patch that added >> -no-undefined to LDFLAGS, so I improved the development branch and >> back ported it. I'll roll a release candidate eventually, so you can >> test it, or you could try CVS. > > The -no-undefined flags should do no harm if you have the required > libraries in place since they are needed to test the binaries anyway. > Generally I think adding -no-undefined to all shared library builds > leads to fewer errors, i.e. when a package should be portable across > several platforms. I'll look into adding it. Btw, daily snapshots of GnuTLS should now be available from: http://josefsson.org/daily/gnutls/ Thanks, Simon