aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Pages: [1] 2

Author Topic: Problem beim compilieren  (Read 9418 times)

BastiG

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 15
Problem beim compilieren
« on: January 31, 2004, 11:50:37 PM »

Hi,

wenn ich ./configure --disable-debug --enable-optimise && make
in der Konsole einge, bekomm ich folgende Fehlermeldung:

ListenSocket.cpp:506:34: Warnung: #warning TODO: CHECK SPAMMERS!
make[1]: *** [amule-ListenSocket.o] Fehler 1
make[1]: Leaving directory `/home/BastiG/aMule-1.2.4/src'
make: *** [install-recursive] Fehler 1

Davor noch viele andere Errors, aber die sind durch diesen verursacht glaube ich.

mfg

BastiG
« Last Edit: January 31, 2004, 11:51:18 PM by BastiG »
Logged

deltaHF

  • Evil Admin
  • Former Developer
  • Hero Member
  • *****
  • Karma: 6
  • Offline Offline
  • Posts: 3920
  • .. Legends may sleep, but they never die ..
    • http://www.amule.org
Re: Problem beim compilieren
« Reply #1 on: January 31, 2004, 11:51:41 PM »

um dir zu helfen bräuchte ich doch mehr info ..
poste die ganzen errors bitte

ps . du könntest dir auch das get-info.sh script laden, ausführen und mitposten .. und n teil vom configure output .. und zwar wos nach wxGTK, wxBase, gtk und curl sucht..

gruss

BastiG

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 15
Re: Problem beim compilieren
« Reply #2 on: February 01, 2004, 12:31:21 AM »

In file included from amuleDlg.h:41,
                 from amule.h:30,
                 from ListenSocket.cpp:22:
SysTray.h:21:21: gtk/gtk.h: Datei oder Verzeichnis nicht gefunden
SysTray.h:22:21: gdk/gdk.h: Datei oder Verzeichnis nicht gefunden
SysTray.h:23:22: gdk/gdkx.h: Datei oder Verzeichnis nicht gefunden
SysTray.h:24:18: glib.h: Datei oder Verzeichnis nicht gefunden
In file included from eggtrayicon.h:24,
                 from SysTray.h:46,
                 from amuleDlg.h:41,
                 from amule.h:30,
                 from ListenSocket.cpp:22:
gtkplugxembed.h:30:21: gdk/gdk.h: Datei oder Verzeichnis nicht gefunden
gtkplugxembed.h:31:27: gtk/gtksocket.h: Datei oder Verzeichnis nicht gefunden
gtkplugxembed.h:32:27: gtk/gtkwindow.h: Datei oder Verzeichnis nicht gefunden
In file included from eggtrayicon.h:24,
                 from SysTray.h:46,
                 from amuleDlg.h:41,
                 from amule.h:30,
                 from ListenSocket.cpp:22:
gtkplugxembed.h:51: error: Syntaxfehler before `;' token
gtkplugxembed.h:55: error: 'GtkWindow' is used as a type, but is not defined as
   a type.
gtkplugxembed.h:62: error: Syntaxfehler before `*' token
gtkplugxembed.h:69: error: 'GtkWindowClass' is used as a type, but is not
   defined as a type.
gtkplugxembed.h:81: error: parse error before `)' token
gtkplugxembed.h:82: error: type specifier omitted for parameter `
   GtkPlugXEmbedNativeWindow'
gtkplugxembed.h:82: error: parse error before `)' token
gtkplugxembed.h:84: error: `GtkPlugXEmbedNativeWindow' was not declared in this
   scope
gtkplugxembed.h:84: error: parse error before `)' token
gtkplugxembed.h:85: error: parse error before `*' token
gtkplugxembed.h:88: error: type specifier omitted for parameter `GtkSocket'
gtkplugxembed.h:88: error: parse error before `*' token
gtkplugxembed.h:90: error: type specifier omitted for parameter `GtkSocket'
gtkplugxembed.h:90: error: parse error before `*' token
In file included from SysTray.h:46,
                 from amuleDlg.h:41,
                 from amule.h:30,
                 from ListenSocket.cpp:22:
eggtrayicon.h:25:22: gdk/gdkx.h: Datei oder Verzeichnis nicht gefunden
In file included from SysTray.h:46,
                 from amuleDlg.h:41,
                 from amule.h:30,
                 from ListenSocket.cpp:22:
eggtrayicon.h:47: error: 'Atom' is used as a type, but is not defined as a
   type.
eggtrayicon.h:48: error: 'Atom' is used as a type, but is not defined as a
   type.
eggtrayicon.h:49: error: 'Atom' is used as a type, but is not defined as a
   type.
eggtrayicon.h:50: error: 'Window' is used as a type, but is not defined as
   type.
eggtrayicon.h:58: error: parse error before `)' token
eggtrayicon.h:61: error: `Screen' was not declared in this scope
eggtrayicon.h:61: error: `xscreen' was not declared in this scope
eggtrayicon.h:61: error: parse error before `char'
ListenSocket.cpp:506:34: Warnung: #warning TODO: CHECK SPAMMERS!
make[1]: *** [amule-ListenSocket.o] Fehler 1
make[1]: Leaving directory `/home/BastiG/aMule-1.2.4/src'
make: *** [install-recursive] Fehler 1

