From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: static linking
Date: Fri, 13 Feb 2004 00:39:03 +0100 [thread overview]
Message-ID: <877jyrhnqg.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87y8rhosj9.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Thu, 05 Feb 2004 20:23:06 -0600")
Rob Browning <rlb@defaultvalue.org> writes:
> So I don't know what's going on yet, but at least it's reproducable.
I can't reproduce it. The resulting statically linked a.out cannot
load shared libraries (so that for example libguilereadline doesn't
work), tho. No segfaults happen, howevers.
$ ldd a.out
not a dynamic executable
$ ./a.out
ERROR: In procedure dynamic-link:
ERROR: file: "libguilereadline-v-12", message: "/usr/local/lib/libguilereadline-v-12.a: invalid ELF header"
$ ./a.out -q
guile>
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2004-02-12 23:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200401150550.i0F5orkj005242@pc18.math.umbc.edu>
2004-02-06 2:23 ` static linking Rob Browning
2004-02-12 23:39 ` Marius Vollmer [this message]
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=877jyrhnqg.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--cc=guile-devel@gnu.org \
--cc=guile-user@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).