Re: library `/usr/lib/libncurses.la' was moved.

[Reini Urban <rurban@x-ray.at>]

Gerrit P. Haase schrieb:
> Reini Urban wrote:
>> Gerrit P. Haase schrieb:
>>> Getting this warning:
>>>
>>> libtool: link: warning: library `/usr/lib/libncurses.la' was moved.
>>>
>>> $ cat /usr/lib/libncurses.la
>>> [...]
>>> # Directory that this library needs to be installed in:
>>> libdir='/usr/src/ncurses/ncurses-5.4/.inst/usr/lib'
>>
>>
>> We should really add some kind of .la test to our gbs.
>> Or maybe into setup.exe, for those people who already have their gbs 
>> customized or not using it?
> 
> Naah, it is a libtool bug, for sure.  Sanity check is good, but it 
> shouldn't be neccessary.
> 
>> Or provide a gbs-library?
>>   It would be easier to upgrade then.

 > I don't get this point.  Would you explain, please?

Modularization of the gbs:
Provide a central place for some common gbs functions, like 
/usr/share/cygwin/gbs-functions.sh, which would be sourced by each build 
script.
Any updates on this library will help all build scripts.
Currently you have to fix/update every single instance.
I'm thinking of functions which are very likely not touched.

The init step which parses the PKG/VER/REL, the name defaults,
install_docs, mkdirs, prep, autoreconf, reconf, mkpatch, build, certain 
install steps, strip, list, depend, requires, pkg, spkg, finish, 
sigfile, checksig, ...
But it's good to have some sane defaults which will get inherited to all 
new and old build scripts your are working with.

>> I had a lot such "broken" .la's, which forced me to post my fixups 
>> last month of a couple of such .la's. libcurl also.
> 
> Wrong libtool version...;)

But not on my side. Certain wrong devel packages install strange la's 
into /lib. I hope mine are correct.
-- 
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/