[Lunar-bugs] [bug] libcdio fails build
Lunar bug reports list
lunar-bugs at lunar-linux.org
Mon Jul 11 16:49:48 UTC 2005
Project: lunar-linux
ID:
Version: <none>
Component: moonbase (modules)
Category: bug reports
Priority: normal
Assigned to: <unassigned>
Reported by: dveatch
Updated by: tchan
-Status: active
+Status: fixed
You have several problems with your lunar box. First off libcdio
compiles just fine without module vcdimager installed. The configure
step does correctly detect that vcdimager is not installed and passes a
WARNING message but the compile clearly continues on to completion. If
your lunar box is failing to compile because of a WARNING message in
./configure then you have other serious problems. Your cut&paste also
shows that your ./configure step is just detecting a WARNING
condition.
Module vcdimager will NOT compile without libcdio installed first as
its configure step forces the compile to fail if libcdio is not found.
So there is no circular dependency as far as compiliation goes. The
warning message in libcdio about libvcdinfo merely disables a minor
feature in the libcdio library.
So technically if you want a "full-featured" libcdio, then you would
have to do a 3 step lin -- lin libcdio, lin vcdimager, lin libcdio.
But just "lin libcdio vcdimager" works fine here and goes to completion
and installation.
I have also version bumped libcdio and vcdimager to the latest
available versions.
tchan
Previous comments:
------------------------------------------------------------------------
Mon, 07/11/2005 - 02:22 : dveatch
Attachment: http://lunar-linux.org/files/issues/libcdio-0.74.bz2 (6.77 KB)
Having a problem with this. During the configure is shows this;
checking for keypad in -lncurses... yes
checking for libvcdinfo >= 0.7.21... Package libcdio was not found in
the pkg-config search path.
Perhaps you should add the directory containing `libcdio.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libcdio', required by 'libvcdinfo', not found
configure: WARNING: a new enough libvcdinfo not found.
AFAICT libvcdinfo comes from vcdimager. So I updated my vcdimager
module to 0.7.22, lined and the ./configure phase failed with ;
checking for libcdio >= 0.72... Package libcdio was not found in the
pkg-config search path.
Perhaps you should add the directory containing `libcdio.pc'
BTW 0.7.21 fails the same way.
Then during the make of libcdio it fails with this;
ings -Wnested-externs -Wno-sign-compare -MT cddb.o -MD -MP -MF
".deps/cddb.Tpo" -c -o cddb.o cddb.c; \
then mv -f ".deps/cddb.Tpo" ".deps/cddb.Po"; else rm -f
".deps/cddb.Tpo"; exit 1; fi
cddb.c: In function `init_cddb':
cddb.c:120: error: dereferencing pointer to incomplete type
cddb.c:124: error: dereferencing pointer to incomplete type
make[3]: *** [cddb.o] Error 1
make[3]: Leaving directory `/usr/src/libcdio-0.74/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/src/libcdio-0.74/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/libcdio-0.74'
make: *** [all] Error 2
Creating /var/log/lunar/compile/libcdio-0.74.bz2
! Problem detected during BUILD
There seems to be a circular dependency between libcdio and vcdimager.
I also ran into thing on a freshly installed system. Or just maybe it
is way to early in the morning and not enough joe.
--
View: http://lunar-linux.org/?q=node/view/911
Edit: http://lunar-linux.org/?q=project/comments/add/911
More information about the Lunar-bugs
mailing list