Eigentlich habe ich gtk installiert :(. Und dann habe ich noch ne Frage. Wenn ich ohne
--disable-amulecmd kompiliere kommen noch mehr Fehler. Wozu brauch ich amulecmd und woran liegt das?

mfg Basti
Logged

deltaHF

  • Evil Admin
  • Former Developer
  • Hero Member
  • *****
  • Karma: 6
  • Offline Offline
  • Posts: 3920
  • .. Legends may sleep, but they never die ..
    • http://www.amule.org
Re: Problem beim compilieren
« Reply #3 on: February 01, 2004, 12:39:25 AM »

Quote
Originally posted by deltaHF

ps .......... und n teil vom configure output .. und zwar wos nach wxGTK, wxBase, gtk und curl sucht..


amulecmd ist quasi eine fernbedienung um amule vom anderen rechner aus bedienen zu können..

poste bitte so viel wie möglich über dein system (get-info.sh wär wohl am besten) und das vom configure ..

fz

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 27
Re: Problem beim compilieren
« Reply #4 on: February 01, 2004, 12:41:52 AM »

hi basti,

in den meisten linux-distributionen brauchst du zu einem packet wie gtk noch das sog. "-devel"-packet, um selber programme, die auf dieses packet zugreifen, kompilieren zu können (devel=development=selber entwickeln).
installier einfach das passende gtk-devel packet, dann sollte das klappen.

gruss, fz

edit:
delta, du bist echt zu schnell  :D
« Last Edit: February 01, 2004, 12:42:23 AM by fz »
Logged

BastiG

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 15
Re: Problem beim compilieren
« Reply #5 on: February 01, 2004, 12:56:59 AM »

devel habe ich installiert!
Logged

deltaHF

  • Evil Admin
  • Former Developer
  • Hero Member
  • *****
  • Karma: 6
  • Offline Offline
  • Posts: 3920
  • .. Legends may sleep, but they never die ..
    • http://www.amule.org
Re: Problem beim compilieren
« Reply #6 on: February 01, 2004, 12:57:41 AM »

ein forum ist nur so gut wie sein admin  :] :D

deltaHF

  • Evil Admin
  • Former Developer
  • Hero Member
  • *****
  • Karma: 6
  • Offline Offline
  • Posts: 3920
  • .. Legends may sleep, but they never die ..
    • http://www.amule.org
Re: Problem beim compilieren
« Reply #7 on: February 01, 2004, 12:58:27 AM »

Quote
Originally posted by BastiG
devel habe ich installiert!

dann lese dir bitte durch was ich noch für infos von dir brauche

BastiG

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 15
Re: Problem beim compilieren
« Reply #8 on: February 01, 2004, 02:11:46 AM »

