Newsgroup: it.comp.os.linux.iniziare
Titolo: errore da ./configure ...?

Salve a tutti,
...Fedora core8.
la situazione di errore è questa :
file tar scompatto il contenuto lancio un
#./configure
questo l'output
  Configure launch with the following arguments: 
/usr/local/share/config.site /usr/local/etc/config.site
  checking for a BSD-compatible install... /usr/bin/install -c
  checking whether build environment is sane... yes
  checking for a thread-safe mkdir -p... /bin/mkdir -p
  checking for gawk... gawk
  checking whether make sets $(MAKE)... yes
  checking for g++... g++
  checking for C++ compiler default output file name... a.out
  checking whether the C++ compiler works... yes
  checking whether we are cross compiling... no
  checking for suffix of executables...
  checking for suffix of object files... o
  checking whether we are using the GNU C++ compiler... yes
  checking whether g++ accepts -g... yes
  checking for style of include used by make... GNU
  checking dependency style of g++... gcc3
  checking for a BSD-compatible install... /usr/bin/install -c
  checking build system type... i686-pc-linux-gnulibc1
  checking host system type... i686-pc-linux-gnulibc1
  checking for gcc... gcc
  checking whether we are using the GNU C compiler... yes
  checking whether gcc accepts -g... yes
  checking for gcc option to accept ISO C89... unsupported
  checking dependency style of gcc... gcc3
  checking for a sed that does not truncate output... /bin/sed
  checking for grep that handles long lines and -e... /bin/grep
  checking for egrep... /bin/grep -E
  checking for ld used by gcc... /usr/bin/ld
  checking if the linker (/usr/bin/ld) is GNU ld... yes
  checking for /usr/bin/ld option to reload object files... -r
  checking for BSD-compatible nm... /usr/bin/nm -B
  checking whether ln -s works... yes
  checking how to recognize dependent libraries... pass_all
  checking how to run the C preprocessor... /lib/cpp
  configure: error: C preprocessor "/lib/cpp" fails sanity check
  See `config.log' for more details.
vado allora a vedere nel file cinfig.log greppando per errore e...
  conftest.c:11:19: error: stdio.h: No such file or directory
  conftest.c:12:23: error: sys/types.h: No such file or directory
  conftest.c:13:22: error: sys/stat.h: No such file or directory
  conftest.c:16: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before '*' token
  conftest.c:50: error: expected declaration specifiers or '...' before 
'FILE'
  |    These don't provoke an error unfortunately, instead are silently 
treated
  |    as 'x'.  The following induces an error, until -std is added to get
  conftest.c:11:19: error: stdio.h: No such file or directory
  conftest.c:12:23: error: sys/types.h: No such file or directory
  conftest.c:13:22: error: sys/stat.h: No such file or directory
  conftest.c:16: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before '*' token
  conftest.c:50: error: expected declaration specifiers or '...' before 
'FILE'
  |    These don't provoke an error unfortunately, instead are silently 
treated
  |    as 'x'.  The following induces an error, until -std is added to get
  conftest.c:11:19: error: stdio.h: No such file or directory
  conftest.c:12:23: error: sys/types.h: No such file or directory
  conftest.c:13:22: error: sys/stat.h: No such file or directory
  conftest.c:16: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before '*' token
  conftest.c:50: error: expected declaration specifiers or '...' before 
'FILE'
  |    These don't provoke an error unfortunately, instead are silently 
treated
  |    as 'x'.  The following induces an error, until -std is added to get
  cc1: error: unrecognized command line option "-std"
  |    These don't provoke an error unfortunately, instead are silently 
treated
  |    as 'x'.  The following induces an error, until -std is added to get
  <command line>:1:2: error: missing '(' after predicate
  conftest.c:11:19: error: stdio.h: No such file or directory
  conftest.c:12:23: error: sys/types.h: No such file or directory
  conftest.c:13:22: error: sys/stat.h: No such file or directory
  conftest.c:16: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before '*' token
  conftest.c:50: error: expected declaration specifiers or '...' before 
'FILE'
  |    These don't provoke an error unfortunately, instead are silently 
treated
  |    as 'x'.  The following induces an error, until -std is added to get
  <command line>:1:2: error: missing '(' after predicate
  conftest.c:11:19: error: stdio.h: No such file or directory
  conftest.c:12:23: error: sys/types.h: No such file or directory
  conftest.c:13:22: error: sys/stat.h: No such file or directory
  conftest.c:16: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before '*' token
  conftest.c:50: error: expected declaration specifiers or '...' before 
'FILE'
  |    These don't provoke an error unfortunately, instead are silently 
treated
  |    as 'x'.  The following induces an error, until -std is added to get
  conftest.c:11:19: error: stdio.h: No such file or directory
  conftest.c:12:23: error: sys/types.h: No such file or directory
  conftest.c:13:22: error: sys/stat.h: No such file or directory
  conftest.c:16: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before '*' token
  conftest.c:50: error: expected declaration specifiers or '...' before 
'FILE'
  |    These don't provoke an error unfortunately, instead are silently 
treated
  |    as 'x'.  The following induces an error, until -std is added to get
  /usr/lib/gcc/i386-redhat-linux/4.1.2/include/limits.h:122:61: error: 
limits.h: No such file or directory
  | 		     Syntax error
  /usr/lib/gcc/i386-redhat-linux/4.1.2/include/limits.h:122:61: error: 
limits.h: No such file or directory
  | 		     Syntax error
  conftest.c:13: error: assert.h: No such file or directory
  | 		     Syntax error
  conftest.c:13: error: assert.h: No such file or directory
  | 		     Syntax error
  /usr/lib/gcc/i386-redhat-linux/4.1.2/include/limits.h:122:61: error: 
limits.h: No such file or directory
  | 		     Syntax error
  /usr/lib/gcc/i386-redhat-linux/4.1.2/include/limits.h:122:61: error: 
limits.h: No such file or directory
  | 		     Syntax error
  /usr/lib/gcc/i386-redhat-linux/4.1.2/include/limits.h:122:61: error: 
limits.h: No such file or directory
  | 		     Syntax error
  /usr/lib/gcc/i386-redhat-linux/4.1.2/include/limits.h:122:61: error: 
limits.h: No such file or directory
  | 		     Syntax error
  configure:5394: error: C preprocessor "/lib/cpp" fails sanity check
  conftest.c:11:19: error: stdio.h: No such file or directory
  conftest.c:12:23: error: sys/types.h: No such file or directory
  conftest.c:13:22: error: sys/stat.h: No such file or directory
  conftest.c:16: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before '*' token
  conftest.c:50: error: expected declaration specifiers or '...' before 
'FILE'
  |    These don't provoke an error unfortunately, instead are silently 
treated
  |    as 'x'.  The following induces an error, until -std is added to get
  conftest.c:11:19: error: stdio.h: No such file or directory
  conftest.c:12:23: error: sys/types.h: No such file or directory
  conftest.c:13:22: error: sys/stat.h: No such file or directory
  conftest.c:16: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before '*' token
  conftest.c:50: error: expected declaration specifiers or '...' before 
'FILE'
  |    These don't provoke an error unfortunately, instead are silently 
treated
  |    as 'x'.  The following induces an error, until -std is added to get
  conftest.c:11:19: error: stdio.h: No such file or directory
  conftest.c:12:23: error: sys/types.h: No such file or directory
  conftest.c:13:22: error: sys/stat.h: No such file or directory
  conftest.c:16: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before '*' token
  conftest.c:50: error: expected declaration specifiers or '...' before 
'FILE'
  |    These don't provoke an error unfortunately, instead are silently 
treated
  |    as 'x'.  The following induces an error, until -std is added to get
  cc1: error: unrecognized command line option "-std"
  |    These don't provoke an error unfortunately, instead are silently 
treated
  |    as 'x'.  The following induces an error, until -std is added to get
  <command line>:1:2: error: missing '(' after predicate
  conftest.c:11:19: error: stdio.h: No such file or directory
  conftest.c:12:23: error: sys/types.h: No such file or directory
  conftest.c:13:22: error: sys/stat.h: No such file or directory
  conftest.c:16: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before '*' token
  conftest.c:50: error: expected declaration specifiers or '...' before 
'FILE'
  |    These don't provoke an error unfortunately, instead are silently 
treated
  |    as 'x'.  The following induces an error, until -std is added to get
  <command line>:1:2: error: missing '(' after predicate
  conftest.c:11:19: error: stdio.h: No such file or directory
  conftest.c:12:23: error: sys/types.h: No such file or directory
  conftest.c:13:22: error: sys/stat.h: No such file or directory
  conftest.c:16: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before '*' token
  conftest.c:50: error: expected declaration specifiers or '...' before 
'FILE'
  |    These don't provoke an error unfortunately, instead are silently 
treated
  |    as 'x'.  The following induces an error, until -std is added to get
  conftest.c:11:19: error: stdio.h: No such file or directory
  conftest.c:12:23: error: sys/types.h: No such file or directory
  conftest.c:13:22: error: sys/stat.h: No such file or directory
  conftest.c:16: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before '*' token
  conftest.c:50: error: expected declaration specifiers or '...' before 
'FILE'
  |    These don't provoke an error unfortunately, instead are silently 
treated
  |    as 'x'.  The following induces an error, until -std is added to get
  /usr/lib/gcc/i386-redhat-linux/4.1.2/include/limits.h:122:61: error: 
limits.h: No such file or directory
  | 		     Syntax error
  /usr/lib/gcc/i386-redhat-linux/4.1.2/include/limits.h:122:61: error: 
limits.h: No such file or directory
  | 		     Syntax error
  conftest.c:13: error: assert.h: No such file or directory
  | 		     Syntax error
  conftest.c:13: error: assert.h: No such file or directory
  | 		     Syntax error
  /usr/lib/gcc/i386-redhat-linux/4.1.2/include/limits.h:122:61: error: 
limits.h: No such file or directory
  | 		     Syntax error
  /usr/lib/gcc/i386-redhat-linux/4.1.2/include/limits.h:122:61: error: 
limits.h: No such file or directory
  | 		     Syntax error
  /usr/lib/gcc/i386-redhat-linux/4.1.2/include/limits.h:122:61: error: 
limits.h: No such file or directory
  | 		     Syntax error
  /usr/lib/gcc/i386-redhat-linux/4.1.2/include/limits.h:122:61: error: 
limits.h: No such file or directory
  | 		     Syntax error
  configure:5394: error: C preprocessor "/lib/cpp" fails sanity check
mi pare di capire che mi manca qualche pacchetto di compilatori;
ho provato ad installare gcc-c++ mi dice che è già presente.
ho provato ad aggiornare kernel ed headers ma tutto è ok ...
ora nn so più cosa fare, spero in un Vs gradito aiuto.
grazie
cry4tux

 ora nn so più cosa fare, spero in un Vs gradito aiuto.
problemi di path?
echo $PATH cosa dice?
altrimenti cerca i file in questione manualmente (find ...) tanto per
essere sicuri che ci sono.
Ciao Jack

Jack ha scritto:

ciao e grazie ancora,
allora il path
#echo $PATH
mi da :
/usr/kerberos/sbin:/usr/kerberos/bin:/usr/lib/ccache:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
ho cercato poi i file con find come suggeritomi ma non li trova.
Se nn ci sono quali sono i pacchetti per installarli?
riproviamoci :-))
ciao


mmhh boh.
a me ad esempio il find mi da':
jack@giskard:~$ sudo find / -name stdio.h
/usr/src/linux-source-2.6.22/arch/powerpc/boot/stdio.h
/usr/include/bits/stdio.h
/usr/include/stdio.h
se non la trovi significa che non hai le librerie di gcc installate.
prova con:
gcc --version
a vedere cosa ti dice (anche se non serve a nulla)
Altrimenti proverei ad reinstallare gcc. Ti direi di farlo tramite apt-
get, ma hai redhat (da quanto vedo) e quindi non so che cosa puoi
usare.
Ciao Jack

 se non la trovi significa che non hai le librerie di gcc installate.
Beh, stdio.h mica arriva con gcc.
$ dpkg -S include/stdio.h
libc6-dev: /usr/include/stdio.h
$ apt-cache show gcc-4.2|grep ^Depends
Depends: binutils (>= 2.17cvs20070426), cpp-4.2 (= 4.2.3-1), gcc-4.2-base (=
4.2.3-1), libc6 (>= 2.7-1), libgcc1 (>= 1:4.2.3-1)
$ 
(su Debian)
Quindi, installando gcc installi libc6, non necessariamente le -dev.
Per Fedora:
ftp://fr2.rpmfind.net/linux/fedora/releases/8/Everything/i386/os/Packages/glibc-headers-2.7-2.i386.rpm
Ciao,
David
-- 
 . ''`.  Debian maintainer | 
