From: Neil Jerram <neil@ossau.uklinux.net>
Cc: bug-guile@gnu.org
Subject: Re: [bug #14925] Non-portable binary compilations on linux
Date: Wed, 16 Nov 2005 21:32:47 +0000 [thread overview]
Message-ID: <87ek5gjn28.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87acg5o1an.fsf@zip.com.au> (Kevin Ryde's message of "Wed, 16 Nov 2005 11:59:28 +1100")
Kevin Ryde <user42@zip.com.au> writes:
> Neil Jerram <neil@ossau.uklinux.net> writes:
>>
>> - Can you be more precise about how __libc_stack_end is non-portable?
>> (Is it just a matter of having a recent enough glibc?)
>
> My guess would be __libc_stack_end is portable enough, in the sense of
> being upward compatible between glibc versions. Maybe the OP was
> moving to an older one.
That would be my guess too, and hence (I think) not a scenario that we
need to worry about.
>> - What do you mean "statically linking from the share directory"?
>
> I can't tell what that means either. Moved directories or something.
> Unlikely to be a good thing.
I thought it could mean somehow linking the Scheme code as text into
the libguile library or guile executable - which I've vaguely mulled
as being possibly useful for embedded systems without a filesystem...
>> But I don't see any way, either in this mail or in the bug report on
>> savannah, to contact the submitter ...
>
> Unless the submitter is lurking here we'll have to close it as unable
> to be actioned, not aware of such a problem ...
I guess we should just allow a few days to pass first, then.
Neil
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2005-11-16 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 17:04 [bug #14925] Non-portable binary compilations on linux anonymous
2005-11-12 9:30 ` Neil Jerram
2005-11-16 0:59 ` Kevin Ryde
2005-11-16 21:32 ` Neil Jerram [this message]
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=87ek5gjn28.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=bug-guile@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).