linux:/home/BastiG/aMule-1.2.4 # ./configure --disable-debug --enable-optimise && make
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for g++... g++
checking for C++ compiler default output... 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 gcc... gcc
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 dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for ranlib... ranlib
checking for strerror in -lcposix... no
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
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 off_t... yes
checking for size_t... yes
checking for working alloca.h... yes
checking for alloca... yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for getpagesize... yes
checking for working mmap... yes
checking whether we are using the GNU C Library 2.1 or newer... yes
checking whether integer division by zero raises SIGFPE... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unsigned long long... yes
checking for inttypes.h... yes
checking whether the inttypes.h PRIxNN macros are broken... no
checking for ld used by GCC... /usr/i586-suse-linux/bin/ld
checking if the linker (/usr/i586-suse-linux/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking argz.h usability... yes
checking argz.h presence... yes
checking for argz.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking nl_types.h usability... yes
checking nl_types.h presence... yes
checking for nl_types.h... yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking stddef.h usability... yes
checking stddef.h presence... yes
checking for stddef.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking for feof_unlocked... yes
checking for fgets_unlocked... yes
checking for getc_unlocked... yes
checking for getcwd... yes
checking for getegid... yes
checking for geteuid... yes
checking for getgid... yes
checking for getuid... yes
checking for mempcpy... yes
checking for munmap... yes
checking for putenv... yes
checking for setenv... yes
checking for setlocale... yes
checking for stpcpy... yes
checking for strcasecmp... yes
checking for strdup... yes
checking for strtoul... yes
checking for tsearch... yes
checking for __argz_count... yes
checking for __argz_stringify... yes
checking for __argz_next... yes
checking for iconv... yes
checking for iconv declaration...
         extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft);
