On 23 April 2010 22:41, James Richard Tyrer <[email protected]> wrote: > I find, as I noted here: > > http://techbase.kde.org/Getting_Started/Build/KDE4/LFS#TagLib > > that GST Plugins Good will only build the TagLib plugin if I set: > > HAVE_CXX="yes". I was wondering if other people have this issue and if > it should be added to the BLFS SVN. >
As with many things in wikis, it's hard to know when it was added, and whether it is still correct (or, indeed, if it ever was - I don't doubt that whoever noted it had a problem which it solved, but I question if it was the right fix). I've given up on kde4, but I do still build taglib-1.5 and in my log for gst-plugins-good-0.10.16 (which is what I'm currently using) I see configure: *** checking feature: taglib tagging library *** configure: *** for plug-ins: taglib *** checking for TAGLIB... yes checking to see if c++ compiler understands -Wno-attributes... yes configure: *** These plugins will be built: taglib FWIW, HAVE_CXX in gst-plugins-good overrides the tests that for me give the following output: checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking whether we are using the GNU C++ compiler... (cached) yes checking whether g++ accepts -g... (cached) yes checking dependency style of g++... (cached) gcc3 checking how to run the C++ preprocessor... g++ -E checking for ld used by g++... /usr/bin/ld -m elf_x86_64 checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC -DPIC checking if g++ PIC flag -fPIC -DPIC works... yes checking if g++ static flag -static works... yes checking if g++ supports -c -o file.o... yes checking if g++ supports -c -o file.o... (cached) yes checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking for g++... yes checking how to run the C++ preprocessor... g++ -E - that makes me think that any LFS system needing HAVE_CXX would need it in many, or most, c++ packages which use autotools (and I would expect cmake to be equally problematic, but I neither know nor care about that any more). OTOH, if *your* system actually needs that variable to be set, then I stand corrected. If that is the case, which version of LFS, and have you upgraded gcc or added a newer version of gcc after you built it ? ĸen -- After tragedy, and farce, "OMG poneys!" -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
