From: Kevin Ryde <savannah-bounces@gnu.org>
Subject: [bug #14925] Non-portable binary compilations on linux
Date: Wed, 15 Feb 2006 10:56:01 +1300 [thread overview]
Message-ID: <20060215-105601.sv2403.79776@savannah.gnu.org> (raw)
In-Reply-To: <20051107-170432.sv0.50799@savannah.gnu.org>
Update of bug #14925 (project guile):
Status: None => Need Info
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #1:
We think __libc_stack_end is portable enough, we think it's upwardly
compatible between glibc versions, which should be enough.
Incidentally, it must be very difficult doing "binary compilations on linux",
I wasn't aware the kernel came with a compiler or shell or tools.
_______________________________________________________
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
prev parent reply other threads:[~2006-02-14 21:56 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
2006-02-14 21:56 ` Kevin Ryde [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=20060215-105601.sv2403.79776@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).