checking for nl_langinfo and CODESET... yes
checking for LC_MESSAGES... yes
checking for bison... bison
checking version of bison... 1.75, ok
checking whether NLS is requested... yes
checking whether included gettext is requested... no
checking for GNU gettext in libc... yes
checking for wx-config... /usr/bin/wx-config
checking for wxWindows version >= 2.4.0... yes (version 2.4.2)
checking for wxbase-2.4-config... /usr/bin/wxbase-2.4-config
checking for wxWindows base version >= 2.4.0... yes (version 2.4.2)
checking for curl >= 7.9.7... yes (version 7.10.5)
checking if wxWindows was linked with GTK2... no
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: line 1: no: command not found
checking if wxWindows version >=2.5.0 ... no
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
checking whether SysTray should be compiled... yes
checking whether SysTray should be compiled in safe mode... no
checking whether pure GTK code should be compiled... yes
checking whether progress bar drawing should be disabled... no
checking whether progress amulecmd should be build... yes
checking for ANSI C header files... (cached) yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking for locale.h... (cached) yes
checking netdb.h usability... yes
checking netdb.h presence... yes
checking for netdb.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking for stdlib.h... (cached) yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking sys/timeb.h usability... yes
checking sys/timeb.h presence... yes
checking for sys/timeb.h... yes
checking for unistd.h... (cached) yes
checking sys/resource.h usability... yes
checking sys/resource.h presence... yes
checking for sys/resource.h... yes
checking for an ANSI C-conforming const... (cached) yes
checking for inline... (cached) inline
checking for off_t... (cached) yes
checking for size_t... (cached) yes
checking whether time.h and sys/time.h may both be included... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for working memcmp... yes
checking for sys/time.h... (cached) yes
checking for unistd.h... (cached) yes
checking for alarm... yes
checking for working mktime... yes
checking return type of signal handlers... void
checking whether lstat dereferences a symlink specified with a trailing slash... yes
checking whether stat accepts an empty string... no
checking for strftime... yes
checking for floor... no
checking for ftruncate... yes
checking for gettimeofday... yes
checking for inet_ntoa... yes
checking for memchr... yes
checking for memmove... yes
checking for memset... yes
checking for mkdir... yes
checking for putenv... (cached) yes
checking for select... yes
checking for setlocale... (cached) yes
checking for sqrt... no
checking for strcasecmp... (cached) yes
checking for strchr... yes
checking for strdup... (cached) yes
checking for strrchr... yes
checking for strstr... yes
checking for strtoul... (cached) yes
checking for getrlimit... yes
checking for setrlimit... yes
configure: creating ./config.status
config.status: creating src/timestamp-sys.h
config.status: sys.h is unchanged
config.status: creating src/Makefile
config.status: creating intl/Makefile
config.status: creating po/Makefile.in
config.status: creating m4/Makefile
config.status: creating Makefile
config.status: creating Compilation.flags
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing default-1 commands
config.status: creating po/POTFILES
config.status: creating po/Makefile


  Configure script has finished system check.

  Configured aMule 1.2.4 for `i686-pc-linux-gnu'.

  Should aMule be compiled in debug mode?                  no
  Should aMule be compiled with release grp code?          no
  Should aMule be compiled without debug reporting?        no
  Should aMule be compiled with profiling?                 no
  Should aMule be compiled with optimizations?             yes
  Should aMule be compiled with systray?                   yes
  Should aMule be compiled with safe systray?              no
  Should aMule be compiled with pure GTK code?             yes
  Should aMule be compiled without bar drawing?            no
  Should aMule be linked against patched gsocket?          yes
  Should amulecmd be built?                                yes
  Should amulecmd (TextClient) be linked against wxbase?   yes

  Which libraries should aMule use?
                                       wxWindows          2.4.2
                                       GTK                Not detected

make  all-recursive
Logged

BastiG

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 15
Re: Problem beim compilieren
« Reply #9 on: February 01, 2004, 01:24:43 PM »

Und hier diese get-info.sh

BastiG@linux:~> sh get-info.sh
I.   Development Environment

     A. Compiler Info
        Reading specs from /usr/lib/gcc-lib/i586-suse-linux/3.3.1/specs Konfiguriert mit: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --enable-languages=c,c++,f77,objc,java,ada --disable-checking --enable-libgcj --with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit i586-suse-linux Thread model: posix gcc-Version 3.3.1 (SuSE Linux)

     B. wxWindows Info
        Version: 2.4.2
        -pthread -lwx_gtk-2.4

     C. GTK Info
        GTK 1: 1.2.10
get-info.sh: line 1: pkg-config: command not found
        GTK 2:

II.  System Environment

     A. CPU Info
        Type:  GenuineIntel
        Model: Intel(R) Pentium(R) 4 CPU 2.53GHz
        Speed: 2524.973
        BMips: 4980.73
        Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm

     B. Memory Info
        Total:   514408 kB
        Unused:  388428 kB

     C. Kernel Info
        Version: 2.4.21-166-default

     D. Library Info
get-info.sh: line 33: ldconfig: command not found
        wxWindows library:
Logged

fz

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 27
Re: Problem beim compilieren
« Reply #10 on: February 01, 2004, 01:57:03 PM »

hi basti,

ok, die datei "gtk-config" wurde nicht gefunden.
normalerweise ist die in /usr/bin/. mach mal ein
"ls /usr/bin/gtk-config". wenn die datei nicht gefunden wurde, gib mal
"find / -name gtk-config" ein (am besten als root) und such sie damit. irgendwo muss die sein, wenn gtk installiert ist.

wenn du den pfad zur gtk-config gefunden hast (z.b. /usr/bin/), dann bleibt noch die frage, warum die vom configure nicht gefunden wurde. vermutlich ist ihr ordner nicht im suchpfad. jetzt gibts zwei möglichkeiten:
1. den ordner in den suchpfad aufnehmen durch
    "export PATH=$PATH:/pfad/zur-gtk-config/"
2. configure mit
    "GTK_CONFIG=/pfad/zur-gtk-config/ configure" aufrufen.

alles klar?

fz

edit: typo
« Last Edit: February 01, 2004, 01:58:01 PM by fz »
Logged

BastiG

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 15
Re: Problem beim compilieren
« Reply #11 on: February 01, 2004, 02:16:58 PM »

Hey,
Ich habe
linux:/home/BastiG/aMule-1.2.4 # export PATH=$PATH:/opt/gnome/bin/gtk-config
linux:/home/BastiG/aMule-1.2.4 #  ./configure --disable-debug --enable-optimise && make

in die Konsole geschrieben. So müsste es doch eigentlich klappen oder muss man es anders schreiben? Jetzt bekomm ich aber immer noch Fehler:

In file included from amuleDlg.h:41,
                 from amule.h:30,
                 from ListenSocket.cpp:22:
SysTray.h:21:21: gtk/gtk.h: Datei oder Verzeichnis nicht gefunden
SysTray.h:22:21: gdk/gdk.h: Datei oder Verzeichnis nicht gefunden
SysTray.h:23:22: gdk/gdkx.h: Datei oder Verzeichnis nicht gefunden
SysTray.h:24:18: glib.h: Datei oder Verzeichnis nicht gefunden
In file included from eggtrayicon.h:24,
                 from SysTray.h:46,
                 from amuleDlg.h:41,
                 from amule.h:30,
                 from ListenSocket.cpp:22:
gtkplugxembed.h:30:21: gdk/gdk.h: Datei oder Verzeichnis nicht gefunden
gtkplugxembed.h:31:27: gtk/gtksocket.h: Datei oder Verzeichnis nicht gefunden
gtkplugxembed.h:32:27: gtk/gtkwindow.h: Datei oder Verzeichnis nicht gefunden
In file included from eggtrayicon.h:24,
                 from SysTray.h:46,
                 from amuleDlg.h:41,
                 from amule.h:30,
                 from ListenSocket.cpp:22:
gtkplugxembed.h:51: error: Syntaxfehler before `;' token
gtkplugxembed.h:55: error: 'GtkWindow' is used as a type, but is not defined as
   a type.
