Re: [blfs-support] fatal error: goo/gmem.h: No such file or, directory; but file does exist!!; cups-filters
When you installed poppler, you should have created /usr/lib/pkgconfig/poppler.pc. Check to see if that is present. I have no idea what LIBQPDF is. LD_LIBRARY_PATH is for specifying library paths for running programs. I suspect you want LIBRARY_PATH for gcc to find included files. It would help to see the error, but not too much before of after the error. Just the line that actually generates the error and it's output would be fine. -- Bruce Thanks Bruce, /usr/lib/pkgconfig/poppler.pc does not exist. Not sure how to create it or what should be in it. What record I have shows the error as: filter/pdftoopvp/oprs/OPRS.cxx:27:22: fatal error: goo/gmem.h: No such file or directory compilation terminated. make: *** [pdftoopvp-OPRS.o] Error 1 -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] fatal error: goo/gmem.h: No such file or, directory; but file does exist!!; cups-filters
Leon Goldman wrote: I may not be responding correctly so my responses don't end up in the correct thread -- if so, I apologize When you installed poppler, you should have created /usr/lib/pkgconfig/poppler.pc. Check to see if that is present. Actually /usr/lib/pkgconfig/poppler.pc does exist. However, I am using a x86_64 system and have a /usr/lib64/pkgconfig also. When I built poppler and libqpdf I just used teh defaults. In /usr/lib64/pkgconfig there is a poppler.pc file which lists the version as 0.16. The poppler.pc in /usr/lib lists the version as 0.20.5. Should I uninstall and recompile poppler and libqpdf with LIBDIR=/usr/lib64? Would the correct steps be to first do a make uninstall for poppler and libqpf, then remove the directories created when the tarball was extracted, re-extract the archive, then proceed with ./configure --LIBDIR=/usr/lib64 and then try to recompile cups-filters? In LFS we said do do 'ln -sv lib /lib64 ln -sv lib /usr/lib64' All of LFS and BLFS assumes that. The only reason to have separate lib directories is for the case when you have a 32-bit binary program that you can't build with 64-bit system. See the discussion 'iii. LFS Target Architectures' in LFS. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] fatal error: goo/gmem.h: No such file or, directory; but file does exist!!; cups-filters
On Mon, Nov 05, 2012 at 09:39:10AM -0600, Bruce Dubbs wrote: Leon Goldman wrote: Actually /usr/lib/pkgconfig/poppler.pc does exist. However, I am using a x86_64 system and have a /usr/lib64/pkgconfig also. When I built poppler and libqpdf I just used teh defaults. In /usr/lib64/pkgconfig there is a poppler.pc file which lists the version as 0.16. The poppler.pc in /usr/lib lists the version as 0.20.5. Should I uninstall and recompile poppler and libqpdf with LIBDIR=/usr/lib64? Would the correct steps be to first do a make uninstall for poppler and libqpf, then remove the directories created when the tarball was extracted, re-extract the archive, then proceed with ./configure --LIBDIR=/usr/lib64 and then try to recompile cups-filters? In LFS we said do do 'ln -sv lib /lib64 ln -sv lib /usr/lib64' All of LFS and BLFS assumes that. The only reason to have separate lib directories is for the case when you have a 32-bit binary program that you can't build with 64-bit system. See the discussion 'iii. LFS Target Architectures' in LFS. Ah, the 'joys' of multilib. First, I cannot recommend that you ever run 'make uninstall' : that is hardly ever tested - in most cases it will work fine. But if it doesn't, your system might be broken. As Bruce says, we don't support multilib in the book. If your existing system is multilib, you might want to look at cross-lfs (specifically cblfs - from memory, almost everything is built as both 32-bit and 64-bit). For sorting out what you have done : everything in lib64 should be 64-bit (use file to check the binaries), everything in lib on multilib should be 32-bit. You haven't specified -m64 or -m32 on what you've done, so looking at the programs you compiled should tell you if your gcc defaults to 32-bit or 64-bit : I would expect 32-bit but knowing is better than assuming. If you are building as 64-bit, use PKG_CONFIG_PATH=/usr/lib64/pkgconfigfile as well as LIBDIR, and forcing -m64 if you need to. If you build as 32-bit on that system, and 64-bit turns out to be its default, use -m32 as well as .usr/lib. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-support] fatal error: goo/gmem.h: No such file or, directory; but file does exist!!; cups-filters
Thank you all. It would appear that I am too far in over my head and I should quit while I am ahead. Only next choice seems to be to reinstall the OS and leave well enough alone. For now I will leave it as broken as it is an hope I don't make it worse. Leon On 11/05/2012 11:37 AM, Ken Moffat wrote: On Mon, Nov 05, 2012 at 09:39:10AM -0600, Bruce Dubbs wrote: Leon Goldman wrote: Actually /usr/lib/pkgconfig/poppler.pc does exist. However, I am using a x86_64 system and have a /usr/lib64/pkgconfig also. When I built poppler and libqpdf I just used teh defaults. In /usr/lib64/pkgconfig there is a poppler.pc file which lists the version as 0.16. The poppler.pc in /usr/lib lists the version as 0.20.5. Should I uninstall and recompile poppler and libqpdf with LIBDIR=/usr/lib64? Would the correct steps be to first do a make uninstall for poppler and libqpf, then remove the directories created when the tarball was extracted, re-extract the archive, then proceed with ./configure --LIBDIR=/usr/lib64 and then try to recompile cups-filters? In LFS we said do do 'ln -sv lib /lib64 ln -sv lib /usr/lib64' All of LFS and BLFS assumes that. The only reason to have separate lib directories is for the case when you have a 32-bit binary program that you can't build with 64-bit system. See the discussion 'iii. LFS Target Architectures' in LFS. Ah, the 'joys' of multilib. First, I cannot recommend that you ever run 'make uninstall' : that is hardly ever tested - in most cases it will work fine. But if it doesn't, your system might be broken. As Bruce says, we don't support multilib in the book. If your existing system is multilib, you might want to look at cross-lfs (specifically cblfs - from memory, almost everything is built as both 32-bit and 64-bit). For sorting out what you have done : everything in lib64 should be 64-bit (use file to check the binaries), everything in lib on multilib should be 32-bit. You haven't specified -m64 or -m32 on what you've done, so looking at the programs you compiled should tell you if your gcc defaults to 32-bit or 64-bit : I would expect 32-bit but knowing is better than assuming. If you are building as 64-bit, use PKG_CONFIG_PATH=/usr/lib64/pkgconfigfile as well as LIBDIR, and forcing -m64 if you need to. If you build as 32-bit on that system, and 64-bit turns out to be its default, use -m32 as well as .usr/lib. ĸen -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
