Ralph Shumaker wrote: > Gregory K. Ruiz-Ade wrote: >> On Dec 11, 2007, at 9:15 PM, Ralph Shumaker wrote: >> >>> I'm having trouble with ./configure,. First, it couldn't find a C >>> compiler. I went into configure.log and saw that one of the >>> compilers it searched for was gcc. I yum installed that, but now it >>> wants an XML::Parser perl module. 'yum list all | grep [Pp]arser | >>> grep XML' shows a few possibilities. But how do I know which one to >>> install? >> >> >> Assuming redhat/fedora/centos, you probably want something like >> "perl-XML-Parser". RH and derivatives name perl modules thusly: >> >> XXX::YYY[::ZZZ] == perl-XXX-YYY[-ZZZ] >> >> So: >> >> $ sudo yum list available | grep -i "xml.*parser" >> Password: >> perl-XML-Parser.i386 2.34-6.1.2.2.1 base >> >> Ah, I was right. >> >> (That was on a CentOS 5 system.) >> >> Gregory >> > I had problems going the cpan2rpm path, but this worked fine. But now I > have a new problem. I don't know how much I should include, so I will > include the whole output. But my untrained eyes don't find any problems > until the end. > > # ./configure > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > checking for gawk... gawk > checking whether make sets $(MAKE)... yes > checking whether to enable maintainer-specific portions of Makefiles... no > checking for style of include used by make... GNU > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ISO C89... none needed > checking dependency style of gcc... gcc3 > checking for intltool >= 0.29... 0.36.1 found > checking for xgettext... /usr/bin/xgettext > checking for msgmerge... /usr/bin/msgmerge > checking for msgfmt... /usr/bin/msgfmt > checking for perl... /usr/bin/perl > checking for XML::Parser... ok > configure: NOTE: This is a development release > checking build system type... i686-pc-linux-gnu > checking host system type... i686-pc-linux-gnu > checking for library containing strerror... none required > checking for gcc... (cached) gcc > checking whether we are using the GNU C compiler... (cached) yes > checking whether gcc accepts -g... (cached) yes > checking for gcc option to accept ISO C89... (cached) none needed > checking dependency style of gcc... (cached) gcc3 > checking for bison... no > checking for byacc... no > checking for flex... no > checking for lex... no > checking whether ln -s works... yes > checking for a sed that does not truncate output... /bin/sed > checking for grep that handles long lines and -e... /bin/grep > checking for egrep... /bin/grep -E > checking for ld used by gcc... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking for /usr/bin/ld option to reload object files... -r > checking for BSD-compatible nm... /usr/bin/nm -B > checking how to recognize dependent libraries... pass_all > checking how to run the C preprocessor... gcc -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking dlfcn.h usability... yes > checking dlfcn.h presence... yes > checking for dlfcn.h... yes > checking for g++... no > checking for c++... no > checking for gpp... no > checking for aCC... no > checking for CC... no > checking for cxx... no > checking for cc++... no > checking for cl.exe... no > checking for FCC... no > checking for KCC... no > checking for RCC... no > checking for xlC_r... no > checking for xlC... no > checking whether we are using the GNU C++ compiler... no > checking whether g++ accepts -g... no > checking dependency style of g++... none > checking for g77... no > checking for xlf... no > checking for f77... no > checking for frt... no > checking for pgf77... no > checking for cf77... no > checking for fort77... no > checking for fl32... no > checking for af77... no > checking for xlf90... no > checking for f90... no > checking for pgf90... no > checking for pghpf... no > checking for epcf90... no > checking for gfortran... no > checking for g95... no > checking for xlf95... no > checking for f95... no > checking for fort... no > checking for ifort... no > checking for ifc... no > checking for efc... no > checking for pgf95... no > checking for lf95... no > checking for ftn... no > checking whether we are using the GNU Fortran 77 compiler... no > checking whether accepts -g... no > checking the maximum length of command line arguments... 98304 > checking command to parse /usr/bin/nm -B output from gcc object... ok > checking for objdir... .libs > checking for ar... ar > checking for ranlib... ranlib > checking for strip... strip > checking if gcc supports -fno-rtti -fno-exceptions... no > checking for gcc option to produce PIC... -fPIC > checking if gcc PIC flag -fPIC works... yes > checking if gcc static flag -static works... yes > checking if gcc supports -c -o file.o... yes > checking whether the gcc linker (/usr/bin/ld) supports shared > libraries... yes > checking whether -lc should be explicitly linked in... no > checking dynamic linker characteristics... GNU/Linux ld.so > checking how to hardcode library paths into programs... immediate > checking whether stripping libraries is possible... yes > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... yes > checking whether to build static libraries... no > configure: creating libtool > appending configuration tag "CXX" to libtool > appending configuration tag "F77" to libtool > checking for ANSI C header files... (cached) yes > checking zlib.h usability... yes > checking zlib.h presence... yes > checking for zlib.h... yes > checking for gzread in -lz... yes > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.18... yes > checking libgoffice-0.5... not found > checking for GTK... configure: error: Package requirements ( > libglade-2.0 >= 2.3.6 > gtk+-2.0 >= 2.10.0 > ) were not met: > > No package 'libglade-2.0' found > No package 'gtk+-2.0' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables GTK_CFLAGS > and GTK_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > # > > So, to check my sanity... > > 'yum list all | grep libgoffice' produces nothing. > 'yum list all | grep libglade' produces no exact match (unless libglade2 > which is *already* installed): > libglade2.i386 2.6.0-3.fc7 > installed pygtk2-libglade.i386 > 2.10.6-1.fc7 installed > glade3-libgladeui.i386 3.4.0-5.fc7 > updates glade3-libgladeui-devel.i386 > 3.4.0-5.fc7 updates > libglade.i386 1:0.17-19.fc6 > fedora libglade-devel.i386 > 1:0.17-19.fc6 fedora > libglade-java.i386 2.12.5-6.fc7 > fedora libglade-java-devel.i386 > 2.12.5-6.fc7 fedora > libglade2-devel.i386 2.6.0-3.fc7 > fedora libglademm2.i386 > 2.0.1-2.fc6.rf rpmforge > libglademm2-debuginfo.i386 2.0.1-2.fc6.rf > rpmforge libglademm2-devel.i386 > 2.0.1-2.fc6.rf rpmforge > libglademm24.i386 2.6.3-2.fc6 > fedora libglademm24-devel.i386 > 2.6.3-2.fc6 fedora > ruby-libglade2.i386 0.16.0-18.fc7 updates > > 'yum list all | grep gtk+' produces 1 exact match *already* installed: > gtk+.i386 1:1.2.10-57.fc7 > installed gtk+-devel.i386 > 1:1.2.10-57.fc7 fedora > gtk+extra.i386 2.1.1-5.fc7 > updates gtk+extra-devel.i386 > 2.1.1-5.fc7 updates > > What am I doing wrong? >
Nothing obvious to me -- maybe it'll catch someone else's eye. Can you say again what software you are trying to build? It is not unheard of for configure to get wrong answers (for asking wrong questions, generally, heh!). Regards, ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
