LINUX.ORG.RU
Форум — Linux-install  

GCC без gcc :)


0

0

Доброго времени суток. Каким то образом я умудрился загубит свой GCC. При попытке что либо собрать получаю: checking how to run the C preprocessor... /lib/cpp configure: error: C preprocessor "/lib/cpp" fails sanity check See `config.log' for more details. make: *** [configure-build-libiberty] Ошибка 1

Переустановил пакеты с оригинального диска,- эффект тот же :( Решил что это судьба, и пришло время обновить gcc:) Затянул себе последний gcc-4.1.2, да ни тут то было:))) Как же его собрать то если компилятор то и не работает. Гуглил, но решение не обнаружил,,, Буду рад если кто поможет советом как вийти из этого закалдованного круга:) Спасибо. P.S. root@dmitry:/# uname -a Linux dmitry 2.6.20.7 #2 SMP Tue Apr 17 12:03:01 MDT 2007 i686 athlon-4 i386 GNU/Linux root@dmitry:/# gcc -v Reading specs from /usr/lib/gcc/i486-slackware-linux/3.4.6/specs Configured with: ../gcc-3.4.6/configure --prefix=/usr --enable-shared --enable-threads=posix --enable-__cxa_atexit --disable-checking --with-gnu-ld --verbose --target=i486-slackware-linux --host=i486-slackware-linux Thread model: posix gcc version 3.4.6

★★★
← Апдейтить SuSE из командной строки за исключением kernel-* и ещё нескольких пакетов
Как установить Mandriva spring? →

Во-первых нужно See `config.log' for more details.
А во-вторых, что даёт команда gcc --version?

UVV ★★★★★
()
Ответ на: комментарий от UVV 

выдаю:
root@dmitry:/tmp/gcc-4.1.2# cat config.log
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

configure:600: checking host system type
configure:621: checking target system type
configure:639: checking build system type
configure:694: checking for a BSD compatible install
configure:747: checking whether ln works
configure:771: checking whether ln -s works
configure:1825: checking for gcc
configure:1938: checking whether the C compiler (gcc  ) works
configure:1954: gcc -o conftest    conftest.c  1>&5
configure:1980: checking whether the C compiler (gcc  ) is a cross-compiler
configure:1985: checking whether we are using GNU C
configure:2013: checking whether gcc accepts -g
configure:2080: checking for gnatbind
configure:2145: checking whether compiler driver understands Ada
configure:2177: checking how to compare bootstrapped objects
configure:2281: checking for correct version of gmp.h
configure:2294: gcc -c -g -O2   conftest.c 1>&5
configure:2307: checking for MPFR
configure:2320: gcc -o conftest -g -O2    conftest.c  -lmpfr -lgmp 1>&5
configure:3319: checking for bison
configure:3359: checking for bison
configure:3398: checking for gm4
configure:3437: checking for flex
configure:3477: checking for flex
configure:3516: checking for makeinfo
configure:3569: checking for expect
configure:3610: checking for runtest
configure:3658: checking for i686-pc-linux-gnu-ar
configure:3733: checking for i686-pc-linux-gnu-as
configure:3808: checking for i686-pc-linux-gnu-dlltool
configure:3839: checking for dlltool
configure:3883: checking for i686-pc-linux-gnu-ld
configure:3958: checking for i686-pc-linux-gnu-lipo
configure:3989: checking for lipo
configure:4033: checking for i686-pc-linux-gnu-nm
configure:4108: checking for i686-pc-linux-gnu-ranlib
configure:4178: checking for i686-pc-linux-gnu-strip
configure:4248: checking for i686-pc-linux-gnu-windres
configure:4279: checking for windres
configure:4323: checking for i686-pc-linux-gnu-objcopy
configure:4398: checking for i686-pc-linux-gnu-objdump
configure:4480: checking for i686-pc-linux-gnu-ar
configure:4555: checking for i686-pc-linux-gnu-as
configure:4630: checking for i686-pc-linux-gnu-cc
configure:4705: checking for i686-pc-linux-gnu-c++
configure:4780: checking for i686-pc-linux-gnu-dlltool
configure:4811: checking for dlltool
configure:4855: checking for i686-pc-linux-gnu-gcc
configure:4925: checking for i686-pc-linux-gnu-gcj
configure:5000: checking for i686-pc-linux-gnu-gfortran
configure:5031: checking for gfortran
configure:5075: checking for i686-pc-linux-gnu-ld
configure:5150: checking for i686-pc-linux-gnu-lipo
configure:5181: checking for lipo
configure:5225: checking for i686-pc-linux-gnu-nm
configure:5300: checking for i686-pc-linux-gnu-objdump
configure:5375: checking for i686-pc-linux-gnu-ranlib
configure:5445: checking for i686-pc-linux-gnu-strip
configure:5520: checking for i686-pc-linux-gnu-windres
configure:5551: checking for windres
configure:5594: checking where to find the target ar
configure:5619: checking where to find the target as
configure:5644: checking where to find the target cc
configure:5669: checking where to find the target c++
configure:5697: checking where to find the target c++ for libstdc++
configure:5725: checking where to find the target dlltool
configure:5750: checking where to find the target gcc
configure:5775: checking where to find the target gcj
configure:5803: checking where to find the target gfortran
configure:5831: checking where to find the target ld
configure:5856: checking where to find the target lipo
configure:5871: checking where to find the target nm
configure:5896: checking where to find the target objdump
configure:5921: checking where to find the target ranlib
configure:5946: checking where to find the target strip
configure:5971: checking where to find the target windres
configure:6024: checking whether to enable maintainer-specific portions of Makefiles
configure:6071: checking if symbolic links between directories work