gtkplugxembed.h:62: error: Syntaxfehler before `*' token
gtkplugxembed.h:69: error: 'GtkWindowClass' is used as a type, but is not
   defined as a type.
gtkplugxembed.h:81: error: parse error before `)' token
gtkplugxembed.h:82: error: type specifier omitted for parameter `
   GtkPlugXEmbedNativeWindow'
gtkplugxembed.h:82: error: parse error before `)' token
gtkplugxembed.h:84: error: `GtkPlugXEmbedNativeWindow' was not declared in this
   scope
gtkplugxembed.h:84: error: parse error before `)' token
gtkplugxembed.h:85: error: parse error before `*' token
gtkplugxembed.h:88: error: type specifier omitted for parameter `GtkSocket'
gtkplugxembed.h:88: error: parse error before `*' token
gtkplugxembed.h:90: error: type specifier omitted for parameter `GtkSocket'
gtkplugxembed.h:90: error: parse error before `*' token
In file included from SysTray.h:46,
                 from amuleDlg.h:41,
                 from amule.h:30,
                 from ListenSocket.cpp:22:
eggtrayicon.h:25:22: gdk/gdkx.h: Datei oder Verzeichnis nicht gefunden
In file included from SysTray.h:46,
                 from amuleDlg.h:41,
                 from amule.h:30,
                 from ListenSocket.cpp:22:
eggtrayicon.h:47: error: 'Atom' is used as a type, but is not defined as a
   type.
eggtrayicon.h:48: error: 'Atom' is used as a type, but is not defined as a
   type.
eggtrayicon.h:49: error: 'Atom' is used as a type, but is not defined as a
   type.
eggtrayicon.h:50: error: 'Window' is used as a type, but is not defined as a
   type.
eggtrayicon.h:58: error: parse error before `)' token
eggtrayicon.h:61: error: `Screen' was not declared in this scope
eggtrayicon.h:61: error: `xscreen' was not declared in this scope
eggtrayicon.h:61: error: parse error before `char'
ListenSocket.cpp:506:34: Warnung: #warning TODO: CHECK SPAMMERS!
make[2]: *** [amule-ListenSocket.o] Fehler 1
make[2]: Leaving directory `/home/BastiG/aMule-1.2.4/src'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/home/BastiG/aMule-1.2.4'
make: *** [all] Fehler 2
In file included from amuleDlg.h:41,
                 from amule.h:30,
                 from ListenSocket.cpp:22:
SysTray.h:21:21: gtk/gtk.h: Datei oder Verzeichnis nicht gefunden
SysTray.h:22:21: gdk/gdk.h: Datei oder Verzeichnis nicht gefunden
SysTray.h:23:22: gdk/gdkx.h: Datei oder Verzeichnis nicht gefunden
SysTray.h:24:18: glib.h: Datei oder Verzeichnis nicht gefunden
In file included from eggtrayicon.h:24,
                 from SysTray.h:46,
                 from amuleDlg.h:41,
                 from amule.h:30,
                 from ListenSocket.cpp:22:
gtkplugxembed.h:30:21: gdk/gdk.h: Datei oder Verzeichnis nicht gefunden
gtkplugxembed.h:31:27: gtk/gtksocket.h: Datei oder Verzeichnis nicht gefunden
gtkplugxembed.h:32:27: gtk/gtkwindow.h: Datei oder Verzeichnis nicht gefunden
In file included from eggtrayicon.h:24,
                 from SysTray.h:46,
                 from amuleDlg.h:41,
                 from amule.h:30,
                 from ListenSocket.cpp:22:
