From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile@gnu.org
Cc: Dwight <dcrs6000@aceweb.com>
Subject: Re: Unable to build guile
Date: Tue, 04 Nov 2008 12:11:06 +0100 [thread overview]
Message-ID: <87prlbwxth.fsf@gnu.org> (raw)
In-Reply-To: 490FB08F.7030903@aceweb.com
Hello,
Dwight <dcrs6000@aceweb.com> writes:
> 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
Note that `-Wall' itself is harmless, it's `-Werror' that causes the
compilation to stop. You can just as well use:
... ./configure --disable--error-on-warning
which removes `-Werror'.
> 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)
The `guile-snarf-docs' scripts uses Guile, so it's an indication that
the newly built Guile doesn't work. :-)
Can you try running "./pre-inst-guile" from the Guile build directory?
Also, can you provide a backtrace for the segfault? Assuming GDB is
available on your platform, something like the following should work:
$ cd /the/guile/build/dir
$ gdb libguile/.libs/lt-guile core
(gdb) bt full
It would also be interesting to see the warnings issued by GCC -Wall.
Thanks in advance,
Ludo'.
next prev parent reply other threads:[~2008-11-04 11:11 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
2008-11-04 11:11 ` Ludovic Courtès [this message]
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=87prlbwxth.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guile@gnu.org \
--cc=dcrs6000@aceweb.com \
/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).