[ clisp-Feature Requests-1226120 ] configure shall report essential findings

[SourceForge.net <no...@so...>]

Feature Requests item #1226120, was opened at 2005-06-23 10:58
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=351355&aid=1226120&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jörg Höhle (hoehle)
Assigned to: Nobody/Anonymous (nobody)
Summary: configure shall report essential findings

Initial Comment:
Hi,

everytime I build a new CLISP, invoking ./configure, it
takes me at least 3 runs until I get the options right.
o will readline get used or not, was it found? (I found
not sensitive mention of it in the logs)
o will libsigsegv get used or not?
 -- will it provide generational GC!?!
o will it eventually use the FFI or not? (it may not be
available for some reason, even when I say
--with-dynamic-ffi).

I suggest that configure outputs essential
configuration items just before it explains how to
create the Makefile.

For example, I found out that even finding noreadline.?
as targets in the Makefile is no indication of whether
readline will get linked in or not. It's sometimes not
until a full clisp is built that I discover that it was
not built the way I intended and I need to restart all
over. This late feedback is not state-of-the-practice.

Regards,
     Jörg Höhle


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=351355&aid=1226120&group_id=1355