Am Sa, den 10.09.2005 schrieb Strong um 17:21: > Why after gcc-c++, libstc++ and libstdc++-devel update, the src.rpms fail when are compiled? > That's what i get: > ... > checking for dlfcn.h... yes > checking for i686-redhat-linux-gnu-g++... no > checking for i686-redhat-linux-gnu-c++... no > checking for i686-redhat-linux-gnu-gpp... no > checking for i686-redhat-linux-gnu-aCC... no > checking for i686-redhat-linux-gnu-CC... no > checking for i686-redhat-linux-gnu-cxx... no > checking for i686-redhat-linux-gnu-cc++... no > checking for i686-redhat-linux-gnu-cl... no > checking for i686-redhat-linux-gnu-FCC... no > checking for i686-redhat-linux-gnu-KCC... no > checking for i686-redhat-linux-gnu-RCC... no > checking for i686-redhat-linux-gnu-xlC_r... no > checking for i686-redhat-linux-gnu-xlC... no > 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 how to run the C++ preprocessor... /lib/cpp > configure: error: C++ preprocessor "/lib/cpp" fails sanity check > See `config.log' for more details. Check that config.log file. > error: Bad exit status from /var/tmp/rpm-tmp.70505 (%build) I don't know what answer you expect. > Strong. Alexander -- Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773 legal statement: http://www.uni-x.org/legal.html Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.35_FC2smp Serendipity 17:42:57 up 19 days, 14:26, load average: 0.28, 0.24, 0.24
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
