Bruce Momjian wrote:
> Bruce Momjian wrote:
>> Tom Lane wrote:
>>> Bruce Momjian <pgman@candle.pha.pa.us> writes:
>>>> Tom Lane wrote:
>>>>> Now that we have the buildfarm I think that experimentation with
>>>>> this sort of thing is a lot less risky than it used to be. I
>>>>> think we should be working towards a project policy that
>>>>> AC_CHECK_LIB calls shalt not use "main", but must name some
>>>>> symbol exported by the expected library. If we can't find out
>>>>> what symbols the library is expected to provide, it's time to
>>>>> dike it out.
>>>
>>>> Agreed. Anyone want to do the legwork?
>>>
>>> It's not possible for any one person to do the legwork, but if
>>> several people would look to see what the story is on their
>>> platforms, we would have enough info to get started. We need to
>>> know which libraries actually get sucked in and some plausible
>>> exported names to test for each one.
>>>
>>> I'll report on HPUX, Linux, and OSX later today, if no one beats me
>>> to it.
>>
>> You want the Makefile.global LIBS line? On BSD/OS it is:
>>
>> LIBS = -lintl -lssl -lcrypto -lz -lreadline -ltermcap -lgetopt \
>> -lcompat -lipc -ldl -lm -lutil
>
> Uh, can't we pull this line from all the buildfarm members and just
> aggregate all the used libraries?
the issue is whether they actually export symbols that are NEEDED.
If someone can give me what to look for, I can cover the UnixWare case
(or give me a script
to run on 'firefly').
LER
--
Larry Rosenman
Database Support Engineer
PERVASIVE SOFTWARE. INC.
12365B RIATA TRACE PKWY
3015
AUSTIN TX 78727-6531
Tel: 512.231.6173
Fax: 512.231.6597
Email: Larry.Rosenman@pervasive.com
Web: www.pervasive.com