>> On Thu, Jan 04, 2001 at 04:23:00AM +0000, Alexander Mai wrote:
> > CVSROOT: /cvsroot/lesstif
> > Module name: lesstif
> > Repository: lesstif/lib/Xbae/
> > Changes by: amai@usw-pr-cvs1. 01/01/04 04:23:00
> >
> > Modified files:
> > lesstif/lib/Xbae/: acinclude.m4 configure.in
> >
> > Log message:
> > configure.in: drop unused(?!?) version stuff.
> > In my understanding we only focus on the default-version
> > of the lesstif tree above, right?
> > acinclude.4: bring motif macros on level of lesstif/acinclude.m4
> > i.e. it's still not capable of adding missing libs
>
> I'm a bit stuck here ...
>
> e.g. I don't know why the direct tests do look for
> some files libXm.a/so/sl only instead of trying to
> link something against, or just use the path for a
> -L flag?!
> If we=configure=etc. can not get these archives/libs linked we
> don't need to proceed anyway!?
>
> Also I want to ensure that only required libs are being
> linked against. As I verified on a linux platform once even
> unused libs can later on cause trouble if being removed.
So I don't like the idea of linking against libXp/libXpm/etc. if found w/o
further checks.
--
Alexander Mai
[EMAIL PROTECTED]
