adonthell-general
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Adonthell-general] some error while building libltdl-dev is good at


From: shirish शिरीष
Subject: Re: [Adonthell-general] some error while building libltdl-dev is good at my end. The system is a 64-bit system, maybe its not looking for 64-bit path systems.
Date: Tue, 15 Nov 2011 04:09:41 +0530

In-line :-

2011/11/15 Kai Sterker <address@hidden>:
> 2011/11/14 shirish शिरीष <address@hidden>:
>
>> Lemme know if it helped or not.
>
> First time the wrong libltdl appears in the log is here:
>
> + . /usr/local/lib/libadonthell_py_runtime.la
> ++ dlname=libadonthell_py_runtime.so.0
> ++ library_names='libadonthell_py_runtime.so.0.0.0
> libadonthell_py_runtime.so.0 libadonthell_py_runtime.so'
> ++ old_library=libadonthell_py_runtime.a
> ++ inherited_linker_flags=
> ++ dependency_libs=' -L/usr/lib/python2.7/config -lpython2.7 -lpthread
> -lutil -lz /usr/lib/libltdl.la -ldl'
> ++ weak_library_names=
> ++ current=0
> ++ age=0
> ++ revision=0
> ++ installed=yes
> ++ shouldnotlink=no
> ++ dlopen=
> ++ dlpreopen=
> ++ libdir=/usr/local/lib
>
> Seems like it picked up some old dependencies from a previous
> installation of Adonthell?
>
> It's still a bit of a puzzle how /usr/lib/libltdl.la ended in there as
> dependency, when all the rest (except for python) is given as
> -l<libname>. I don't know enough about libtool to even guess at the
> reason.
>
> Anyway, try cleaning up any traces left from old installations. I
> imagine those can confuse the build system.


Ok, first of all this is another machine so having old installations
of adonthell is outta the question.

As far as 'cleaning up any traces left from old installations' is
concerned, even if there were/are, how to know ?

I did try to compile adonthell-tools-build quite a few times today
though before coming on to the mailing list. (thought perhaps is wrong
at my end). Even after trying everything including reinstalling
libtool when the output did not change then came on the ML.

Any hints or ideas in this regard would be much appreciated.

> If somebody has any input how to avoid such problems in the future, or
> what to change in Adonthell's build system, please let me know.

+1 here.

> Kai

-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
065C 6D79 A68C E7EA 52B3  8D70 950D 53FB 729A 8B17



reply via email to

[Prev in Thread] Current Thread [Next in Thread]