guile-1.8.6 build core dumps (autoconf issue ?)

[Mel Flynn]

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