From: Greg Troxel <gdt@ir.bbn.com>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: guile-devel@gnu.org, debian-hppa@lists.debian.org
Subject: Re: Guile FTBFS on hppa - problem in detecting stack direction?
Date: Sat, 09 Aug 2008 09:31:22 -0400 [thread overview]
Message-ID: <rmibq02nwlx.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <20080807094906.GB30637@pcpool00.mathematik.uni-freiburg.de> (Bernhard R. Link's message of "Thu, 7 Aug 2008 11:49:06 +0200")
"Bernhard R. Link" <brlink@debian.org> writes:
> * Carlos O'Donell <carlos@systemhalted.org> [080807 03:41]:
>
> Just because something is part of some ABI is no reason to not try to
> autodetect it. It's an elementary philisophical idea behind autoconf
> (and one of its biggest advantages in my POV) that you do not check for
> the system but for its features[1].
> This allows it to support most new platforms for most programs out of
> the box (and not fail if anything changes anywhere).
>
> There are some reasons to sometimes depart from that rule, when things
> are too hard to check or too subtle to break. But just that this
> information can be deduced from some triplet in alone is no reason at
> all.
Another consideration is being able to do cross builds, and for that one
should avoid AC_TRY_RUN.
next prev parent reply other threads:[~2008-08-09 13:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 20:38 Guile FTBFS on hppa - problem in detecting stack direction? Neil Jerram
2008-08-06 21:13 ` Kyle McMartin
2008-08-07 1:40 ` Carlos O'Donell
2008-08-07 9:49 ` Bernhard R. Link
2008-08-07 12:29 ` Carlos O'Donell
2008-08-09 13:31 ` Greg Troxel [this message]
2008-08-09 15:16 ` Han-Wen Nienhuys
2008-08-07 12:27 ` Carlos O'Donell
2008-08-07 21:04 ` Neil Jerram
2008-08-09 17:02 ` Kyle McMartin
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=rmibq02nwlx.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=carlos@systemhalted.org \
--cc=debian-hppa@lists.debian.org \
--cc=guile-devel@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).