From: Dwight <dcrs6000@aceweb.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bug-guile@gnu.org
Subject: Re: Unable to build guile
Date: Mon, 03 Nov 2008 18:16:47 -0800 [thread overview]
Message-ID: <490FB08F.7030903@aceweb.com> (raw)
In-Reply-To: <87ljw01lm1.fsf@gnu.org>
Hi Ludovic Courtès,
>>>It's libltdl (part of Libtool) that matters, since Libtool (the script)
>>>is otherwise bundled with Guile's tar.gz. So can you please make sure
>>>Guile is compiled using libltdl from Libtool 1.5.x? To that end, you
>>>can pass `-I' flags to the compiler, e.g., as follows:
>>>
>>> $ CPPFLAGS="-I/path/to/libtool/1.5.x/include" ./configure ...
>>
>> I could not find a libtool include directory. All I could find
>>is the following.
>
>
> You should look for `ltdl.h', which is the public header file of
> libltdl. You can also look for `libltdl.*', which is the compiled
> `libltdl'.
>
> Then there should be a `-I' flag for the former and a `-L' flag for the
> latter.
I did the following:
# CPPFLAGS="-I/opt/freeware/share/libtool/libltdl" ./configure
remove the -Wall from the compile of numbers.c compiler command and
reran the command
# make
remove the _Wall from the compile of net_db.c compiler command and
reran the command
# make
Not sure; but I think it got pass the place where it was having
a problem with the unknow symbol. But I am not sure because I was not
watching the compile.
However; the make did not complete successfully. It stopped with the
following: (I typed a make again to see if it would work! Got the same error message!)
Any suggestions?
gawk -f ./guile-func-name-check regex-posix.c
(./guile-snarf-docs -DHAVE_CONFIG_H -I.. -I.. -I.. -I/opt/freeware/share/libtool/libltdl -I/usr/local/include
-I/opt/pware/include -g -O2 -Wall -Wmissing-prototypes -Werror regex-posix.c | \
./guile_filter_doc_snarfage --filter-snarfage) > regex-posix.doc || { rm regex-posix.doc; false; }
cat alist.doc arbiters.doc async.doc backtrace.doc boolean.doc chars.doc continuations.doc debug.doc
deprecation.doc deprecated.doc discouraged.doc dynl.doc dynwind.doc environments.doc eq.doc error.doc eval.doc
evalext.doc extensions.doc feature.doc fluids.doc fports.doc futures.doc gc.doc goops.doc gsubr.doc
gc-mark.doc gc-segment.doc gc-malloc.doc gc-card.doc guardians.doc hash.doc hashtab.doc hooks.doc i18n.doc
init.doc ioext.doc keywords.doc lang.doc list.doc load.doc macros.doc mallocs.doc modules.doc numbers.doc
objects.doc objprop.doc options.doc pairs.doc ports.doc print.doc procprop.doc procs.doc properties.doc
random.doc rdelim.doc read.doc root.doc rw.doc scmsigs.doc script.doc simpos.doc smob.doc sort.doc srcprop.doc
stackchk.doc stacks.doc stime.doc strings.doc srfi-4.doc srfi-13.doc srfi-14.doc strorder.doc strports.doc
struct.doc symbols.doc threads.doc throw.doc values.doc variable.doc vectors.doc version.doc vports.doc
weaks.doc ramap.doc unif.doc dynl.doc filesys.doc posix.doc net_db.doc socket.doc regex-posix.doc |
GUILE="/tmp/VIM/guile-1.8.5/pre-inst-guile" ../scripts/snarf-check-and-output-texi >
guile-procedures.texi || { rm guile-procedures.texi; false; }
/bin/sh: 29454 Segmentation fault(coredump)
make[3]: *** [guile-procedures.texi] Error 1
make[3]: Leaving directory `/tmp/VIM/guile-1.8.5/libguile'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/tmp/VIM/guile-1.8.5/libguile'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/VIM/guile-1.8.5'
make: *** [all] Error 2
*********************************************************************************************************
Error Log entry for this problem:
LABEL: CORE_DUMP
Date/Time: Mon Nov 3 18:03:58 PST
Type: PERM
Resource Name: SYSPROC
Description
SOFTWARE PROGRAM ABNORMALLY TERMINATED
Detail Data
SIGNAL NUMBER
11
USER'S PROCESS ID:
28756
FILE SYSTEM SERIAL NUMBER
5
INODE NUMBER
24579
PROCESSOR ID
1
CORE FILE NAME
/tmp/VIM/guile-1.8.5/libguile/core
PROGRAM NAME
lt-guile
ADDITIONAL INFORMATION
pthread_m 4C
pthread_m 44
scm_threa 28
scm_i_ini 4C
scm_i_wit 100
scm_boot_ 34
main 3C
__start 8C
# find . -name "lt-guile" -print
./libguile/.libs/lt-guile
# /usr/local/bin/file ./libguile/.libs/lt-guile
./libguile/.libs/lt-guile: executable (RISC System/6000 V3.1) or obj module not stripped
next prev parent reply other threads:[~2008-11-04 2:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 21:08 Unable to build guile Dwight
2008-11-02 20:31 ` Ludovic Courtès
2008-11-03 21:01 ` Andy Wingo
[not found] ` <490E7842.9040903@aceweb.com>
[not found] ` <87d4hdmbw8.fsf@gnu.org>
[not found] ` <490F78C1.9020703@aceweb.com>
[not found] ` <87ljw01lm1.fsf@gnu.org>
2008-11-04 2:16 ` Dwight [this message]
2008-11-04 11:11 ` Ludovic Courtès
2008-11-04 20:35 ` Dwight
2008-11-05 9:10 ` Ludovic Courtès
2008-11-05 21:17 ` Dwight
2008-11-06 11:28 ` Ludovic Courtès
2008-11-07 1:22 ` Dwight
2008-11-08 17:49 ` Ludovic Courtès
2008-11-09 0:45 ` Dwight
2008-11-09 21:48 ` Ludovic Courtès
2008-11-10 2:26 ` Dwight
2008-11-04 17:50 ` Marijn Schouten (hkBst)
2008-11-05 8:42 ` Ludovic Courtès
2008-11-05 15:05 ` Marijn Schouten (hkBst)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=490FB08F.7030903@aceweb.com \
--to=dcrs6000@aceweb.com \
--cc=bug-guile@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).