Re: guile-1.8.6 build core dumps (autoconf issue ?)
Mel Flynn wrote: On Thursday 02 April 2009 03:01:53 manish jain wrote: Hi Mel, Sorry, I was away for work. Here is what I think you want : /usr/ports/lang/guile # make -C /usr/ports/lang/guile -V CONFIGURE_ENV -V CONFIGURE_ARGS CPPFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib" SHELL=/bin/sh CONFIG_SHELL=/bin/sh MAKE=gmake AUTOCONF=/usr/local/bin/autoconf-2.62 AUTOHEADER=/usr/local/bin/autoheader-2.62 AUTOIFNAMES=/usr/local/bin/ifnames-2.62 AUTOM4TE=/usr/local/bin/autom4te-2.62 AUTORECONF=/usr/local/bin/autoreconf-2.62 AUTOSCAN=/usr/local/bin/autoscan-2.62 AUTOUPDATE=/usr/local/bin/autoupdate-2.62 AUTOCONF_VERSION=262 lt_cv_sys_max_cmd_len=262144 --prefix=/usr/local ${_LATE_CONFIGURE_ARGS} Hmmm...last straw: find /usr/local -name '*.la' -exec grep -- '-llthread' {} + To explain: something guile needs is built with linux-threads yet this is not correctly handled and the resulting binaries are flawed, most likely because another library that guile needs uses FreeBSD native threads. On FreeBSD threaded linking is done with -pthread linker flag which pulls in the correct threading library (on 7.0 and above libthr, on 6.x and earlier libpthread). Hi Mel, There is no output. /root # find /usr/local -name '*.la' -exec grep -- '-llthread' {} + /root # -- Thank you and Regards Manish Jain invalid.poin...@gmail.com +91-99830-62246 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: guile-1.8.6 build core dumps (autoconf issue ?)
On Thursday 02 April 2009 03:01:53 manish jain wrote: > Hi Mel, > > Sorry, I was away for work. > > Here is what I think you want : > > /usr/ports/lang/guile # make -C /usr/ports/lang/guile -V CONFIGURE_ENV > -V CONFIGURE_ARGS > CPPFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib" > SHELL=/bin/sh CONFIG_SHELL=/bin/sh MAKE=gmake > AUTOCONF=/usr/local/bin/autoconf-2.62 > AUTOHEADER=/usr/local/bin/autoheader-2.62 > AUTOIFNAMES=/usr/local/bin/ifnames-2.62 > AUTOM4TE=/usr/local/bin/autom4te-2.62 > AUTORECONF=/usr/local/bin/autoreconf-2.62 > AUTOSCAN=/usr/local/bin/autoscan-2.62 > AUTOUPDATE=/usr/local/bin/autoupdate-2.62 AUTOCONF_VERSION=262 > lt_cv_sys_max_cmd_len=262144 > --prefix=/usr/local ${_LATE_CONFIGURE_ARGS} Hmmm...last straw: find /usr/local -name '*.la' -exec grep -- '-llthread' {} + To explain: something guile needs is built with linux-threads yet this is not correctly handled and the resulting binaries are flawed, most likely because another library that guile needs uses FreeBSD native threads. On FreeBSD threaded linking is done with -pthread linker flag which pulls in the correct threading library (on 7.0 and above libthr, on 6.x and earlier libpthread). -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: guile-1.8.6 build core dumps (autoconf issue ?)
On Tuesday 31 March 2009 19:30:59 manish jain wrote: > Mel Flynn wrote: > > On Tuesday 31 March 2009 19:02:56 manish jain wrote: > >> Mel Flynn wrote: > >>> On Tuesday 31 March 2009 08:15:56 manish jain wrote: > Hi, > > I portsnapped the lastest tarball a couple of days back. Doing a build > > in lang/guile (1.8.6) core dumps with the following message : > > Making all in libguile > > gmake[2]: Entering directory > > `/usr/ports/lang/guile/work/guile-1.8.6/libguile' cd .. && /bin/sh > > ./config.status libguile/Makefile depfiles > > config.status: creating libguile/Makefile > > config.status: executing depfiles commands > > gmake[2]: Leaving directory > > `/usr/ports/lang/guile/work/guile-1.8.6/libguile' gmake[2]: Entering > > directory `/usr/ports/lang/guile/work/guile-1.8.6/libguile' > > Generating libpath.h... > > sed < ./version.h.in > version.h.tmp \ > > -e s:@-GUILE_MAJOR_VERSION-@:1: \ > > -e s:@-GUILE_MINOR_VERSION-@:8: \ > > -e s:@-GUILE_MICRO_VERSION-@:6: > > mv version.h.tmp version.h > > if [ "no" = "yes" ]; then \ > > cc -DHAVE_CONFIG_H -I.. -I.. -I.. -c -o gen-scmconfig.o > > gen-scmconfig.c; \ else \ > > cc -DHAVE_CONFIG_H -I.. -I.. -I.. > > -I/usr/local/include -O2 > > -fno-strict-aliasing -pipe -Wall -Wmissing-prototypes -Werror -c -o > > gen-scmconfig.o gen-scmconfig.c; \ fi > > if [ "no" = "yes" ]; then \ > > cc -o gen-scmconfig gen-scmconfig.o; \ > > else \ > > /bin/sh ../libtool --tag=CC --mode=link cc -O2 > > -fno-strict-aliasing -pipe -Wall -Wmissing-prototypes -Werror > > -L/usr/local/lib -o > > gen-scmconfig gen-scmconfig.o -llthread -lgmp -lcrypt -lm -lltdl ; \ > > fi libtool: link: cc -O2 -fno-strict-aliasing -pipe -Wall > > -Wmissing-prototypes -Werror -o gen-scmconfig gen-scmconfig.o > > -L/usr/local/lib -llthread /usr/local/lib/libgmp.so -lcrypt -lm > >>> > >>> vs mine: > >>> libtool: link: /usr/local/libexec/ccache/world-cc -O2 > >>> -fno-strict-aliasing - pipe -Wall -Wmissing-prototypes -Werror -o > >>> gen-scmconfig gen-scmconfig.o - L/usr/local/lib > >>> /usr/local/lib/libgmp.so -lcrypt -lm /usr/local/lib/libltdl.so > >>> -Wl,-rpath -Wl,/usr/local/lib -Wl,-rpath -Wl,/usr/local/lib > >>> > >>> Where does -llthread come from? > >> > >> Hi Mel, > >> > >> I can't really answer the question. I just ran 'make install clean'. I > >> am attaching the log file, just in case you are able to spot something. > > > > I think config.log is more helpful, as it would show LDFLAGS and detected > > threading library. > > Hi Mel, > > There sure is plenty in config.log to interest you. Attached is the log > in zip format. No mention of -llthread there. It links so I'm assuming you have devel/linuxthreads installed. Could you show: make -C /usr/ports/lang/guild -V CONFIGURE_ENV -V CONFIGURE_ARGS It must come from somewhere...Your environment and /etc/make.conf are free from LDFLAGS or LIBS according to config.log. > Could you please clear up one question : do the freebsd-question forum > rules allow attachments ? I am actually using 'Reply to sender' rather > than 'Reply to all' because of this doubt. On -questions attachments are stripped to the best of my knowledge. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: guile-1.8.6 build core dumps (autoconf issue ?)
On Tuesday 31 March 2009 19:02:56 manish jain wrote: > Mel Flynn wrote: > > On Tuesday 31 March 2009 08:15:56 manish jain wrote: > >> Hi, > >> > >> I portsnapped the lastest tarball a couple of days back. Doing a build > >> > >> in lang/guile (1.8.6) core dumps with the following message : > >>> Making all in libguile > >>> gmake[2]: Entering directory > >>> `/usr/ports/lang/guile/work/guile-1.8.6/libguile' cd .. && /bin/sh > >>> ./config.status libguile/Makefile depfiles > >>> config.status: creating libguile/Makefile > >>> config.status: executing depfiles commands > >>> gmake[2]: Leaving directory > >>> `/usr/ports/lang/guile/work/guile-1.8.6/libguile' gmake[2]: Entering > >>> directory `/usr/ports/lang/guile/work/guile-1.8.6/libguile' Generating > >>> libpath.h... > >>> sed < ./version.h.in > version.h.tmp \ > >>> -e s:@-GUILE_MAJOR_VERSION-@:1: \ > >>> -e s:@-GUILE_MINOR_VERSION-@:8: \ > >>> -e s:@-GUILE_MICRO_VERSION-@:6: > >>> mv version.h.tmp version.h > >>> if [ "no" = "yes" ]; then \ > >>> cc -DHAVE_CONFIG_H -I.. -I.. -I.. -c -o gen-scmconfig.o > >>> gen-scmconfig.c; \ else \ > >>> cc -DHAVE_CONFIG_H -I.. -I.. -I.. -I/usr/local/include -O2 > >>> -fno-strict-aliasing -pipe -Wall -Wmissing-prototypes -Werror -c -o > >>> gen-scmconfig.o gen-scmconfig.c; \ fi > >>> if [ "no" = "yes" ]; then \ > >>> cc -o gen-scmconfig gen-scmconfig.o; \ > >>> else \ > >>> /bin/sh ../libtool --tag=CC --mode=link cc -O2 > >>> -fno-strict-aliasing -pipe -Wall -Wmissing-prototypes -Werror > >>> -L/usr/local/lib -o > >>> gen-scmconfig gen-scmconfig.o -llthread -lgmp -lcrypt -lm -lltdl ; \ > >>> fi libtool: link: cc -O2 -fno-strict-aliasing -pipe -Wall > >>> -Wmissing-prototypes -Werror -o gen-scmconfig gen-scmconfig.o > >>> -L/usr/local/lib -llthread /usr/local/lib/libgmp.so -lcrypt -lm > > > > vs mine: > > libtool: link: /usr/local/libexec/ccache/world-cc -O2 > > -fno-strict-aliasing - pipe -Wall -Wmissing-prototypes -Werror -o > > gen-scmconfig gen-scmconfig.o - L/usr/local/lib /usr/local/lib/libgmp.so > > -lcrypt -lm /usr/local/lib/libltdl.so -Wl,-rpath -Wl,/usr/local/lib > > -Wl,-rpath -Wl,/usr/local/lib > > > > Where does -llthread come from? > > Hi Mel, > > I can't really answer the question. I just ran 'make install clean'. I > am attaching the log file, just in case you are able to spot something. I think config.log is more helpful, as it would show LDFLAGS and detected threading library. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: guile-1.8.6 build core dumps (autoconf issue ?)
On Tuesday 31 March 2009 08:15:56 manish jain wrote: > Hi, > > I portsnapped the lastest tarball a couple of days back. Doing a build > > in lang/guile (1.8.6) core dumps with the following message : > > Making all in libguile > > gmake[2]: Entering directory > > `/usr/ports/lang/guile/work/guile-1.8.6/libguile' cd .. && /bin/sh > > ./config.status libguile/Makefile depfiles > > config.status: creating libguile/Makefile > > config.status: executing depfiles commands > > gmake[2]: Leaving directory > > `/usr/ports/lang/guile/work/guile-1.8.6/libguile' gmake[2]: Entering > > directory `/usr/ports/lang/guile/work/guile-1.8.6/libguile' Generating > > libpath.h... > > sed < ./version.h.in > version.h.tmp \ > > -e s:@-GUILE_MAJOR_VERSION-@:1: \ > > -e s:@-GUILE_MINOR_VERSION-@:8: \ > > -e s:@-GUILE_MICRO_VERSION-@:6: > > mv version.h.tmp version.h > > if [ "no" = "yes" ]; then \ > > cc -DHAVE_CONFIG_H -I.. -I.. -I.. -c -o gen-scmconfig.o > > gen-scmconfig.c; \ else \ > > cc -DHAVE_CONFIG_H -I.. -I.. -I.. -I/usr/local/include -O2 > > -fno-strict-aliasing -pipe -Wall -Wmissing-prototypes -Werror -c -o > > gen-scmconfig.o gen-scmconfig.c; \ fi > > if [ "no" = "yes" ]; then \ > > cc -o gen-scmconfig gen-scmconfig.o; \ > > else \ > > /bin/sh ../libtool --tag=CC --mode=link cc -O2 > > -fno-strict-aliasing > > -pipe -Wall -Wmissing-prototypes -Werror -L/usr/local/lib -o > > gen-scmconfig gen-scmconfig.o -llthread -lgmp -lcrypt -lm -lltdl ; \ fi > > libtool: link: cc -O2 -fno-strict-aliasing -pipe -Wall > > -Wmissing-prototypes -Werror -o gen-scmconfig gen-scmconfig.o > > -L/usr/local/lib -llthread /usr/local/lib/libgmp.so -lcrypt -lm vs mine: libtool: link: /usr/local/libexec/ccache/world-cc -O2 -fno-strict-aliasing - pipe -Wall -Wmissing-prototypes -Werror -o gen-scmconfig gen-scmconfig.o - L/usr/local/lib /usr/local/lib/libgmp.so -lcrypt -lm /usr/local/lib/libltdl.so -Wl,-rpath -Wl,/usr/local/lib -Wl,-rpath -Wl,/usr/local/lib Where does -llthread come from? -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
guile-1.8.6 build core dumps (autoconf issue ?)
Hi, I portsnapped the lastest tarball a couple of days back. Doing a build in lang/guile (1.8.6) core dumps with the following message : Making all in libguile gmake[2]: Entering directory `/usr/ports/lang/guile/work/guile-1.8.6/libguile' cd .. && /bin/sh ./config.status libguile/Makefile depfiles config.status: creating libguile/Makefile config.status: executing depfiles commands gmake[2]: Leaving directory `/usr/ports/lang/guile/work/guile-1.8.6/libguile' gmake[2]: Entering directory `/usr/ports/lang/guile/work/guile-1.8.6/libguile' Generating libpath.h... sed < ./version.h.in > version.h.tmp \ -e s:@-GUILE_MAJOR_VERSION-@:1: \ -e s:@-GUILE_MINOR_VERSION-@:8: \ -e s:@-GUILE_MICRO_VERSION-@:6: mv version.h.tmp version.h if [ "no" = "yes" ]; then \ cc -DHAVE_CONFIG_H -I.. -I.. -I.. -c -o gen-scmconfig.o gen-scmconfig.c; \ else \ cc -DHAVE_CONFIG_H -I.. -I.. -I.. -I/usr/local/include -O2 -fno-strict-aliasing -pipe -Wall -Wmissing-prototypes -Werror -c -o gen-scmconfig.o gen-scmconfig.c; \ fi if [ "no" = "yes" ]; then \ cc -o gen-scmconfig gen-scmconfig.o; \ else \ /bin/sh ../libtool --tag=CC --mode=link cc -O2 -fno-strict-aliasing -pipe -Wall -Wmissing-prototypes -Werror -L/usr/local/lib -o gen-scmconfig gen-scmconfig.o -llthread -lgmp -lcrypt -lm -lltdl ; \ fi libtool: link: cc -O2 -fno-strict-aliasing -pipe -Wall -Wmissing-prototypes -Werror -o gen-scmconfig gen-scmconfig.o -L/usr/local/lib -llthread /usr/local/lib/libgmp.so -lcrypt -lm /usr/local/lib/libltdl.so -Wl,-rpath -Wl,/usr/local/lib -Wl,-rpath -Wl,/usr/local/lib rm -f scmconfig.h.tmp cat ./scmconfig.h.top > scmconfig.h.tmp ./gen-scmconfig >> scmconfig.h.tmp Segmentation fault (core dumped) gmake[2]: *** [scmconfig.h] Error 139 gmake[2]: Leaving directory `/usr/ports/lang/guile/work/guile-1.8.6/libguile' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/lang/guile/work/guile-1.8.6' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/lang/guile. The complete logfile is more than 27 kb, which anybody can get from me by sending me a separate mail. One point of interest in the previous sections of the build states that guile-1.8.6 is to be configured with autoconf-2.63 whereas the latest autoconf port available is 2.62. -- Thank you and Regards Manish Jain invalid.poin...@gmail.com +91-99830-62246 NB : Laast year I kudn't spell Software Engineer. Now I are won. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"