hi,
a new *build* of
libtool (Build: 1.2599 2008/03/02 00:05:01) 2.2
from cvs seems ok (no noticed errors) on OSX 10.5.2,
Darwin Kernel Version 9.2.0: Tue Feb 5 16:15:19 PST 2008;
root:xnu-1228.3.13~1/RELEASE_PPC
w/
automake --version
automake (GNU automake) 1.10.1
autoconf --ver
snowcrash+libtool wrote:
> hi,
>
>
> is this a libtool or bdb problem? or, am i again missing a new/required step?
db's configuration requires it to know the shared library extension at
configure time, it does this by running the generated libtool script.
This does not work with libtool-2.2 bec
Albert Chin kirjoitti:
On Thu, Feb 28, 2008 at 03:17:54PM +0200, Petteri Räty wrote:
[EMAIL PROTECTED] /mnt/checkouts/classpath/native/jni/qt-peer $ make
make all-am
make[1]: Entering directory `/mnt/checkouts/classpath/native/jni/qt-peer'
/bin/sh ../../../libtool --tag=CXX --mode=link g++ -D
Petteri Räty wrote:
> Albert Chin kirjoitti:
>> On Thu, Feb 28, 2008 at 03:17:54PM +0200, Petteri Räty wrote:
>>> [EMAIL PROTECTED] /mnt/checkouts/classpath/native/jni/qt-peer $ make
>>> make all-am
>>> make[1]: Entering directory
>>> `/mnt/checkouts/classpath/native/jni/qt-peer'
>>> /bin/sh ../..
On Mon, Mar 03, 2008 at 02:02:09AM +0200, Petteri Räty wrote:
> Albert Chin kirjoitti:
>> On Thu, Feb 28, 2008 at 03:17:54PM +0200, Petteri Räty wrote:
>>> [EMAIL PROTECTED] /mnt/checkouts/classpath/native/jni/qt-peer $ make
>>> make all-am
>>> make[1]: Entering directory `/mnt/checkouts/classpath
hi,
> db's configuration requires it to know the shared library extension at
> configure time, it does this by running the generated libtool script.
> It is possible to generate one
> during configure, but it does not do so by default.
yup.
from my own, long-ago email from sleepycat support:
