Re: [Gcl-devel] Re: More problems with solaris build

[C Y]

--- Camm Maguire <address@hidden> wrote:
> Greetings!
> 
> Dan Stanger <address@hidden> writes:
> 
> > The default is to include readline support, which  requires
> libreadline
> > and libncurses.
> > However if these files are not present, shouldn't the configure
> complain
> > about this?
> 
> Well, right now the way it is supposed to work is that support will
> be
> included if present, and silently omitted otherwise.  Gcl will still
> work without readline.  Isn't that more flexible?  The other options
> are
> 1) compile failure if no readline found
> 2) configure warning
> 
> 1) might seem a bit extreme, and 2) would most probably get lost in
>    the voluminous configure output, no?  But if its useful to you, I
>    could certainly add.

1 is too extreme.  The way I've seen this handled in a few other
programs with lots of output is to sum up at the end the key points of
the build, such what features are enabled.  So at the end, you might
have something like:

*****************************
Ready to build GCL for i686

Readline:  Enabled
TCL/TK:  Enabled

Now type make to compile.
*****************************

Don't know how feasible this is with the current system, but it might
be the best way to avoid having to scroll through all the output.

CY

__________________________________________________
Do You Yahoo!?
Yahoo! Sports - Coverage of the 2002 Olympic Games
http://sports.yahoo.com