On Tue, 21 Aug 2001 13:59:04 +0100, [EMAIL PROTECTED] wrote:
>> does it help with the LessTif compilation if we/you just
>> rename the 'Depth' int variables inside Baseclass.c into 'depth'?
>
>
>Sure - that's actually what I ended up doing myself...
Done in CVS.
>The other problem I had was with libtool. This seems more tricky to
>sort out properly (I kind of hacked it a bit).
>
>Basically, it fails when it tries to create a library which contains
>nothing.
>
>If you find the line in libtool as follows:
>
>old_archive_cmds="\$AR cru \$oldlib\$oldobjs~\$RANLIB \$oldlib"
>
>What was happening was that it was trying to execute the command:
>
>ar cru Xm/.libs/libXm.a (or something like that...)
>
>...with $oldobjs empty (or just a space) because it had not built
>any object files in Xm.
>
>I hacked this basically by putting a condition on it:
>
>if [ !'x\$oldobjs'='x ' ]; then \$AR -cru \$oldlib\$oldobjs ;fi
>
>
>I'd be interested to know how/why the installer decides which of
>1.2/2.0/2.1 to install. On my G4 cube (OS X 10.0.4) it looks like it
>only compiled for v2.0 - the others are empty.
>
>Does this mean I could be missing something important that comes from
>1.2? And since 2.0 is effectively 'discontinued', is this something
>that needs sorting out so it comiles v2.1 also?
>
>Any info greatly appreciated!
We decided to have a default version which is the only
one built and which gets installed. Check out the docs and
configure --help on how to change this.
WRT libtool: did we already give the advice to install
a recent set of auto* tools (libtool 1.4, autoconf 2.5x, automake 1.4-p5),
run CVSMake in our toplevel dir and try this?
Drawback is, of course, that you have then a rather unusable
autoconf installed, but if it helps for LessTif ...
---
Alexander Mai
[EMAIL PROTECTED]
