Differences between Slackware 11 ../pkgconfig folders and their contents
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Differences between Slackware 11 ../pkgconfig folders and their contents
This has been stymying (sp?) me for about an hour now.
The app is called 'gtkam' and it's a tar.bz2 archive. It's a little digital-camera dumping thingy.
It works great, and I can build it just fine using ./configure make make install. And it runs perfect.
However, I have been trying to use src2pkg to whip it into a .tgz and get it into my pkgtool, but the $#@%# thing won't work.
Now first, I have built SCORES of things with src2pkg, and have never encountered something like this, which is why I am here now.
Here's some paraphrased output from the console:
Code:
sh-3.1$ ./configure
...zoom zoom blah blah blah.. done!
...
Configuration (gtkam 0.1.14):
Build
Source code location: .
Compiler: gcc
Features
Use translations: yes
libgphoto2: yes
bonobo support: no (bonobo-activation, bononoboui libs)
Gnome support: no (gnomeui lib)
GTKAM_C_IDENTIFIER: file:$(datadir)/gnome/help/gtkam/C/gtkam.xml
Gimp support: yes (2.0)
libexif: yes
libexif-gtk: yes
You may run "make" and "make install" now.
sh-3.1# make
WTF !? Now it won't make anymore.. OK, I think it's time for a reboot; if I've got something out of whack behind the scenes, that'll bring it to the forefront..
Grr..
So as you can see, MAKE quits because it cannot find this 'libgphoto2' stuff.
To ensure that libgphoto2 in itself isn't the problem, I just rebuilt & reinstalled it right now, before running make on GTKAM again, and the above errors still resulted when I tried to build GTKAM. Incidentally, there were no make errors or any errors when I built libgphoto2..
As for this:
cannot find the library `/usr/share/pkgconfig/libgphoto2/libgphoto2.la' or unhandled argument `/usr/share/pkgconfig/libgphoto2/libgphoto2.la'
/usr/share/pkgconfig AND /usr/lib/pkgconfig both contain 'libgphoto2-uninstalled.pc' and 'libgphoto2.pc'
Now, earlier today I DID have some sort of error about 'Link follows two paths ***corrupted library link***' which likely had something to do with my accidentally removing part of glib/glib2 from my system. I have since repaired that to the best of my knowledge, by reinstalling the offending pieces from my install DVD.
ldconfig works fine, returning no errors. The system boots and runs fine, and everything I have tested and checked thus far have proven to be OK. But something's amiss here..
Maybe something as simple as maybe /usr/share/pkgconfig is supposed to be symlinked to /usr/lib ??? I dunno, but am still looking. However if anyone has an idea what simple/stupid thing I have overloked here, i really appreciate your feedback..
Thanks
Last edited by GrapefruiTgirl; 10-03-2007 at 02:46 PM.
LOL, yes folks, this is the sort of obscure thing we like to solve on our own, immediately after screaming to the world that "My Computer's Posessssssed!!!!"
OK, in the folder /usr/share/pkgconfig, according to my backup drive, USED TO contain one single file, called atk.pc, which contains:
And so I restored it to my /usr/share/pkgconfig folder, and deleted anything else in there, and presto make MAKES again!!
Can anyone verufy that this is the only thing that's supposed to be in /usr/share/pkgconfig, and also check whether or not this file exists anywhere else on your Slackware 11.0 system??
Finally, for those of you better versed in the glib/glibc world, is this little file (or lack thereof) and its contents solely to blams for my problems, or should I go ahead and reinstall a bunch of stuff from my DVD just to be certain?
Well.... Beats the crap out of me, what happened to my /usr/share/pkgconfig directory. $hit..
However, I wonder if I am correct in assuming that /usr/lib/pkgconfig and /usr/share/pkgconfig contain identical collections of files? If you don't mind Xavier, are you able to check that for me too? No rush, please take your time. All "appears" stable here for the time being
I don't trust my backups for this particular instance, because GENERALLY when I discover a problem, it's because I **just now** caused it, but with this pkgconfig situation, I'm not sure when it actually occurred, or how long ago. My backups go back 7 days.
Thanks
PS - Here's my /usr/lib/pkgconfig (note it contains about HALF the number of files as your ../share/.. directory, but that's likely a matter of what stuff we have installed, yes?
I also have /usr/lib/pkgconfig. When you use prefix (e.g. /usr/local or /usr) and when you don't *.pc files are written to different locations (/usr/local/lib/pkconfig and /usr/lib/pkconfig), that's why you sometimes need to export PKG_CONFIG_PATH to show where the right pc file resides. I think, atk.pc has nothing to do with it.
Thanks for that, A_H ;-]
Not sure if it helps me or not.. my usr/local/lib/pkgconfig folder is all but empty, except for libexif-gtk.pc and libgphoto2.pc, both of which I installed again within the past hour, but ALSO both of which I first installed a week or two ago..
I think, even though my Slack isn't quite stock anymore, I would benefit from seeing what someone who still runs Slacl 11.0 has in their pkgconfig folders.. Anyone ?
No, it absolutely isn't, but I can't change the thread title (atleast, last times I tried to change a thread title it didn't work)..
And I didn't see how it could have been from the start of this, as src2pkg has always (and even through this episode) still build other packages just fine.
I'm sure that whatever has occurred here (read: whatever I have borked) is at system-level, and prolly if it IS still borked, will affect me in weird ways at weird times, until I figure it out.
Just add all three 3 (or 4) pkgconfig directories to the PKG_CONFIG_PATH environmental variable and it should be ok, though no guarantees are given. You can add these to bash_profile.
Last edited by Alien_Hominid; 10-03-2007 at 04:15 PM.
/usr/lib/pkgconfig contains the 'whole collection'. /usr/local/lib/pkgconfig contains 4 items. opt/kde/lib/pkgconfig is irrelevant to this discussion, I believe.
So, what if I were to make /usr/local/lib/pkgconfig a SYMLINK to /usr/lib/pkgconfig (after making sure those 4 items are in there too) ?? This would work wouldn't it? It almost appears as though this is how it was supposed to be to begin with what do you think? Alternately I could simply remove the second folder entirely, and remove it from the CONFIG_PATH too, but the first idea may be safer.
That's exactly how I make it and it works usally perfectly fine, as long as I don't forget to check ld.so.conf if I installed new stuff into strange places and call ldconfig afterwards.
And I call "pkg-config --list-all | grep whatever" from time to time to see, if and what pkg-config actually finds or try pkg-config --exists <packagename> to check a wrong going configure and so on...
And my /usr/share/pkgconfig is identical with /usr/lib/pkgconfig. Same size, same time stamp.
GG, what exactly are you trying to do? Is this still related to "I just need a few Gnome libs for something.."?
That's exactly how I make it and it works usally perfectly fine, as long as I don't forget to check ld.so.conf if I installed new stuff into strange places and call ldconfig afterwards.
AFAIK I don't install anything to 'weird places' so I should be OK there. I run ldconfig occasionally, but it runs on boot anyhow.
And I call "pkg-config --list-all | grep whatever" from time to time to see, if and what pkg-config actually finds or try pkg-config --exists <packagename> to check a wrong going configure and so on...
I'll make a mental note of this-- thank you.
And my /usr/share/pkgconfig is identical with /usr/lib/pkgconfig. Same size, same time stamp.
Thank you even more for this verification! XX
GG, what exactly are you trying to do? Is this still related to "I just need a few Gnome libs for something.."? "..related to.."-- YES. This problem developed after I removed what I *thought* were the items I had managed to install while dealing with that worm-farm of Gnome libs. It seems I may have removed one too many things, and then this issue subsequently arose today. I think with this info you have provided, as well as what Alien_H has suggested, I can get it fixed now.
NOTE - I am no longer "..in need of a few Gnome libs.."
Thanks to everyone in here-- now I'm on the 'road to recovery"
EDIT - Here's something weird: Why would my ld.so.conf file contain a path into a Trash bin? LMAO @ /root/.local/share/Trash/files/package-xmms/usr/lib
Last edited by GrapefruiTgirl; 10-03-2007 at 04:56 PM.
You can. But you were asking about /usr/share. I don't know about /user/share and what programs pc files are expected to be found there.
Good point. And me neither.. But if they're ALL in there, then any one of them can be found at any given time though I think the symlink idea is good..
I have synced all the pkgconfig directories (except the KDE one) so hopefully I won't run into trouble by having the .pc files in all directories.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
make MAKES again!!
Thank you!! 
