public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "xdje42 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug guile/17367] New: computation of guild path wrong when pkg-config script supplied as arg to --with-guile
Date: Wed, 10 Sep 2014 04:06:00 -0000 [thread overview]
Message-ID: <bug-17367-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=17367
Bug ID: 17367
Summary: computation of guild path wrong when pkg-config script
supplied as arg to --with-guile
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: guile
Assignee: unassigned at sourceware dot org
Reporter: xdje42 at gmail dot com
Guile 2.2 now compiles to ELF files, and I was noticing gdb complaining when
starting up.
Exception caught while booting Guile.
Error in function "load-thunk-from-memory":
not an ELF file
./gdb: warning: Could not complete Guile gdb module initialization from:
/hack/gnu/sourceware/gdb-guile/b-sigchld-prep-git-guile-gc74/gdb/data-directory/guile/gdb/boot.scm.
I traced this to the wrong guild program being used.
guild should come from the specified guile distribution,
but /bin/guild was being used instead (which is guile 2.0).
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2014-09-10 4:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 4:06 xdje42 at gmail dot com [this message]
2014-09-10 4:09 ` [Bug guile/17367] " xdje42 at gmail dot com
2014-09-10 4:20 ` cvs-commit at gcc dot gnu.org
2014-09-10 5:14 ` cvs-commit at gcc dot gnu.org
2014-09-11 16:01 ` xdje42 at gmail dot com
2014-10-29 19:48 ` cvs-commit at gcc dot gnu.org
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-17367-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.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).