From: anonymous <savannah-bounces@gnu.org>
Subject: [bug #14925] Non-portable binary compilations on linux
Date: Mon, 7 Nov 2005 17:04:33 +0000 [thread overview]
Message-ID: <20051107-170432.sv0.50799@savannah.gnu.org> (raw)
In-Reply-To:
URL:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=14925>
Summary: Non-portable binary compilations on linux
Project: Guile
Submitted by: None
Submitted on: Mon 11/07/05 at 17:04
Category: None
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
_______________________________________________________
Details:
By default, when I built guile on my linux box (debian sarge). it uses the
"__libc_stack_end" symbol. This symbol is not portable. When I compile and
link my program with the guile libraries, and then try to move the binary to
a different linux platform (with a different version of GNU libc), the
program won't load with the error:
./no-repl: relocation error: ./no-repl: symbol __libc_stack_end, version
GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference
ldd --version shows glic 2.3.2 on one box, 2.3.5 on the other (it also fails
between 2.3.2 and 2.3.3)
My solution was to rebuild guile, but remove the line
"#define HAVE_LIBC_STACK_END 1" from config.h before recompiling (after
reconfiguring)
After relinking my executeable with this new version of guile, it still
failed due to:
ERROR: In procedure primitive-load-path:
ERROR: Unable to find file "ice-9/boot-9.scm" in load path
which meant I had to distribute along with the contents of
<install dir>/share/guile/1.6/
and set up run scripts to configure GUILE_LOAD_PATH before running my
executeable.
As __libc_stack_end is a non-portable symbol, I would like to see it not used
by default on the guile build. (or not used at all honestly)
Also, it would be nice if there was a way to statically link the file from
the share directory. If there already is and I just missed it while browsing
the documentation, I apologize, but I was unable to find it.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=14925>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next reply other threads:[~2005-11-07 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 17:04 anonymous [this message]
2005-11-12 9:30 ` [bug #14925] Non-portable binary compilations on linux Neil Jerram
2005-11-16 0:59 ` Kevin Ryde
2005-11-16 21:32 ` Neil Jerram
2006-02-14 21:56 ` Kevin Ryde
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=20051107-170432.sv0.50799@savannah.gnu.org \
--to=savannah-bounces@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).