Re: [PHP4BETA] cvs: /php4 configure.in

Sascha Schumann <sascha@schumann.cx> writes: > On Thu, Dec 02, 1999 at 03:04:07PM -0800, David Hedbor wrote: > > "Sascha Schumann" <sascha@schumann.cx> writes: > > > > > Sas Sat Dec 4 14:56:39 1999 EDT > > > > > > Modified files: > > > /php4 configure.in > > > Log: > > > Create ``libs'' subdirectory as the current user and add /usr/ucblib > > > always to the libpath, if it exists (#2752). > > > > I don't think you want to do this. Using ucblib stuff can create tons > > of weird problems. > > We don't use "ucblib stuff," we merely provide a convenient > way to avoid setting LD_LIBRARY_PATH. > > Because there are no conflicting libraries in /usr/lib and > /usr/ucblib, I don't see how this can break anything. The libs in /usr/ucblib basically are BSD compatibility stuff. As an example I once linked an xv against libs in /usr/ucblib since it was using some BSD function (maybe it was search instead of index). The result was that I got an XV that cut off the beginning of all all file names in the file listing. Needless to say the problem was fixed when I did a "correct" port instead. I have had many other ucblib related problems and also know of other people that has had them and I can probably dig up more if you wish. The question still stands - why is ucblib used at all? It's not a requirement to compile on Solaris (other than if you try to compile using BSD compatibility stuff and don't port correctly). -- [ Below is a random fortune, which is unrelated to the above message. ] Q: How many WASPs does it take to change a lightbulb? A: One.