'configure' ( for GNU bash, version 2.05b.0(1) )

[Diller Ryan]

I ran into some problems when I tries to compile bashdb 0.36 on mac 
OSX 10.2.  The first two problems produced error messages from 
'configure' that requested the user to notify you.  The third and 
fourthproblems are more general issues with bash.

Someone was a little old fashioned in some header file tests. This 
person used the null definition
    #define const
which caused a redefinition error in cdefs.h.  I believe the form
    #undef const
would fix the problem.

A little more subtle is defaulting to the user's PATH in accessing 
'ls'.  If the user's PATH includes the GNU (fileutils-4.1) version of 
'ls', the output is not valid for a pipe at least on Mac OSX, .  The 
file names still have the termios control characters appended when 
the directed to a pipe.  To bypass this bug, you might want to use 
/bin/ls.

The following isn't a general config-type problem, so I don't know if 
you care about it.   There is a conflict between the definition of 
sys_siglist in /usr/include/signal.h and the usage in the bash 
siglist.c. It seems like the bash siglist.h tries to adjust for this, 
but isn't successful.  The easiest fix might be to modify 
/usr/include/signal.h, but I think there should be a better way.

The original reason for wanting to compile bash was to figure out why 
it has a problem with line-wrap on OSX (and apparently some other 
systems).  The problem is that an input line typed at the bash prompt 
which exceeds the window width is wrapped with only a <CR>.  This 
causes the wrap line to overlay the first part of the input.

Let me know if you want some more Mac OSX info,
Diller