Kevin Ryde <[EMAIL PROTECTED]> writes: > Neil Jerram <[EMAIL PROTECTED]> writes: >> >> - Can you be more precise about how __libc_stack_end is non-portable? >> (Is it just a matter of having a recent enough glibc?) > > My guess would be __libc_stack_end is portable enough, in the sense of > being upward compatible between glibc versions. Maybe the OP was > moving to an older one.
That would be my guess too, and hence (I think) not a scenario that we need to worry about. >> - What do you mean "statically linking from the share directory"? > > I can't tell what that means either. Moved directories or something. > Unlikely to be a good thing. I thought it could mean somehow linking the Scheme code as text into the libguile library or guile executable - which I've vaguely mulled as being possibly useful for embedded systems without a filesystem... >> But I don't see any way, either in this mail or in the bug report on >> savannah, to contact the submitter ... > > Unless the submitter is lurking here we'll have to close it as unable > to be actioned, not aware of such a problem ... I guess we should just allow a few days to pass first, then. Neil _______________________________________________ Bug-guile mailing list Bug-guile@gnu.org http://lists.gnu.org/mailman/listinfo/bug-guile