Re: A possible bash bug?

[Chet Ramey]

> I'm having a heck of a time trying to build my favorite vi look
> alike (nvi) and I think I've found a bug. I'm not sure where it is
> though, maybe behind my keyboard?
> 
> I'm running the configure file that's shipped with nvi-1.81.5 which
> I have freshly downloaded. I'm on a solaris 2.8 system with a ton of
> gnu software installed... most built by me but some packages from
> sunfreeware.com...
> 
> Nvi uses the db3 or db4 software and that's the area in which
> configure's apparently failing. I thought it might be a /bin/sh
> problem which is suns sh so I switched to the latest bash (2.05b
> with patches) hoping that this solves the problem. The problem
> appears with this version of bash as well. I have clip'd part of the
> build log created when I run configure with --no-reexec and -xv
> flags set in configure itself. I displayed the LIBS variable just
> before and just after the case statement below and both show up as
> being empty. Am I mis-understanding the case statement or the
> expression for the solaris* case or is this a bug?

I suspect that LIBS is somehow being assigned the null string, which is
making the test (${LIBS-xxx}) succeed.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
                                                Live...Laugh...Love
Chet Ramey, ITS, CWRU    chet@po.cwru.edu    http://tiswww.tis.cwru.edu/~chet/