From: Dwight <dcrs6000@aceweb.com>
To: ludo@gnu.org
Cc: bug-guile@gnu.org
Subject: Re: Unable to build guile
Date: Tue, 04 Nov 2008 12:35:37 -0800 [thread overview]
Message-ID: <4910B219.9000301@aceweb.com> (raw)
In-Reply-To: <87prlbwxth.fsf@gnu.org>
Hi Ludovic Courtès,
> 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'.
OK! Thanks for the tip!
> 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?
# ./pre-inst-guile 2>&1 | tee /tmp/ToMail
ksh: 28668 Segmentation fault(coredump)
LABEL: CORE_DUMP
Date/Time: Tue Nov 4 11:09:47 PST
Type: PERM
Resource Name: SYSPROC
Description
SOFTWARE PROGRAM ABNORMALLY TERMINATED
Detail Data
SIGNAL NUMBER
11
USER'S PROCESS ID:
28668
FILE SYSTEM SERIAL NUMBER
5
INODE NUMBER
24576
PROCESSOR ID
1
CORE FILE NAME
/tmp/VIM/guile-1.8.5/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
> 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
# ./pre-inst-guile
Segmentation fault(coredump)
# gdb libguile/.libs/lt-guile core
GNU gdb 6.5
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "powerpc-ibm-aix5.2.0.0"...
ptrace ldinfo: The process does not exist..
(gdb) bt full
#0 0xd004a864 in pthread_mutexattr_init () from /usr/lib/libpthreads.a(shr_xpg5.o)
No symbol table info available.
#1 0xd6dd0bac in scm_threads_prehistory (base=0x2ff21e48) at threads.c:1656
No locals.
#2 0xd6e38b40 in scm_i_init_guile (base=0x0) at init.c:421
No locals.
#3 0xd6dd2fa4 in scm_i_with_guile_and_parent (func=@0xf0bd8764: 0x100a6834, data=0x2ff21ea8, parent=0xd6e37cfc)
at threads.c:561
res = (void *) 0xf0bd8764
base_item = 3846
#4 0xd6e38908 in scm_boot_guile (argc=536910536, argv=0x1, main_func=@0x20009af0: 0, closure=0x8180)
at init.c:350
c = {main_func = @0x200018b0: 0x10000458 <inner_main>, closure = 0x0, argc = 1, argv = 0x2ff21f5c}
#5 0x10000414 in main (argc=1, argv=0x2ff21f5c) at guile.c:74
No locals.
(gdb) Quit
> It would also be interesting to see the warnings issued by GCC -Wall.
numbers.c: In function 'guile_ieee_init':
numbers.c:622: warning: dereferencing type-punned pointer will break strict-aliasing rules
numbers.c:645: warning: dereferencing type-punned pointer will break strict-aliasing rules
make[3]: *** [libguile_la-numbers.lo] Error 1
cc1: warnings being treated as errors
net_db.c: In function 'scm_resolv_error':
net_db.c:112: warning: implicit declaration of function 'hstrerror'
make[3]: *** [net_db.lo] Error 1
Hope this information help.
Bye,
Dwight
next prev parent reply other threads:[~2008-11-04 20:35 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
2008-11-04 20:35 ` Dwight [this message]
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=4910B219.9000301@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).