Steve Ellcey <[EMAIL PROTECTED]> writes: > Well, I am not sure. There seem to be two ways to attack this, create > some HP-UX specific code for continuations.c and gc.c, which would be to > replace the access of ucontext_t with calls and then set IA64 in > gc_os_dep.c and do more HP-UX specific stuff in that file. Or bail out > of the continuations.c and gc.c changes (use the default case) and just > use more generic code. I am not sure what the right way to go is.
Does HP-UX work with the generic code? If so, then what would be the advantage to anything else? > I don't have the HP-UX specific code for continuations.c and gc.c at > hand, my first thought was to just skip that code and use the generic C > code. That is why I was wondering if we wanted to punt on 1.6.8. And, > to add one more complication, the accessor functions that I would use to > replace the IA64 Linux code are not in libc, but in a library called > libuca.so so that library would need to be linked in with guile. I > don't know if that complicates things or not. Adding support for the library would probably mean we'd need to add at least a bit of autoconfery. > I am not sure exactly what schedule 1.6.8 is on but I will be down from > tomorrow afternoon until Monday because of an office move over the > weekend. I think we're probably not in any danger of a release before then, but you're probably right. There's no reason this can't wait for 1.6.9, which I can release as soon as we figure it out. 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 _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://lists.gnu.org/mailman/listinfo/guile-devel