root@dmitry:/tmp/gcc-4.1.2# gcc --version
gcc (GCC) 3.4.6
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

papay ★★★
() автор топика
Ответ на: комментарий от UVV 

вот другой лог:

root@dmitry:/tmp/licq-1.3.2# cat config.log

....
,,,,,,

configure:3148: result: /lib/cpp
configure:3173: /lib/cpp  conftest.c
In file included from /usr/include/bits/posix1_lim.h:153,
                 from /usr/include/limits.h:144,
                 from /usr/lib/gcc/i486-slackware-linux/3.4.6/include/limits.h:122,
                 from /usr/lib/gcc/i486-slackware-linux/3.4.6/include/syslimits.h:7,
                 from /usr/lib/gcc/i486-slackware-linux/3.4.6/include/limits.h:11,
                 from configure:3174:
/usr/include/bits/local_lim.h:36:26: linux/limits.h: No such file or directory
configure:3179: $? = 1
configure: failed program was:
| #line 3159 "configure"
| /* confdefs.h.  */
|
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE "licq"
| #define VERSION "1.3.2"
| #define PACKAGE "licq"
| #define VERSION "1.3.2"
| #define INT_VERSION 1032
| #define USE_FIFO 1
| /* end confdefs.h.  */
| #ifdef __STDC__
| # include <limits.h>
| #else
| # include <assert.h>
| #endif
|                      Syntax error
configure:3173: /lib/cpp  conftest.c
In file included from /usr/include/bits/posix1_lim.h:153,
                 from /usr/include/limits.h:144,
                 from /usr/lib/gcc/i486-slackware-linux/3.4.6/include/limits.h:122,
                 from /usr/lib/gcc/i486-slackware-linux/3.4.6/include/syslimits.h:7,
                 from /usr/lib/gcc/i486-slackware-linux/3.4.6/include/limits.h:11,
                 from configure:3174:
/usr/include/bits/local_lim.h:36:26: linux/limits.h: No such file or directory
configure:3179: $? = 1
configure: failed program was:
| #line 3159 "configure"
| /* confdefs.h.  */
|
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE "licq"
| #define VERSION "1.3.2"
| #define PACKAGE "licq"
| #define VERSION "1.3.2"
| #define INT_VERSION 1032
| #define USE_FIFO 1
| /* end confdefs.h.  */
| #ifdef __STDC__
| # include <limits.h>
| #else
| # include <assert.h>
| #endif
|                      Syntax error
configure:3247: error: C preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.

## ---------------- ##
## Cache variables. ##
## ---------------- ##

,,,
,,,,,,
,,,,,,,,,
configure: exit 1

papay ★★★
() автор топика
Ответ на: комментарий от Deleted

Понял,,, Большое спасибо! :)

papay ★★★
() автор топика
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.
← Апдейтить SuSE из командной строки за исключением kernel-* и ещё нескольких пакетов
Linux-install
Как установить Mandriva spring? →