http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- 
http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 ----|---- 
http://snipr.com/qa_page
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174

 /usr/kerberos/sbin:/usr/kerberos/bin:/usr/lib/ccache:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
PATH è il percorso ai binari per il tuo utente, non certo agli header per
gcc

 Ciao, David
Interessante, installi la libreria, ma non gli headers. Utile avere gcc
installato allora.
Ciao Jack -- Yoda of Borg am I! Assimilated shall you be! Futile
resistance is, hmm?

 installato allora.
Potrebbe esserlo. Non hai necessariamente bisogno di stdio.h:
$cat hello.c 
int main() {
	printf("Ciao!\n");
	return 0;
}
$ gcc -o hello hello.c 
hello.c: In function ‘main’:
hello.c:2: warning: incompatible implicit declaration of built-in function
‘printf’
$ ./hello 
Ciao!
$
Sarà uno schifo stilisticamente (e poi a me i warning, anche se sono warning e
non errori, non mi piacciono), ma funziona lo stesso :)


 non errori, non mi piacciono), ma funziona lo stesso :)
ok, pero'...mah...
cmq deve installare le dev.
mi pare strano cmq che non vengano installate di loro. boh.
cioe' capisco che se installi gimp non hai per forza bisogno di
gimp-dev, ma se installi gcc e' possibilissimo che tu abbia bisogno
oltre che della glibc anche della glibc-dev...


 oltre che della glibc anche della glibc-dev...
