View previous topic :: View next topic |
Author |
Message |
Daimos Tux's lil' helper
Joined: 08 May 2003 Posts: 78
|
Posted: Mon May 19, 2003 10:31 pm Post subject: Problem beim Bootstrap mit gcc 3.3 |
|
|
hi,
ich hab mal versucht, mit gcc 3.3 nen bootstrap anzuwerfen und bekomme den folgenden Fehler:
Code: |
/var/tmp/portage/gcc-3.3/work/build/gcc/xgcc -shared-libgcc -B/var/tmp/portage/gcc-3.3/work/build/gcc/ -nostdinc++ -L/var/tmp/portage/gcc-3.3/work/build/i686-pc-linux-gnu/libstdc++-v3/src -L/var/tmp/portage/gcc-3.3/work/build/i686-pc-linux-gnu/libstdc++-v3/src/.libs -B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/lib/ -isystem /usr/i686-pc-linux-gnu/include -DHAVE_CONFIG_H -I. -I/var/tmp/portage/gcc-3.3/work/gcc-3.3/libjava -I./include -I./gcj -I/var/tmp/portage/gcc-3.3/work/gcc-3.3/libjava -Iinclude -I/var/tmp/portage/gcc-3.3/work/gcc-3.3/libjava/include -I/var/tmp/portage/gcc-3.3/work/gcc-3.3/libjava/../boehm-gc/include -DGC_LINUX_THREADS=1 -D_REENTRANT=1 -DTHREAD_LOCAL_ALLOC=1 -DSILENT=1 -DNO_SIGNALS=1 -DNO_EXECUTE_PERMISSION=1 -DALL_INTERIOR_POINTERS=1 -DJAVA_FINALIZATION=1 -DGC_GCJ_SUPPORT=1 -DATOMIC_UNCOLLECTABLE=1 -I/var/tmp/portage/gcc-3.3/work/gcc-3.3/libjava/libltdl -I/var/tmp/portage/gcc-3.3/work/gcc-3.3/libjava/libltdl -I../libstdc++-v3/include -I../libstdc++-v3/include/i686-pc-linux-gnu -I/var/tmp/portage/gcc-3.3/work/gcc-3.3/libjava/../libstdc++-v3/libsupc++ -I/var/tmp/portage/gcc-3.3/work/gcc-3.3/libjava/.././libjava/../gcc -I/var/tmp/portage/gcc-3.3/work/gcc-3.3/libjava/../libffi/include -I../libffi/include -fno-rtti -fnon-call-exceptions -fdollars-in-identifiers -Wswitch-enum -D__NO_MATH_INLINES -ffloat-store -I/usr/X11R6/include -W -Wall -D_GNU_SOURCE -DPREFIX=\"/usr\" -march=athlon-tbird -pipe -D_GNU_SOURCE -MD -MT gnu/gcj/xlib/natClip.lo -MF gnu/gcj/xlib/natClip.pp -c /var/tmp/portage/gcc-3.3/work/gcc-3.3/libjava/gnu/gcj/xlib/natClip.cc -fPIC -DPIC -o gnu/gcj/xlib/.libs/natClip.o
/var/tmp/portage/gcc-3.3/work/gcc-3.3/libjava/gnu/gcj/xlib/natClip.cc:17:22: X11/Xlib.h: No such file or directory
/var/tmp/portage/gcc-3.3/work/gcc-3.3/libjava/gnu/gcj/xlib/natClip.cc:26: error: `
XRectangle' was not declared in this scope
/var/tmp/portage/gcc-3.3/work/gcc-3.3/libjava/gnu/gcj/xlib/natClip.cc:26: error: template
argument 1 is invalid
/var/tmp/portage/gcc-3.3/work/gcc-3.3/libjava/gnu/gcj/xlib/natClip.cc:26: error: template
argument 2 is invalid
/var/tmp/portage/gcc-3.3/work/gcc-3.3/libjava/gnu/gcj/xlib/natClip.cc:26: error: ISO
C++ forbids declaration of `XRectVector' with no type
/var/tmp/portage/gcc-3.3/work/gcc-3.3/libjava/gnu/gcj/xlib/natClip.cc: In
member function `void gnu::gcj::xlib::Clip::init(AWTRectArray*)':
/var/tmp/portage/gcc-3.3/work/gcc-3.3/libjava/gnu/gcj/xlib/natClip.cc:38: error: `
XRectangle' undeclared (first use this function)
/var/tmp/portage/gcc-3.3/work/gcc-3.3/libjava/gnu/gcj/xlib/natClip.cc:38: error: (Each
undeclared identifier is reported only once for each function it appears
in.)
/var/tmp/portage/gcc-3.3/work/gcc-3.3/libjava/gnu/gcj/xlib/natClip.cc:38: error: `
xrect' undeclared (first use this function)
/var/tmp/portage/gcc-3.3/work/gcc-3.3/libjava/gnu/gcj/xlib/natClip.cc:38: error: invalid
types `int[int]' for array subscript
make[3]: *** [gnu/gcj/xlib/natClip.lo] Error 1
make[3]: Leaving directory `/var/tmp/portage/gcc-3.3/work/build/i686-pc-linux-gnu/libjava'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/gcc-3.3/work/build/i686-pc-linux-gnu/libjava'
make[1]: *** [all-target-libjava] Error 2
make[1]: Leaving directory `/var/tmp/portage/gcc-3.3/work/build'
make: *** [bootstrap-lean] Error 2
!!! ERROR: sys-devel/gcc-3.3 failed.
!!! Function src_compile, Line 332, Exitcode 2
!!! (no error message)
|
Jemand ne Idee? |
|
Back to top |
|
|
Daimos Tux's lil' helper
Joined: 08 May 2003 Posts: 78
|
Posted: Tue May 20, 2003 11:11 am Post subject: |
|
|
so, ich bins nochmal,
irgendwie hat das ebuild X als Abhängigkeit drin, was ich beim bootstrap wohl kaum erfüllen kann *g*.
Daher hab ich in die make.conf infach mal ein USE="-X" dazugepackt, und schon lief es sauber durch. Ob das jetzt allerdings des Rätsels Lösung ist, weiß ich auch nicht.
Ihm scheinen ja laut Fehlermeldung X11 Header zu fehlen, daher dachte ich, daß das evtl helfen kann (tat es ja auch ). Bloß warum kommt das als Abhängkeit ins ebuild, fast jeder wird das X in USE drin haben? |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|