A libtool and automake question (for developing fuppes)

[Robert Massaioli]

Recently I tried to build fuppes UPnP Media Server
(http://fuppes.ulrich-voelkel.de/) but I came across the following
error:

bin/sed: can't read /usr/lib/libogg.la: No such file or directory
libtool: link: `/usr/lib/libogg.la' is not a valid libtool archive

The problem seems to be that Debian is removing the .la files from
most of their packages
(http://lists.debian.org/debian-devel/2009/08/msg00783.html) and as a
result I get the following:

# dpkg -L libogg-dev | grep "a$"
/usr/lib/libogg.a
#

So now I don't have a libogg.la file anymore. I have read around and
all I know is that you are not supposed to need to .la files to use
libtool and compile your package. I read the libtool-automake docs but
I still cannot see what I am supposed to do; they seem to suggest that
you need all of the .la files present. So my question is, how am I
supposed to compile fuppes so that it does not require .la files from
packages like libogg-dev?

N.B. I am asking this here because this is the first open source
project that I have decided to work on and I hope to re-raise fuppes,
from the rut it seems to have fallen into, to a package that somebody
might even want to sponsor. Thankyou for any time and help. If this is
not the right place for me to ask this kind of question, please point
me in the right direction and I'd be more than happy.


--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Russ Allbery-2]

Robert Massaioli <robertm@...> writes:

> Recently I tried to build fuppes UPnP Media Server
> (http://fuppes.ulrich-voelkel.de/) but I came across the following
> error:

> bin/sed: can't read /usr/lib/libogg.la: No such file or directory
> libtool: link: `/usr/lib/libogg.la' is not a valid libtool archive

Usually libtool should just cope transparently and you don't need to do
anything.  The case when it doesn't, and what I suspect you're running
into, is when what you're building depends on some other library that does
have an *.la file, and that *.la file in turn references the (no longer
present) libogg.la file.

This happened to a lot of packages because the removal of libogg.la wasn't
as well-coordinated as it could have been, so the first step would be to
make sure that you're completely up-to-date on all the dev packages that
you're using.  If that still doesn't work, reporting here what libraries
your program is trying to link against should help in narrowing it down.

--
Russ Allbery (rra@...)               <http://www.eyrie.org/~eagle/>


--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...