Ma infatti...
$ apt-cache show gcc-4.2 | grep ^Recommends
Recommends: libc6-dev (>= 2.5)
$
il campo "Depends" (parlo per Debian, eh) elenca solo i pacchetti _necessari_
_per_ _il_ _funzionamento_. I Recommends sono quelli che probabilmente ti
serviranno, appunto libc6-dev :)


 
e se vi dicessi che ora il problema è superato con il pacchetto 
consigliatomi da David Paleino, ma mi da un errore analogo con
checking for cairo... no
configure: error: This game cannot be built without cairo >= 1.2
e questo il file di config.log
grep error config.log
conftest.c:10:28: error: ac_nonexistent.h: No such file or directory
conftest.c:10:28: error: ac_nonexistent.h: No such file or directory
conftest.cpp:21:28: error: ac_nonexistent.h: No such file or directory
conftest.cpp:21:28: error: ac_nonexistent.h: No such file or directory
configure:20797: $PKG_CONFIG --exists --print-errors "cairo >= 1.2 "
configure:20815: $PKG_CONFIG --exists --print-errors "cairo >= 1.2 "
configure:20848: error: This game cannot be built without cairo >= 1.2
quale pacchetto mi consigliate?
grazie
cry4tux

 configure: error: This game cannot be built without cairo >= 1.2
Non ti salta in mente di cercare con Google? :)
ftp://fr2.rpmfind.net/linux/fedora/updates/8/i386/cairo-devel-1.4.14-1.fc8.i386.rpm
a) utilizza 
rpmfind.net
, 
rpmseek.com
 e simili
b) utilizza yum
c) quando c'è di mezzo pkgconfig,
cerca /usr/lib/pkgconfig/<pacchettomancante>.pc, spesso ci azzecchi (io ho
cercato /usr/lib/pkgconfig/cairo.pc)
d) Google, *Google*, *GOOGLE*!
Ciao,


 
grazie
ho provato su google ma probably nn cercavo nella maniera giusta ...
il fatto è che ancora nn sono pratico di questo affascinante mondo ...
scusate
a presto
cry4tux


quando devi compilare il più delle volte in fedora ti mancano i
pacchetti -devel. quindi se si lamenta della mancanza di cairo o altro tu
per prima cosa prova a fare:
yum install cairo-devel
è molto più facile che cercarli su google