Bug 195733 – dev-util/libconf-0.42.10-r1 emerge fails due to missing conf2xml() in -lconf2xml

• Status: RESOLVED DUPLICATE of bug 117061
• Product: Gentoo Linux

[Description Vladimir G. Ivanovic 2007-10-13 18:37:37 UTC]

Here is a snippet from the log file:

checking for #include <conf2xml.h>
... yes
checking for conf2xml() in -lconf2xml... no
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of
necessary libraries and/or headers.  Check the mkmf.log file for more
details.  You may need configuration options.

Provided configuration options:
	--with-opt-dir
	--without-opt-dir
	--with-opt-include
	--without-opt-include=${opt-dir}/include
	--with-opt-lib
	--without-opt-lib=${opt-dir}/lib
	--with-make-prog
	--without-make-prog
	--srcdir=.
	--curdir
	--ruby=/usr/bin/ruby18
	--with-conf2xmllib
	--without-conf2xmllib

[Comment 1 Vladimir G. Ivanovic 2007-10-13 18:38:32 UTC]

Created attachment 133349 [details]
build log file

[Comment 2 Vladimir G. Ivanovic 2007-10-13 18:39:07 UTC]

Created attachment 133350 [details]
Emerge info

[Comment 3 dams (RETIRED) 2007-10-13 19:06:00 UTC]

you can't compile the ruby binding without the C binding.
quick fix : don't compile libconf with the ruby useflag. Edit your /etc/gentoo/package.use

[Comment 4 Dolores 2007-11-20 02:09:04 UTC]

(In reply to comment #3)
> you can't compile the ruby binding without the C binding.
> quick fix : don't compile libconf with the ruby useflag. Edit your
> /etc/gentoo/package.use
> 

Whatever, revdep-rebuild will try to emerge -1 libconf in vain repeatedly

[Comment 5 Ian Abbott 2007-12-01 12:11:20 UTC]

(In reply to comment #3)
> you can't compile the ruby binding without the C binding.
> quick fix : don't compile libconf with the ruby useflag. Edit your
> /etc/gentoo/package.use

How does one get the C binding?

[Comment 6 Holger Hoffstätte 2009-09-20 14:38:04 UTC]

This is a duplicate of bug#117061 (which contains a solution), could someone please close?

[Comment 7 Torsten Veller (RETIRED) 2009-11-11 20:44:25 UTC]

*** This bug has been marked as a duplicate of bug 117061 ***