From: Steve Ellcey <sje@cup.hp.com>
Cc: guile-devel@gnu.org
Subject: Re: Preparing for a 1.6.8 release.
Date: Wed, 19 Oct 2005 15:31:11 -0700 (PDT) [thread overview]
Message-ID: <200510192231.PAA27954@hpsje.cup.hp.com> (raw)
In-Reply-To: <8764rtp3zh.fsf@trouble.defaultvalue.org>
> > Given that things don't work with 1.6.8.rc0 even after changing __ia64__
> > to IA64 I think it is reasonable not to address this problem for 1.6.8.
>
> Well, if we can do it safely and fairly easily, I'd still be inclined
> to add the code for ucontext_t on HP-UX because that lowers the bar
> for future progress. Is there a sufficiently specific test that you
> think might be appropriate?
Well the test for IA64 and not HP-UX would be "defined(__ia64) &&
!defined(__hpux)". __hpux and __ia64 are defined by both the HP
compilers and GCC on IA64 HP-UX. __hpux__ and __ia64__ are only defined
by GCC. IA64 Linux GCC defines __ia64 and __ia64__ but not any of the
hpux macros.
> Well if your needs aren't short-to-medium term, or if your intended
> purpose can handle a potentially very unstable guile, then you might
> want to focus on CVS HEAD (i.e. 1.7). However, if you need something
> stable, then 1.6 is it.
Sounds like 1.6 is more in line with what I want (1.6.9 if not 1.6.8).
Steve Ellcey
sje@cup.hp.com
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-10-19 22:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-15 2:11 Preparing for a 1.6.8 release Rob Browning
2005-10-16 19:35 ` Steve Ellcey
2005-10-19 21:08 ` Rob Browning
2005-10-19 21:25 ` Steve Ellcey
2005-10-19 21:54 ` Rob Browning
2005-10-19 22:31 ` Steve Ellcey [this message]
2005-10-19 22:59 ` Rob Browning
2005-10-19 23:22 ` Steve Ellcey
2005-10-19 23:39 ` Rob Browning
2005-10-19 23:45 ` Steve Ellcey
2005-10-16 22:46 ` Kevin Ryde
2005-10-16 22:59 ` Rob Browning
2005-10-18 7:31 ` Ludovic Courtès
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=200510192231.PAA27954@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--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).