In <[EMAIL PROTECTED]>, on 01/07/05
at 10:00 PM, "Marc G. Fournier" <[EMAIL PROTECTED]> said:
>On Fri, 7 Jan 2005, Peter Eisentraut wrote:
>> Various recent and not so recent problem reports got me thinking again
>> that it might be worth switching our shared library build system to
>> libtool. Among those are:
>>
>> - Guesswork about which spellings of -rpath, -export-dynamic, -fpic etc.
>> work on a particular platform or compiler.
>>
>> - Lack of information about which libraries libpq depends on.
>>
>> - Makefile.shlib can only build one library per directory.
>>
>> - pgxs is pretty ugly and inflexible because of the above.
>>
>> - Static libraries built with -fpic, which is sometimes considered a
>> bug.
>>
>> - Misbehavior with rpaths pointing the wrong way during the regression
>> tests and similar problems could maybe be tackled.
>>
>> Considering that pretty much everyone uses libtool these days, I'm not
>> too worried about portability.
>>
>> (And before anyone asks: No, libtool does not require automake.)
>>
>> I think it may be worth trying out. Comments?
>Does it work with Windows, or with that be a 'special case'?
It is supposed to...
Mind you, it is supposed to support OS/2 as well and I have had problems
with several projects that use it.
--
-----------------------------------------------------------
[EMAIL PROTECTED]
-----------------------------------------------------------
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
