Nieuws:

Welkom, Gast. Alsjeblieft inloggen of registreren.
Heb je de activerings-mail niet ontvangen?

Auteur Topic: C compiler error  (gelezen 2601 keer)

SlisheR

  • Gast
C compiler error
« Gepost op: 2007/07/08, 01:13:22 »
Altijd als ik iets wil installeren, vb:
cd 'dir'
./configure
make
en dan blablabla ... ga maar door
maar na de ./configure geeft m'n shell dit aan:
Citaat
loading cache ./config.cache
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... missing
checking for working autoconf... missing
checking for working automake... missing
checking for working autoheader... missing
checking for working makeinfo... missing
checking for gcc... gcc
checking whether the C compiler (gcc  ) works... no
configure: error: installation or configuration problem: C compiler cannot create executables.
ik weet uberhaupt niet wat hier fout aan is...
en ik krijg dit berichtje altijd bij elke ./configure command.

C compiler error
« Reactie #1 Gepost op: 2007/07/08, 01:30:10 »
https://wiki.ubuntu.com/NlSoftwareInstalleren Heb je dit helemaal vanonder al eens gelezen? :)
Heb je het pakket build-essentials al geïnstalleerd?

SlisheR

  • Gast
C compiler error
« Reactie #2 Gepost op: 2007/07/08, 11:26:41 »
Idd, bedankt.
Maar hier nog een probleem.
Nu moet ik wat anders doen, seems to be wat andere pakketen.
Zelfs die heb ik niet kunnen installeren.
Ik kreeg dit hele bericht na de ./configure:
loading cache ./config.cache
checking for a BSD compatible install... (cached) /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... (cached) yes
checking for working aclocal... missing
checking for working autoconf... missing
checking for working automake... missing
checking for working autoheader... missing
checking for working makeinfo... missing
checking for gcc... (cached) gcc
checking whether the C compiler (gcc  ) works... yes
checking whether the C compiler (gcc  ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for POSIXized ISC... no
checking for gcc... (cached) gcc
checking whether the C compiler (gcc -g -O2 ) works... yes
checking whether the C compiler (gcc -g -O2 ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for a BSD compatible install... /usr/bin/install -c
checking host system type... i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking for ranlib... (cached) ranlib
checking for ld used by GCC... (cached) /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... (cached) yes
checking for BSD-compatible nm... (cached) /usr/bin/nm -B
checking whether ln -s works... (cached) yes
checking for object suffix... o
checking for executable suffix... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.lo... yes
checking if gcc supports -fno-rtti -fno-exceptions ... no
checking if gcc static flag -static works... -static
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the linker (/usr/bin/ld) supports shared libraries... yes
checking command to parse /usr/bin/nm -B output... ok
checking how to hardcode library paths into programs... immediate
checking for /usr/bin/ld option to reload object files... -r
checking dynamic linker characteristics... Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking for objdir... .libs
creating libtool
loading cache ./config.cache
checking for gtk-config... no
checking for GTK - version >= 1.2.0... no
*** The gtk-config script installed by GTK could not be found
*** If GTK was installed in PREFIX, make sure PREFIX/bin is in
*** your path, or set the GTK_CONFIG environment variable to the
*** full path to gtk-config.
configure: error: Cannot find GTK: Is gtk-config in the path?
Zo te zien GTK dus, ik heb dit pakket gedownload maar was er niet in geslaagd te installeren.
En als ik GTK wil installeren met ./configure:
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for native Win32... no
checking for gcc... gcc
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 gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for egrep... 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 recognise dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
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... g++ -E
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for gfortran... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether  accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... cat: /etc/ld.so.conf.d/*.conf: No such file or directory
GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... cat: /etc/ld.so.conf.d/*.conf: No such file or directory
GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for _LARGE_FILES value needed for large files... no
checking for nm... /usr/bin/nm -B
checking whether to enable maintainer-specific portions of Makefiles... no
checking for some Win32 platform... no
checking whether build environment is sane... yes
checking for library containing strerror... none required
checking for gcc option to accept ANSI C... none needed
checking for a BSD-compatible install... /usr/bin/install -c
checking whether make sets $(MAKE)... (cached) yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for BASE_DEPENDENCIES... configure: error: Package requirements (glib-2.0 >= 2.8.5    atk >= 1.9.0    pango >= 1.9.0    cairo >= 0.9.2) were not met:

No package 'glib-2.0' found
No package 'atk' found
No package 'pango' found
No package 'cairo' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables BASE_DEPENDENCIES_CFLAGS
and BASE_DEPENDENCIES_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
Weet je misschien een manier waarmee ik het met apt-get kan installeren?
Bedankt, SlisheR.

C compiler error
« Reactie #3 Gepost op: 2007/07/08, 11:42:01 »
Kan je Gtk niet via de synaptic installeren?

Offline hello

  • Lid
C compiler error
« Reactie #4 Gepost op: 2007/07/08, 11:56:39 »
Kijk altijd eerst of dat packages niet in Synaptic staan!

NoiK

  • Gast
C compiler error
« Reactie #5 Gepost op: 2007/07/08, 13:44:12 »
waarom synaptic en niet gewoon apt-get en terminal?
(interesse;))

Offline Soul-Sing

  • Lid
C compiler error
« Reactie #6 Gepost op: 2007/07/08, 14:05:10 »
Citaat van: NoiK
waarom synaptic en niet gewoon apt-get en terminal?
(interesse;))
soms kun je de synaptic gebruiken om de zoekfunctie die het heeft. toch?

NoiK

  • Gast
C compiler error
« Reactie #7 Gepost op: 2007/07/08, 14:24:55 »
ah ja die klopt dies erg handig maar ken me herinnerren dat yum een optie heeft:
yum info foob*

zodat ie alle packages ken weergeven, die dat bevat..
maja heeft apt-get die niet?

Offline muksie

  • Lid
C compiler error
« Reactie #8 Gepost op: 2007/07/08, 14:35:17 »
Apt heeft dat ook, alleen dan in de vorm van apt-cache. Gewoon apt-cache search foob en je krijgt een lijst met pakketten waarbij foob in de naam of korte beschrijving voorkomt.

SlisheR

  • Gast
C compiler error
« Reactie #9 Gepost op: 2007/07/08, 14:49:44 »
Citaat van: Q.
Kan je Gtk niet via de synaptic installeren?
Heb alle pakketen gezocht via de synaptic maar niets gevonden.

Offline muksie

  • Lid
C compiler error
« Reactie #10 Gepost op: 2007/07/08, 19:09:52 »
Doe eens apt-cache search libgtk2.0
Je krijgt dan een lijst met packages. Daarvan ben je i.i.g. libgtk2.0-dev nodig, die zeer waarschijnlijk ook het programma gtk-config bevat, die je configure script niet kan vinden.

De anderen die je daarvan nodig bent, heb je zeer waarschijnlijk al geinstalleerd, of worden anders vanzelf meegeinstalleerd met het -dev pakket.