LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Fedora
User Name
Password
Fedora This forum is for the discussion of the Fedora Project.

Notices

Reply
 
Search this Thread
Old 10-14-2012, 10:32 PM   #1
ewlabonte
Member
 
Registered: Mar 2005
Distribution: Slackware 14.1
Posts: 66

Rep: Reputation: 15
pkg-config problem in fedora 17


I'm trying to build e17 in fedora 17. I installed all the dependencies and downloaded the first two library packages: eina and eet. eina built and installed fine. But while running ./configure on eet it gave me the error message "No package 'eina' found". I've run into this type of thing before so I checked for eina.pc and it's in /usr/lib/pkgconfig/. But $PKG_CONFIG_PATH was empty (?) so I ran: PKG_CONFIG_PATH=/usr/lib/pkgconfig. Then I checked it with echo $PKG_CONFIG_PATH and it gave me the right path. But when I ran ./configure again, I got the same error message. "No package 'eina' found"

Here's what I got:

ewl@ghoti:~/Desktop/e17/eet-1.7.0$ ./configure --prefix=/usr
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
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 how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -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 minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a sed that does not truncate output... /usr/bin/sed
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... no
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) 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... yes
checking whether to build eet binary... yes
checking whether to support old eet file format... yes
checking whether to use OpenSSL... auto
checking whether to use cipher... yes
checking whether to use signature... yes
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 pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking whether to build documentation... yes
checking for doxygen... yes
checking whether to use Gnutls... auto
checking for GNUTLS... no
checking whether to use gnutls_x509_crt_verify_hash... yes
checking whether to use gnutls_privkey_sign_data... no
checking whether to use gnutls_pubkey_verify_hash... no
checking whether to activate cipher support in eet... yes
checking whether to activate signature support in eet... yes
checking jpeglib.h usability... yes
checking jpeglib.h presence... yes
checking for jpeglib.h... yes
checking for jpeg_std_error in -ljpeg... yes
checking for libjpeg... yes
checking for zlib... yes
checking for EET... no
configure: error: Package requirements (eina >= 1.2.0 openssl zlib) were not met:

No package 'eina' 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 EET_CFLAGS
and EET_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
 
Old 10-15-2012, 12:05 AM   #2
Rupadhya
Member
 
Registered: Sep 2012
Location: Hoffman Estates, IL
Distribution: Fedora 20
Posts: 167

Rep: Reputation: Disabled
I am not sure, but is it possible that configure can't pick up the PKG_CONFIG_PATH because you didn't export it?
Try this..
Code:
PKG_CONFIG_PATH=/usr/lib/pkgconfig ; export PKG_CONFIG_PATH
echo $PKG_CONFIG_PATH
-Raj
 
Old 10-15-2012, 12:21 AM   #3
ewlabonte
Member
 
Registered: Mar 2005
Distribution: Slackware 14.1
Posts: 66

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by Rupadhya View Post
I am not sure, but is it possible that configure can't pick up the PKG_CONFIG_PATH because you didn't export it?
Try this..
Code:
PKG_CONFIG_PATH=/usr/lib/pkgconfig ; export PKG_CONFIG_PATH
echo $PKG_CONFIG_PATH
-Raj
That did it! Thanks. What I don't know about bash could fill volumes.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
PKG config problem ? fatum Linux - Software 2 10-03-2004 06:52 PM
pkg config problem fatum Linux - General 0 10-01-2004 02:22 PM
pkg-config problem pasalacqua128 Linux - Software 1 06-02-2004 07:31 AM
pkg-config problem melinda_sayang Slackware 2 02-28-2004 08:56 AM
pkg-config problem sandy Linux - Newbie 8 03-07-2003 01:39 PM


All times are GMT -5. The time now is 03:26 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration