Make that $PREFIX/share/pkgconfig
On Sat, Dec 26, 2009 at 1:40 PM, Hops Error, Line 21, alcoholi.c <[email protected]> wrote: > I don't know about python, but gtk relies heavily on pkg-config. Is > your PKG_CONFIG_PATH environment variable set correctly? > > What tipped me off was pangocairo. Pangocairo is not a real package, > it's a set of pkgconfig includes that is built when you compile pango > and cairo in the correct order (I don't remember which offhand) so > that one is aware of the other. It's good that you have it. If the > configure script is checking for that, it's likely using pkgconfig. > > What a lot of packages do to see if you have something is to make a > small c executable and include a header from the package they want to > check. With most gtk and X11 packages, that means calling pkgconfig > -cflags $packagename. So if you try that call on the command line > (e.g. pkgconfig -cflags gtk), given your situation you should get an > error message. > > pc files for pkgconfig are usually located in $PREFIX/share. > PKG_CONFIG_PATH is colon seperated just like PATH. > > For the configure script to recognize something, pkgconfig -libs and > pkgconfig -cflags must both work, and your c compiler needs to be able > to compile a hello world using all the flags both those calls > generate. In other words, this needs to work: > > cat > hello.c << EOF > #include <stdio.h> > int main(){printf("hello world\n");} > EOF > gcc -o test `pkgconfig -cflags gtk` `pkgconfig -libs gtk` hello.c > ./test > > and you can replace gtk with whatever package you need to test for. If > you want to be REALLY sure that it's working correctly, you can even > include a real header from whatever package you're testing for, but > it's not necessary, and the above recipe is generic and can be cut and > pasted to your heart's content. > > On Sat, Dec 26, 2009 at 1:00 AM, > <[email protected]> wrote: >> Send blfs-support mailing list submissions to >> [email protected] >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://linuxfromscratch.org/mailman/listinfo/blfs-support >> or, via email, send a message with subject or body 'help' to >> [email protected] >> >> You can reach the person managing the list at >> [email protected] >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of blfs-support digest..." >> >> >> Today's Topics: >> >> 1. Re: wicd-client (Dr. Edgar Alwers) >> 2. Re: wicd-client (Simon Geard) >> 3. Re: wicd-client (William Immendorf) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Fri, 25 Dec 2009 16:07:04 +0100 >> From: "Dr. Edgar Alwers" <[email protected]> >> Subject: Re: wicd-client >> To: BLFS Support List <[email protected]> >> Message-ID: <[email protected]> >> Content-Type: Text/Plain; charset="iso-8859-1" >> >> Hi William, >> >> On Friday 25 December 2009 01:20:39 William Immendorf wrote: >> >>> >>> Edgar, did you use the latest versions of PyGobject, PyCairo, and >>> PyGTK, and building PyGTK aganst libglade? >>> >> >> Well: >> PyGobject 2.20.0 >> PyCairo 1.8.8 >> PyGTK 2.14.1 >> libglade 2.6.4 >> >> Only PyGobject hast a 2.21 version, but this one does not compile for me, as >> GLI'B > 2.22.4 is required. >> PyGTK build the modules atk, pango, pangocairo, gtk with 2.14 API, gtk.glade >> and gtk.unixprint, as configure tells. >> I built again PyGTK and made a call to wicd-client. This time, I get a >> different error: >> --------------------------- >> Traceback (most recent call last): >> File "/usr/lib/wicd/wicd-client.py", line 38, in <module> >> import gtk >> ImportError: No module named gtk >> --------------------------- >> >> It seems, that the py.gtk is not found by wicd. This could indicate an >> address >> fault. Anyway, it sounds much better now. I shall try to fix it ! >> >> Edgar >> >> -- >> ---------------------- >> Dr. Edgar Alwers >> Weinheim >> >> >> ------------------------------ >> >> Message: 2 >> Date: Sat, 26 Dec 2009 16:45:45 +1300 >> From: Simon Geard <[email protected]> >> Subject: Re: wicd-client >> To: [email protected] >> Message-ID: <[email protected]> >> Content-Type: text/plain; charset="utf-8" >> >> On Fri, 2009-12-25 at 16:07 +0100, Dr. Edgar Alwers wrote: >>> Hi William, >>> >>> On Friday 25 December 2009 01:20:39 William Immendorf wrote: >>> >>> > >>> > Edgar, did you use the latest versions of PyGobject, PyCairo, and >>> > PyGTK, and building PyGTK aganst libglade? >>> > >>> >>> Well: >>> PyGobject 2.20.0 >>> PyCairo 1.8.8 >>> PyGTK 2.14.1 >>> libglade 2.6.4 >>> >>> Only PyGobject hast a 2.21 version, but this one does not compile for me, as >>> GLI'B > 2.22.4 is required. >> >> Two things - first, pygtk 2.14.1 isn't the current version, 2.16 is. >> Might be worth it to try that out. >> >> Second, what version of glib and gtk+ are you running? If these are >> relatively old, the pygobject or pygtk builds may be missing >> functionality that wicd expects to find. The errors mentioned 'gio', for >> example - that went into glib in, I think 2.16. Are you using a version >> older than that? >> >> Simon. >> -------------- next part -------------- >> A non-text attachment was scrubbed... >> Name: not available >> Type: application/pgp-signature >> Size: 198 bytes >> Desc: This is a digitally signed message part >> Url : >> http://linuxfromscratch.org/pipermail/blfs-support/attachments/20091226/10e8228c/attachment-0001.bin >> >> ------------------------------ >> >> Message: 3 >> Date: Fri, 25 Dec 2009 22:13:49 -0600 >> From: William Immendorf <[email protected]> >> Subject: Re: wicd-client >> To: BLFS Support List <[email protected]> >> Message-ID: >> <[email protected]> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> On Fri, Dec 25, 2009 at 9:45 PM, Simon Geard <[email protected]> wrote: >>> Two things - first, pygtk 2.14.1 isn't the current version, 2.16 is. >>> Might be worth it to try that out. >>> >>> Second, what version of glib and gtk+ are you running? If these are >>> relatively old, the pygobject or pygtk builds may be missing >>> functionality that wicd expects to find. The errors mentioned 'gio', for >>> example - that went into glib in, I think 2.16. Are you using a version >>> older than that? >> Try building these versions of Glib, Pango, ATK, GTK+, and PyGTK: >> >> Glib 2.22.3 >> Pango 1.26.2 >> ATK 1.28.0 >> GTK+ 2.18.5 >> PyGTK 2.16.0 >> >> Then try running wicd-client. >> >> -- >> William Immendorf >> The ultimate in free computing. >> Messages in plain text, please, no HTML. >> >> -------------- >> >> "Every nonfree program has a lord, a master -- >> and if you use the program, he is your master." Richard Stallman >> >> >> ------------------------------ >> >> -- >> http://linuxfromscratch.org/mailman/listinfo/blfs-support >> FAQ: http://www.linuxfromscratch.org/blfs/faq.html >> Unsubscribe: See the above information page >> >> End of blfs-support Digest, Vol 1917, Issue 1 >> ********************************************* >> >> > -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
