I am having problems compiling guile on my system, and have not found any material in the archive relating to my problem. Here is the text from the Terminal:

Making all in libltdl
/bin/sh ./libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I. -no-cpp-precomp -g -O2 -c ltdl.c
mkdir .libs
gcc -DHAVE_CONFIG_H -I. -I. -I. -no-cpp-precomp -g -O2 -c ltdl.c -fno-common -DPIC -o .libs/ltdl.lo
gcc -DHAVE_CONFIG_H -I. -I. -I. -no-cpp-precomp -g -O2 -c ltdl.c -o ltdl.o >/dev/null 2>&1
mv -f .libs/ltdl.lo ltdl.lo
/bin/sh ./libtool --mode=link gcc -g -O2 -o libltdlc.la ltdl.lo -ldl
rm -fr .libs/libltdlc.la .libs/libltdlc.* .libs/libltdlc.*
ar cru .libs/libltdlc.al ltdl.lo
ranlib .libs/libltdlc.al
creating libltdlc.la
(cd .libs && rm -f libltdlc.la && ln -s ../libltdlc.la libltdlc.la)
Making all in libguile
PATH=.:/sw/bin:/sw/sbin:/bin:/usr/bin:/sbin:/usr/sbin:/usr/X11R6/bin ./guile-doc-snarf alist.c -DHAVE_CONFIG_H -I.. -I./.. -I../libltdl -no-cpp-precomp -g -O2 -Wall -Wmissing-prototypes alist.c > alist.x \
|| { rm alist.x; false; }
./guile-doc-snarf: line 26: 11699 Segmentation fault ${AWK} -f guile-func-name-check "$fullfilename"
./guile-doc-snarf: line 32: 11704 Broken pipe cat ${temp}
11705 | sed 's/ ^\(.\{128\}.\{128\}.\{128\}.\{128\}.\{128\}.\{128\}.\{128\}.\{128\}\).*/ \1/g'
11706 Segmentation fault | ${AWK} -f `dirname $0`/guile-snarf.awk `basename ${dot_doc}`
make[1]: *** [alist.x] Error 1
make: *** [all-recursive] Error 1
### execution of /var/tmp/tmp.1.WZSodu failed, exit code 2
Failed: compiling guile-1.4-27 failed


Does anybody know what this means?



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to