gtkplugxembed.h:51: error: Syntaxfehler before `;' token
gtkplugxembed.h:55: error: 'GtkWindow' is used as a type, but is not defined as
   a type.
gtkplugxembed.h:62: error: Syntaxfehler before `*' token
gtkplugxembed.h:69: error: 'GtkWindowClass' is used as a type, but is not
   defined as a type.
gtkplugxembed.h:81: error: parse error before `)' token
gtkplugxembed.h:82: error: type specifier omitted for parameter `
   GtkPlugXEmbedNativeWindow'
gtkplugxembed.h:82: error: parse error before `)' token
gtkplugxembed.h:84: error: `GtkPlugXEmbedNativeWindow' was not declared in this
   scope
gtkplugxembed.h:84: error: parse error before `)' token
gtkplugxembed.h:85: error: parse error before `*' token
gtkplugxembed.h:88: error: type specifier omitted for parameter `GtkSocket'
gtkplugxembed.h:88: error: parse error before `*' token
gtkplugxembed.h:90: error: type specifier omitted for parameter `GtkSocket'
gtkplugxembed.h:90: error: parse error before `*' token
In file included from SysTray.h:46,
                 from amuleDlg.h:41,
                 from amule.h:30,
                 from ListenSocket.cpp:22:
eggtrayicon.h:25:22: gdk/gdkx.h: Datei oder Verzeichnis nicht gefunden
In file included from SysTray.h:46,
                 from amuleDlg.h:41,
                 from amule.h:30,
                 from ListenSocket.cpp:22:
eggtrayicon.h:47: error: 'Atom' is used as a type, but is not defined as a
   type.
eggtrayicon.h:48: error: 'Atom' is used as a type, but is not defined as a
   type.
eggtrayicon.h:49: error: 'Atom' is used as a type, but is not defined as a
   type.
eggtrayicon.h:50: error: 'Window' is used as a type, but is not defined as a
   type.
eggtrayicon.h:58: error: parse error before `)' token
eggtrayicon.h:61: error: `Screen' was not declared in this scope
eggtrayicon.h:61: error: `xscreen' was not declared in this scope
eggtrayicon.h:61: error: parse error before `char'
ListenSocket.cpp:506:34: Warnung: #warning TODO: CHECK SPAMMERS!
make[2]: *** [amule-ListenSocket.o] Fehler 1
make[2]: Leaving directory `/home/BastiG/aMule-1.2.4/src'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/home/BastiG/aMule-1.2.4'
make: *** [all] Fehler 2
Logged

fz

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 27
Re: Problem beim compilieren
« Reply #12 on: February 01, 2004, 02:27:41 PM »

hi,

was ist die ausgabe von "gtk-config --cflags" bei dir?
da müsste dann sowas wie "-I/usr/include/gtk-1.2" stehen. in dem ordner /usr/include/gtk-1.2 sind die header-dateien für gtk. gibt es den ordner?
Logged

BastiG

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 15
Re: Problem beim compilieren
« Reply #13 on: February 01, 2004, 02:37:44 PM »

ich bekomme immer die folgende Ausgabe:
linux:/opt/gnome/bin # gtk-config --cflags
bash: gtk-config: command not found

Wo muss ich den Befehl eingeben bzw. welchen Ordner (oder egal)?

Den Ordner, den du angegeben hast, gibt es nicht.
Logged

fz

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 27
Re: Problem beim compilieren
« Reply #14 on: February 01, 2004, 02:42:41 PM »

hm...bist du als root eingeloggt?
dann musst du
linux:/opt/gnome/bin # ./gtk-config --cflags
eingeben.
aber nachdem du den "export PATH=$PATH:/opt/gnome/bin/" gemacht hast, müsstes du den befehl in jedem ordner ausführen können (weil gtk-config dann ja im suchpfad für ausführbare programme ist).

edit:

die korrekte export-anweisung lautet
"export PATH=$PATH:/opt/gnome/bin/", also OHNE den dateinamen "gtk-config". der suchpfad bezieht sich immer auf ordner, nicht auf dateien!
« Last Edit: February 01, 2004, 02:44:22 PM by fz »
Logged
Pages: [1] 2