WinFuture-Forum.de: E17 Kompilieren - WinFuture-Forum.de

Zum Inhalt wechseln

Nachrichten zum Thema: Linux
Seite 1 von 1

E17 Kompilieren


#1 Mitglied ist offline   heoidasoulfly 

  • Gruppe: aktive Mitglieder
  • Beiträge: 80
  • Beigetreten: 15. April 04
  • Reputation: 0
  • Wohnort:Vorchdorf(Oberösterreich)

geschrieben 16. April 2005 - 12:50

Hi!

Versuche grad E17 zu kompileren und hänge bei /libs/ecore:

root@darkstar:~/e17/libs/ecore# sh autogen.sh
Running aclocal...
/usr/share/aclocal/xmms.m4:17: warning: underquoted definition of XMMS_TEST_VERSION
run info '(automake)Extending aclocal'
or see http://sources.redhat.com/automake/automak...tending-aclocal
/usr/share/aclocal/xmms.m4:62: warning: underquoted definition of AM_PATH_XMMS
/usr/share/aclocal/vorbis.m4:9: warning: underquoted definition of XIPH_PATH_VORBIS
/usr/share/aclocal/pilot-link.m4:1: warning: underquoted definition of AC_PILOT_LINK_HOOK
/usr/share/aclocal/ogg.m4:8: warning: underquoted definition of XIPH_PATH_OGG
/usr/share/aclocal/movtar.m4:14: warning: underquoted definition of MOVTAR_TEST_VERSION
/usr/share/aclocal/movtar.m4:59: warning: underquoted definition of AM_PATH_MOVTAR
/usr/share/aclocal/libmikmod.m4:11: warning: underquoted definition of AM_PATH_LIBMIKMOD
/usr/share/aclocal/libfame.m4:6: warning: underquoted definition of AM_PATH_LIBFAME
/usr/share/aclocal/libIDL.m4:6: warning: underquoted definition of AM_PATH_LIBIDL
/usr/share/aclocal/imlib.m4:9: warning: underquoted definition of AM_PATH_IMLIB
/usr/share/aclocal/imlib.m4:167: warning: underquoted definition of AM_PATH_GDK_IMLIB
/usr/share/aclocal/gtk.m4:7: warning: underquoted definition of AM_PATH_GTK
/usr/share/aclocal/gnet-2.0.m4:8: warning: underquoted definition of AM_PATH_GNET_2_0
/usr/share/aclocal/glib.m4:8: warning: underquoted definition of AM_PATH_GLIB
/usr/share/aclocal/gdk-pixbuf.m4:12: warning: underquoted definition of AM_PATH_GDK_PIXBUF
/usr/share/aclocal/audiofile.m4:12: warning: underquoted definition of AM_PATH_AUDIOFILE
/usr/share/aclocal/ao.m4:9: warning: underquoted definition of XIPH_PATH_AO
/usr/share/aclocal/aalib.m4:12: warning: underquoted definition of AM_PATH_AALIB/usr/share/aclocal/ORBit.m4:4: warning: underquoted definition of AM_PATH_ORBIT
Running autoheader...
Running autoconf...
Running libtoolize...
Running automake...
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
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 library containing strerror... none required
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking whether byte ordering is bigendian... no
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ANSI C... (cached) none needed
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ANSI C... (cached) none needed
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for an ANSI C-conforming const... 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 for int... yes
checking size of int... 4
checking for a sed that does not truncate output... /usr/bin/sed
checking for ld used by gcc... /usr/i486-slackware-linux/bin/ld
checking if the linker (/usr/i486-slackware-linux/bin/ld) is GNU ld... yes
checking for /usr/i486-slackware-linux/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 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 static flag works... yes
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 supports -c -o file.o... yes
checking whether the gcc linker (/usr/i486-slackware-linux/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... 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... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/i486-slackware-linux/bin/ld
checking if the linker (/usr/i486-slackware-linux/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/i486-slackware-linux/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++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/i486-slackware-linux/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
appending configuration tag "F77" to libtool
checking for __attribute__... yes
checking for gettimeofday... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking whether ecore_txt module is to be built... yes
checking for libiconv in -liconv... no
checking for iconv in -liconv... no
checking for libiconv in -lc... no
checking for iconv in -lc... yes
checking whether ecore_x module is to be built... yes
checking for X11/Xcursor/Xcursor.h... yes
checking for XcursorImageLoadCursor in -lXcursor... yes
checking for X11/extensions/Print.h... yes
checking for XpQueryScreens in -lXp... yes
checking for X11/extensions/Xinerama.h... yes
checking for XineramaQueryScreens in -lXinerama... yes
checking whether ecore_job module is to be built... yes
checking whether ecore_fb module is to be built... yes
checking linux/fb.h usability... yes
checking linux/fb.h presence... yes
checking for linux/fb.h... yes
checking for evas-config... /usr/local/bin/evas-config
checking whether ecore_evas module is to be built... yes
checking whether ecore_evas gl support is to be built... yes
checking for Evas_Engine_GL_X11.h... yes
checking whether ecore_evas fb support is to be built... yes
checking for Evas_Engine_FB.h... yes
checking whether ecore_evas buffer support is to be built... yes
checking for Evas_Engine_Buffer.h... yes
checking whether ecore_con module is to be built... yes
./configure: line 23862: syntax error near unexpected token `SSL,'
./configure: line 23862: ` PKG_CHECK_MODULES(SSL, openssl, use_openssl=yes, use_openssl=no)'
root@darkstar:~/e17/libs/ecore#

Hab schon gegooglt aber nix gefunden, wiess jemand Rat?

Slackware 10.1
0

Anzeige



#2 Mitglied ist offline   Rika 

  • Gruppe: aktive Mitglieder
  • Beiträge: 11.533
  • Beigetreten: 11. Juni 03
  • Reputation: 2
  • Geschlecht:Männlich

geschrieben 16. April 2005 - 13:07

Sieht nach einen kaputten configure-Script aus. Entferne einfach mal den betreffenden Check und gib grundsätzlich ein false zurück.
Konnichiwa. Manga wo shitte masu ka? Iie? Gomenne, sonoyouna koto ga tabitabi arimasu. Mangaka ojousan nihongo doujinshi desu wa 'Clamp X', 'Ayashi no Ceres', 'Card Captor Sakura', 'Tsubasa', 'Chobits', 'Sakura Taisen', 'Inuyasha' wo 'Ah! Megamisama'. Hai, mangaka gozaimashita desu ni yuujin yori.
Eingefügtes Bild
Ja, mata ne!

(For sending email please use OpenPGP encryption and signing. KeyID: 0xA0E28D18)
0

#3 Mitglied ist offline   ichbines 

  • Gruppe: aktive Mitglieder
  • Beiträge: 5.725
  • Beigetreten: 06. Oktober 02
  • Reputation: 0
  • Wohnort:Parndorf (Österreich)
  • Interessen:Computer, Linux

geschrieben 16. April 2005 - 15:12

hallo

Sowas kann schon mal passieren, dass die CVS-Version kaput ist. Die wird in den nächsten Tagen schon mal korrigiert werden.

Vor 3 Wochen wollte ich auch E17 installieren. Die CVS-Version hatte auch net geklappt. Dann habe ich fertig kompilierte RPM-Packete und Debian-Packete genommen. Das hat dann geklappt.
Es gibt dazu ja die Konverter rpm2targz und deb2gz.
Nacher muss man die Daten noch manuell in die Verzeichnisse kopieren.

RPM-Packete
oder versuche diese.
0

Thema verteilen:


Seite 1 von 1

1 Besucher lesen dieses Thema
Mitglieder: 0, Gäste: 1, unsichtbare Mitglieder: 0