LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 01-07-2005, 05:43 AM   #16
jhartney
LQ Newbie
 
Registered: Dec 2004
Distribution: SuSE 9.0
Posts: 26

Original Poster
Rep: Reputation: 15

Well, I found it:

linux:~ # find / -name "glib.h"
/opt/gnome/include/glib-1.2/glib.h
/opt/gnome/include/glib-2.0/glib.h
/usr/local/include/glib.h
/home/jhartney/Desktop/Trash/glib-1.2.2/glib.h
/home/jhartney/Desktop/Trash/glib-1.2.9/glib.h
find: /proc/18757/fd: No such file or directory
 
Old 01-07-2005, 05:47 AM   #17
Dark_Helmet
Senior Member
 
Registered: Jan 2003
Posts: 2,786

Rep: Reputation: 370Reputation: 370Reputation: 370Reputation: 370
Ok, now execute pkg-config --modversion --cflags glib
 
Old 01-07-2005, 05:55 AM   #18
jhartney
LQ Newbie
 
Registered: Dec 2004
Distribution: SuSE 9.0
Posts: 26

Original Poster
Rep: Reputation: 15
linux:~ # pkg -config --modversion --cflags glib
bash: pkg: command not found


that can't be good. What do those commands do?
 
Old 01-07-2005, 06:00 AM   #19
Dark_Helmet
Senior Member
 
Registered: Jan 2003
Posts: 2,786

Rep: Reputation: 370Reputation: 370Reputation: 370Reputation: 370
Actually, pkg-config has no space

When building software, the compiler needs to know where certain files are. The glib.h file I mentioned earlier (a header file) can be thought of as an interface to the library. The compiler will need to know where both the header file and the library reside. The pkg-config program is a somewhat consistent way of doing it.

The --modversion tells pkg-config to display the librariy's version. The --cflags tells pkg-config to display the arguments the compiler needs.

Everything you have told me to this point indicates that glib is properly installed. This is the last command to verify that. If it is properly installed, then there's something else at the core of the software compile problem you mentioned at the start.

So give pkg-config another shot, and let me know what it spits out.
 
Old 01-07-2005, 06:02 AM   #20
jhartney
LQ Newbie
 
Registered: Dec 2004
Distribution: SuSE 9.0
Posts: 26

Original Poster
Rep: Reputation: 15
linux:/home/jhartney # pkg-config --modversion --cflags glib
1.2.10
-I/opt/gnome/include/glib-1.2 -I/opt/gnome/lib/glib/include


All looks well to me,,,no?
 
Old 01-07-2005, 06:07 AM   #21
Dark_Helmet
Senior Member
 
Registered: Jan 2003
Posts: 2,786

Rep: Reputation: 370Reputation: 370Reputation: 370Reputation: 370
Yeah, that looks good to me, and it matches with my Red Hat system. So, now I need you to paste the error message from trying to compile one of the tarballs.
 
Old 01-07-2005, 06:08 AM   #22
jhartney
LQ Newbie
 
Registered: Dec 2004
Distribution: SuSE 9.0
Posts: 26

Original Poster
Rep: Reputation: 15
yeah I gotta find one of those...this might take a minute
 
Old 01-07-2005, 06:12 AM   #23
Dark_Helmet
Senior Member
 
Registered: Jan 2003
Posts: 2,786

Rep: Reputation: 370Reputation: 370Reputation: 370Reputation: 370
Actually, if you could, try to compile it again, and paste the error from the terminal. That'll make sure that the ldconfig from earlier has been included, and that the error is 100% current.
 
Old 01-07-2005, 06:15 AM   #24
jhartney
LQ Newbie
 
Registered: Dec 2004
Distribution: SuSE 9.0
Posts: 26

Original Poster
Rep: Reputation: 15
i still gotta find a tarball that is giving me the errors...i've been doing so many things the last couple hours that I have no idea where I put it.
 
Old 01-07-2005, 06:17 AM   #25
Dark_Helmet
Senior Member
 
Registered: Jan 2003
Posts: 2,786

Rep: Reputation: 370Reputation: 370Reputation: 370Reputation: 370
And one other thing I'm curious about: the find command listed a couple glib.h files in your Trash bin. What was that about? I mean, were you manually poking around with those files? What was it you were trying to do, and what things did you try? Everything seems to be ok, but that made me raise an eyebrow.
 
