[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: guile-1.5.6: some build comments

From: Neil Jerram
Subject: Re: guile-1.5.6: some build comments
Date: 27 Apr 2002 18:03:47 +0100
User-agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7

>>>>> "Marius" == Marius Vollmer <address@hidden> writes:

    Marius> Neil Jerram <address@hidden> writes:
    >> >>>>> "Nelson" == Nelson H F Beebe <address@hidden> writes:
    Nelson> I've made installation attempts for guile-1.5.6 on 13+
    Nelson> different UNIX platforms, with a few successes (GNU/Linux
    Nelson> systems), and several failures, either of the build, or of
    Nelson> parts of the test suite.  A brief summary is given below;
    Nelson> details, including full build logs, are available on
    Nelson> request.  Builds were done with the usual recipe
    Nelson> ./configure && make all check install
    >> Thanks enormously for such extensive testing!

    Marius> Indeed!

    Marius> Sorry for coming so late to the party.  I would be
    Marius> thrilled if we can sort out these issues.  What is the
    Marius> status on this?  Can I help?

Mr. Beebe reported several problems in his original email.

1. The "regcomp doesn't accept empty strings" bug that has now been
   reported by others as well.

2. The "putenv ("TZ") returns -1" bug that has now been reported by
   others as well.

3. A problem with "$@" not working on Compaq/DEC OSF/1 4.0 and 5.0,
   which means that our standard Guile scripts boilerplate won't work
   on this OS in the case that no arguments are passed.

4. Two problems with the Boehm GC stack-finding code not working, on
   MacOS X and Compaq Alpha OSF/1 5.0.

5. A .so library loading problem on IBM RS/6000 AIX 4.3.

6. The syncase/gensym issue, since fixed in CVS.

7. A stack overflow during guile_filter_doc_snarfage on SGI IRIX 6.5.

8. A build failure on Solaris 2.8.

I copied various followups to address@hidden, but no firm
conclusion was reached on any (except 6).  Can you see them there?  If
not, I could send them to you privately.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]