From: Steve Ellcey <sje@cup.hp.com>
Subject: Re: Preparing for a 1.6.8 release.
Date: Sun, 16 Oct 2005 12:35:21 -0700 (PDT) [thread overview]
Message-ID: <200510161935.MAA18120@hpsje.cup.hp.com> (raw)
In-Reply-To: <877jcfsf5f.fsf@trouble.defaultvalue.org>
Rob,
> I'd like to release 1.6.8 quite soon.
>
> Given that, if there are issues that need to be resolved that you
> think I might overlook, please speak up.
>
> Thanks
> --
> 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
Rob,
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 made the ifdef changes to guile 1.6.7 to test them and I still had a
bulid problem that I don't understand, the build of libguile seemed to
work fine but the overall libguile make died while making some
documentation:
| cat alist.doc arbiters.doc async.doc backtrace.doc boolean.doc chars.doc continuations.doc debug.doc dynl.doc dynwind.doc environments.doc eq.doc error.doc eval.doc evalext.doc extensions.doc feature.doc fluids.doc fports.doc gc.doc goops.doc gsubr.doc guardians.doc hash.doc hashtab.doc hooks.doc init.doc ioext.doc iselect.doc keywords.doc lang.doc list.doc load.doc macros.doc mallocs.doc modules.doc numbers.doc objects.doc objprop.doc options.doc pairs.doc ports.doc print.doc procprop.doc procs.doc properties.doc random.doc rdelim.doc read.doc root.docrw.doc scmsigs.doc script.doc simpos.doc smob.doc sort.doc srcprop.doc stackchk.doc stacks.doc stime.doc strings.doc strop.doc strorder.doc strports.doc struct.doc symbols.doc throw.doc values.doc variable.doc vectors.doc version.doc vports.doc weaks.doc symbols-deprecated.doc ramap.doc unif.doc filesys.doc posix.doc net_db.doc socket.do
c regex-posix.doc | GUILE="/shale/sje/guile/obj/pre-inst-guile" /shale/sje/guile/guile-1.6
.7/scripts/snarf-check-and-output-texi --manual > guile.texi || { rm guile.texi; false; }
| ERROR: In procedure variable-set-name-hint!:
| ERROR: Wrong type argument in position 2 (expecting SYMBOLP): #<freed cell 40050f00; GC missed a reference>
| make[2]: *** [guile.texi] Error 1
| make[2]: Leaving directory `/shale/sje/guile/obj/libguile'
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).
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-16 19:35 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 [this message]
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
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=200510161935.MAA18120@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
/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).