Old 01-07-2005, 06:22 AM   #26
jhartney
LQ Newbie
 
Registered: Dec 2004
Distribution: SuSE 9.0
Posts: 26

Original Poster
Rep: Reputation: 15
I tried installing glib a few times in the past. When they didn't work i just threw the untarred crap into my trash bin. No worries.
 
Old 01-07-2005, 06:23 AM   #27
jhartney
LQ Newbie
 
Registered: Dec 2004
Distribution: SuSE 9.0
Posts: 26

Original Poster
Rep: Reputation: 15
ok...funny how when you NEED an error to occur, you can't get it. Any ideas on a package to install that might need glib >= 1.2.0?
 
Old 01-07-2005, 06:25 AM   #28
jhartney
LQ Newbie
 
Registered: Dec 2004
Distribution: SuSE 9.0
Posts: 26

Original Poster
Rep: Reputation: 15
oh...just so you can put your eyebrow down....no I wasn't looking through those header files manually...haha
 
Old 01-07-2005, 06:32 AM   #29
Dark_Helmet
Senior Member
 
Registered: Jan 2003
Posts: 2,786

Rep: Reputation: 370Reputation: 370Reputation: 370Reputation: 370
Hehe... no, no more raised eyebrow. I was worried you may have been moving files around by hand. It wouldn't have been the first time it's happened.

As for a package that uses glib...

Here's a URL to one that requires it:
ftp://ftp.gnome.org/pub/GNOME/source...0.5.17.tar.bz2

It's a support library for Gnome. You already have it installed I'm sure, but all you're interested in is the ./configure step anyway.
 
Old 01-07-2005, 06:34 AM   #30
jhartney
LQ Newbie
 
Registered: Dec 2004
Distribution: SuSE 9.0
Posts: 26

Original Poster
Rep: Reputation: 15
Perfect file for the job. Here's the output:

linux:/home/jhartney/Desktop/ORBit-0.5.17 # ./configure
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... missing
checking for working autoconf... missing
checking for working automake... missing
checking for working autoheader... missing
checking for working makeinfo... missing
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix...
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for ld used by GCC... /usr/i586-suse-linux/bin/ld
checking if the linker (/usr/i586-suse-linux/bin/ld) is GNU ld... yes
checking for /usr/i586-suse-linux/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependant libraries... pass_all
checking command to parse /usr/bin/nm -B output... ok
checking how to run the C preprocessor... gcc -E
checking for dlfcn.h... yes
checking for ranlib... ranlib
checking for strip... strip
checking for objdir... .libs
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 if gcc supports -c -o file.lo... yes
checking if gcc supports -fno-rtti -fno-exceptions... yes
checking whether the linker (/usr/i586-suse-linux/bin/ld) supports shared libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking whether -lc should be explicitly linked in... no
creating libtool
checking whether to enable maintainer-specific portions of Makefiles... no
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 a BSD compatible install... /usr/bin/install -c
checking for indentation command to pipe generated c-files through... indent -npro -bad -bap -bc -sob -br -ce -cli2 -npcs -di1 -psl -i3 -lp -st
checking for glib-config... no
checking for GLIB - version >= 1.2.1... no
*** The glib-config script installed by GLIB could not be found
*** If GLIB was installed in PREFIX, make sure PREFIX/bin is in
*** your path, or set the GLIB_CONFIG environment variable to the
*** full path to glib-config.
configure: error:
*** GLIB 1.2.1 or better is required. The latest version of GLIB
*** is always available from ftp://ftp.gtk.org/.
linux:/home/jhartney/Desktop/ORBit-0.5.17 #



I really don't get this. haha
 
  


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
glib-2.0 problems. Sjonnie48 Mandriva 5 11-26-2005 01:34 AM
glib problems njjk DamnSmallLinux 2 04-22-2005 04:18 PM
glib problems migu Mandriva 3 02-26-2005 06:02 PM
[GLIB] Problems Installing GLIB ThA_eLMo_GoD Linux - Newbie 2 09-04-2004 06:27 PM
Problems relating to glib 1.2.10 and glib 1.2.9 p3ngu!n Mandriva 10 05-23-2004 10:03 PM


All times are GMT -5. The time now is 04:31 AM.

Main Menu
Advertisement
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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration