Re: bug reporting

Hi Sam,

> the current list is:
> https://clisp.sourceforge.io/beta/impnotes/clisp.html#bugs
> 
> is this all we need?

Probably it could be streamlined by distinguishing build failures from
other bugs. For the other bugs, "clisp --version" will give us the
version, compiler flags, versions of dependencies already, so no need to
ask for it explicitly.

How about this?

"When submitting a bug report, please specify the following information:

  1. What is your platform (uname -a on a UNIX system)?
  2. Please supply the full output (copy and paste) of all the error messages
  3. Please provide step-by-step instructions on how to reproduce the problem.
  4. If you are reporting a build failure:
     - Compiler version? GNU libc version (on GNU/Linux)?
     - What is the version of each of the DEPENDENCIES?
     - Where did you get the CLISP sources? When? (Absolute dates, e.g., “2006-01-17”,
       are preferred over the relative ones, e.g., “2 days ago”. If you are using
       Mercurial, please supply the output of hg id).
     - Which configure command were you using, and what are the values of the
       environment variables CC, CFLAGS, CPPFLAGS, LDFLAGS, LD_LIBRARY_PATH?
     - Please attach all build logs.
  5. If you are reporting any other bug:
     - What is the output of clisp --version?
     - Where did you get the CLISP sources or binaries? When? (Absolute dates,
       e.g., “2006-01-17”, are preferred over the relative ones, e.g., “2 days ago”.
       If you are using Mercurial, please supply the output of hg id).
"

Bruno


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel