From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Preparing for a 1.6.8 release.
Date: Wed, 19 Oct 2005 14:08:22 -0700 [thread overview]
Message-ID: <87wtk9use1.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <200510161935.MAA18120@hpsje.cup.hp.com> (Steve Ellcey's message of "Sun, 16 Oct 2005 12:35:21 -0700 (PDT)")
Steve Ellcey <sje@cup.hp.com> writes:
> I was hoping the next release of guile would be buildable on IA64 HP-UX.
> The change that is needed is to modify libguile/continuations.c,
> libguile/continuations.h, and libguile/gc.c to have ifdefs on IA64
> instead of __ia64__.
>
> IA64 is set in libguile/gc_os_dep.c only for IA64 Linux. __ia64__ is set
> by GCC (and other compilers) for both Linux and HP-UX. But the code
> that is under the __ia64__ ifdef is Linux specific and will not compile
> on HP-UX.
I'll need to think about this for a moment. We can't use IA64
directly if it's only defined in gc_os_dep.c, since that's not
something continuations.c or gc.c can see.
I also don't want to introduce any new header symbols during a stable
release, so the least intrusive change would probably be to copy the
detection logic from gc_os_dep.c (or something similar) to
continuations.c and gc.c.
I haven't investigated carefully yet -- do you have any idea offhand
if the __ia64__ guarded bits in those files are absolutely Linux
specific? If we're not *sure*, then we'll need to reverse the sense
of the test and just exclude HP-UX so that we don't accidentally break
some other ia64 platform.
> | ERROR: In procedure variable-set-name-hint!:
> | ERROR: Wrong type argument in position 2 (expecting SYMBOLP): #<freed cell 40050f00; GC missed a reference>
I can't recall if I already asked this, but could you re-try with
the 1.6.8-rc0 archive (or current 1.6 CVS)?
> I don't know if this is a known issue or IA64 specific or what since I
> am not that familiar with guile (I mostly just want to build autogen).
We had a similar problem on ia64/Linux, but with rc0 it seems to have
vanished, at least on the machine I tested. We still have a problem
on m68k.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
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 21:08 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 [this message]
2005-10-19 21:25 ` Steve Ellcey
2005-10-19 21:54 ` Rob Browning
2005-10-19 22:31 ` Steve Ellcey
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=87wtk9use1.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.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).