Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
how to emerge qemu ? [solved ???]
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Gentoo on PPC
View previous topic :: View next topic  
Author Message
ddc
Guru
Guru


Joined: 29 Aug 2006
Posts: 527

PostPosted: Mon Sep 24, 2007 3:05 pm    Post subject: how to emerge qemu ? [solved ???] Reply with quote

qemu requires gcc 3.x while the last gentoo is equipped with gcc 4.x
how to fix it ?


Last edited by ddc on Fri Oct 26, 2007 9:31 am; edited 2 times in total
Back to top
View user's profile Send private message
Deusexodus
Tux's lil' helper
Tux's lil' helper


Joined: 30 May 2005
Posts: 124
Location: Paris

PostPosted: Mon Sep 24, 2007 5:06 pm    Post subject: Reply with quote

Simply in merging gcc3, like others ebuild you have to compil gcc3.

Sorry if you think that I'm saying stupid things ---> []
_________________
Lenovo x220 | Lenovo S12 | Hp mini 2133 | Via VB8001
Back to top
View user's profile Send private message
ddc
Guru
Guru


Joined: 29 Aug 2006
Posts: 527

PostPosted: Mon Sep 24, 2007 8:26 pm    Post subject: Reply with quote

yes, but no gcc-3.x has success in recompiling
this is my problem

for example

in /usr/portage/sys-devel/gcc
we have {3.1.1-r2, 3.2.3-r4, 3.3.5-r1, 3.3.6-r1, 3.4.1-r3, 3.4.5-r1, 3.4.6-r1, 3.4.6, 3.2.2, 3.3.2-r7, 3.3.5, 3.3.6, 3.4.1-r3, 3.4.4-r1, 3.4.5, 3.4.6-r2}

"grep KEYWORD * | grep ppc" shows i have to edit gcc-3.3.6.ebuild to add "~ppc" to the KEYWORDS
then ebuild gcc-3.3.6.ebuild digest
and emerge =sys-devel/gcc-3.3.6

and it stars compiling, but it fails with an error in "bootstrap" (i don't know what does this error mean)

how tow fix it ?
also, i can't understand why qemu requires gcc.4.x ....
and if/when it could be fixed to be compiled with gcc.4.x


Last edited by ddc on Mon Sep 24, 2007 11:52 pm; edited 3 times in total
Back to top
View user's profile Send private message
corsair
Retired Dev
Retired Dev


Joined: 06 Oct 2003
Posts: 451
Location: Aachen, Germany

PostPosted: Mon Sep 24, 2007 8:39 pm    Post subject: Reply with quote

are you using powerpc64? there is no way compiling gcc-3.3.x there.
Back to top
View user's profile Send private message
ddc
Guru
Guru


Joined: 29 Aug 2006
Posts: 527

PostPosted: Mon Sep 24, 2007 8:43 pm    Post subject: Reply with quote

i have a ppc7450, also called G4: it should be called "ppc" in the KEYWORDS
Back to top
View user's profile Send private message
JoseJX
Retired Dev
Retired Dev


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Mon Sep 24, 2007 10:34 pm    Post subject: Reply with quote

Why are you using 3.3? You'll have more success with 3.4.x, try 3.4.6-r2.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
ddc
Guru
Guru


Joined: 29 Aug 2006
Posts: 527

PostPosted: Tue Sep 25, 2007 8:14 am    Post subject: Reply with quote

Code:

gcc -v


Quote:

Using built-in specs.
Target: powerpc-unknown-linux-gnu
Configured with: /var/tmp/portage/sys-devel/gcc-4.1.2/work/gcc-4.1.2/configure --prefix=/usr --bindir=/usr/powerpc-unknown-linux-gnu/gcc-bin/4.1.2 --includedir=/usr/lib/gcc/powerpc-unknown-linux-gnu/4.1.2/include --datadir=/usr/share/gcc-data/powerpc-unknown-linux-gnu/4.1.2 --mandir=/usr/share/gcc-data/powerpc-unknown-linux-gnu/4.1.2/man --infodir=/usr/share/gcc-data/powerpc-unknown-linux-gnu/4.1.2/info --with-gxx-include-dir=/usr/lib/gcc/powerpc-unknown-linux-gnu/4.1.2/include/g++-v4 --host=powerpc-unknown-linux-gnu --build=powerpc-unknown-linux-gnu --enable-altivec --enable-nls --without-included-gettext --with-system-zlib --disable-checking --disable-werror --enable-secureplt --disable-libunwind-exceptions --disable-multilib --enable-libmudflap --disable-libssp --enable-languages=c,c++,java,fortran --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
Thread model: posix
gcc version 4.1.2 (Gentoo 4.1.2 p1.0.1)


Code:

emerge =sys-devel/gcc-3.4.1-r3
gcc-config -f powerpc-unknown-linux-gnu-3.4.1
source /etc/profile


Code:

gcc -v


Quote:

Using built-in specs.
Configured with: /var/tmp/portage/sys-devel/gcc-3.4.1-r3/work/gcc-3.4.1/configure --prefix=/usr --bindir=/usr/powerpc-unknown-linux-gnu/gcc-bin/3.4 --includedir=/usr/lib/gcc/powerpc-unknown-linux-gnu/3.4.1/include --datadir=/usr/share/gcc-data/powerpc-unknown-linux-gnu/3.4 --mandir=/usr/share/gcc-data/powerpc-unknown-linux-gnu/3.4/man --infodir=/usr/share/gcc-data/powerpc-unknown-linux-gnu/3.4/info --enable-shared --host=powerpc-unknown-linux-gnu --target=powerpc-unknown-linux-gnu --with-system-zlib --enable-languages=c,c++,f77,java --enable-threads=posix --enable-long-long --disable-checking --disable-libunwind-exceptions --enable-cstdio=stdio --enable-version-specific-runtime-libs --with-gxx-include-dir=/usr/lib/gcc/powerpc-unknown-linux-gnu/3.4.1/include/g++-v3 --with-local-prefix=/usr/local --disable-werror --enable-shared --enable-nls --without-included-gettext --disable-multilib --enable-__cxa_atexit --enable-clocale=gnu
Thread model: posix
gcc version 3.4.1 20040803 (Gentoo Linux 3.4.1-r3, ssp-3.4-2, pie-8.7.6.5)


Code:

nano /etc/env.d/gcc/powerpc-unknown-linux-gnu/gcc-bin.3.4.1


Quote:

PATH="/usr/powerpc-unknown-linux-gnu/gcc-bin/3.4"
ROOTPATH="/usr/powerpc-unknown-linux-gnu/gcc-bin/3.4"
LDPATH="/usr/lib/gcc-lib/powerpc-unknown-linux-gnu/3.4.1"
MANPATH="/usr/share/gcc-data/powerpc-unknown-linux-gnu/3.4/man"
INFOPATH="/usr/share/gcc-data/powerpc-unknown-linux-gnu/3.4/info"
STDCXX_INCDIR="g++-v3"
CC="gcc"
CXX="g++"


Code:

nano /etc/env.d/gcc/powerpc-unknown-linux-gnu/gcc-bin.4.1.2


Quote:

PATH="/usr/powerpc-unknown-linux-gnu/gcc-bin/4.1.2"
ROOTPATH="/usr/powerpc-unknown-linux-gnu/gcc-bin/4.1.2"
GCC_PATH="/usr/powerpc-unknown-linux-gnu/gcc-bin/4.1.2"
LDPATH="/usr/lib/gcc/powerpc-unknown-linux-gnu/4.1.2"
MANPATH="/usr/share/gcc-data/powerpc-unknown-linux-gnu/4.1.2/man"
INFOPATH="/usr/share/gcc-data/powerpc-unknown-linux-gnu/4.1.2/info"
STDCXX_INCDIR="g++-v4"



Code:

gcc -o endian endian.c


Quote:

In file included from endian.c:2:
/usr/include/stdio.h:34:21: stddef.h: No such file or directory
In file included from /usr/include/_G_config.h:44,
from /usr/include/libio.h:32,
from /usr/include/stdio.h:72,
from endian.c:2:
/usr/include/gconv.h:72: error: parse error before "size_t"
/usr/include/gconv.h:88: error: parse error before "size_t"
/usr/include/gconv.h:97: error: parse error before "size_t"
/usr/include/gconv.h:174: error: parse error before "size_t"
/usr/include/gconv.h:177: error: parse error before '}' token
In file included from /usr/include/libio.h:32,
from /usr/include/stdio.h:72,
from endian.c:2:
/usr/include/_G_config.h:47: error: field `__cd' has incomplete type
/usr/include/_G_config.h:50: error: field `__cd' has incomplete type
In file included from /usr/include/stdio.h:72,
from endian.c:2:
/usr/include/libio.h:53:21: stdarg.h: No such file or directory
In file included from /usr/include/stdio.h:72,
from endian.c:2:
/usr/include/libio.h:328: error: parse error before "size_t"
/usr/include/libio.h:332: error: `size_t' undeclared here (not in a function)
/usr/include/libio.h:334: error: parse error before '}' token
/usr/include/libio.h:360: error: parse error before "size_t"
/usr/include/libio.h:369: error: parse error before "size_t"
/usr/include/libio.h:481: error: parse error before "__gnuc_va_list"
/usr/include/libio.h:483: error: parse error before "__gnuc_va_list"
/usr/include/libio.h:485: error: parse error before "_IO_sgetn"
/usr/include/libio.h:485: error: parse error before "size_t"
In file included from endian.c:2:
/usr/include/stdio.h:306: error: parse error before "size_t"
/usr/include/stdio.h:313: error: parse error before "size_t"
/usr/include/stdio.h:341: error: parse error before "__gnuc_va_list"
/usr/include/stdio.h:346: error: parse error before "__gnuc_va_list"
/usr/include/stdio.h:349: error: parse error before "__gnuc_va_list"
/usr/include/stdio.h:355: error: parse error before "size_t"
/usr/include/stdio.h:359: error: parse error before "size_t"
/usr/include/stdio.h:608: error: parse error before "fread"
/usr/include/stdio.h:608: error: parse error before "size_t"
/usr/include/stdio.h:614: error: parse error before "fwrite"
/usr/include/stdio.h:614: error: parse error before "size_t"
/usr/include/stdio.h:636: error: parse error before "fread_unlocked"
/usr/include/stdio.h:636: error: parse error before "size_t"
/usr/include/stdio.h:638: error: parse error before "fwrite_unlocked"
/usr/include/stdio.h:638: error: parse error before "size_t"
endian.c: In function `main':
endian.c:4: warning: return type of 'main' is not `int'
endian.c: At top level:
/usr/include/gconv.h:176: warning: array '__data' assumed to have one element



looking around my system i found that "/usr/lib/gcc-lib/3.4.1" should be "/usr/lib/gcc/powerpc-unknown-linux-gnu/3.4.1"
so it seems that moving this library in that path makes the gcc-3.4.1 able to compile .c files (i mean the endian.c has success)


why did emerge put that lib into the wrong path?
Back to top
View user's profile Send private message
ddc
Guru
Guru


Joined: 29 Aug 2006
Posts: 527

PostPosted: Tue Sep 25, 2007 8:42 am    Post subject: Reply with quote

with this gcc-3.4.1 the (testing) emerge of mpg321 has success while the emerge of qemu fails

Quote:

softfloat.c:4742: internal compiler error: in choose_reload_regs, at reload1.c:5790
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:https://bugs.gentoo.org/> for instructions.
Preprocessed source stored into /var/tmp/portage/app-emulation/qemu-softmmu-0.9.0/temp/ccQdmgFf.out file, please attach this to your bugreport.
make[1]: *** [fpu/softfloat.o] Error 1
make[1]: Leaving directory `/var/tmp/portage/app-emulation/qemu-softmmu-0.9.0/work/qemu-0.9.0/sparc-softmmu'
make: *** [subdir-sparc-softmmu] Error 2
*
* ERROR: app-emulation/qemu-softmmu-0.9.0 failed.
* Call stack:
* ebuild.sh, line 1654: Called dyn_compile
* ebuild.sh, line 990: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* qemu-softmmu-0.9.0.ebuild, line 98: Called die
*
* make failed
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/app-emulation/qemu-softmmu-0.9.0/temp/build.log'.
*

* Messages for package app-emulation/qemu-softmmu-0.9.0:

*
* ERROR: app-emulation/qemu-softmmu-0.9.0 failed.
* Call stack:
* ebuild.sh, line 1654: Called dyn_compile
* ebuild.sh, line 990: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* qemu-softmmu-0.9.0.ebuild, line 98: Called die
*
* make failed
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/app-emulation/qemu-softmmu-0.9.0/temp/build.log'.
*
Back to top
View user's profile Send private message
JoseJX
Retired Dev
Retired Dev


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Tue Sep 25, 2007 1:09 pm    Post subject: Reply with quote

#1. I told you to use 3.4.6-r2, that is the latest gcc-v3 version and the one most likely to work
#2. Use gcc-config to switch the active compiler, don't move links/files around yourself, you'll only break things
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
ddc
Guru
Guru


Joined: 29 Aug 2006
Posts: 527

PostPosted: Tue Sep 25, 2007 3:06 pm    Post subject: Reply with quote

JoseJX wrote:
#1. I told you to use 3.4.6-r2, that is the latest gcc-v3 version and the one most likely to work
#2. Use gcc-config to switch the active compiler, don't move links/files around yourself, you'll only break things


1) i will try the 3.4.6-r2 ! (i'm emerging it now)
2) it is not my fault if i've correctly emerged a gcc and emerge has put the working directory in the wrong place

i mean i emerged the gcc-3.4.1, it has been emerged, i've tested it with a test.c file and it fails (as you can read) ....
what should you do ?
with the fix i've done, the endian.c (testing file) has been correctly compiled, and mpg321 has been correctly emerged with the downgraded gcc !


i will inform you about emerging qemu with gcc-3.4.6-r2.
the question is: has somebody got success in emerging qemu ? if so, how ?
Back to top
View user's profile Send private message
ddc
Guru
Guru


Joined: 29 Aug 2006
Posts: 527

PostPosted: Tue Sep 25, 2007 5:30 pm    Post subject: Reply with quote

well, emerged gcc-3.4.6-r2: it works without any fix up
i tested it emerging mpg321: all is OK, the mpg321 is well working

Quote:

Calculating dependencies ..... ....... done!
>>> Verifying ebuild Manifests...

>>> Emerging (1 of 3) app-emulation/qemu-softmmu-0.9.0 to /
* qemu-0.9.0.tar.gz RMD160 ... [ ok ]
* qemu-0.9.0.tar.gz SHA1 ... [ ok ]
* qemu-0.9.0.tar.gz SHA256 ... [ ok ]
* qemu-0.9.0.tar.gz size ... [ ok ]
* checking ebuild checksums ... [ ok ]
* checking auxfile checksums ... [ ok ]
* checking miscfile checksums ... [ ok ]
* checking qemu-0.9.0.tar.gz ... [ ok ]
>>> Unpacking source...
>>> Unpacking qemu-0.9.0.tar.gz to /var/tmp/portage/app-emulation/qemu-softmmu-0.9.0/work
* Applying qemu-softmmu-0.9.0-ide-cd.patch ...
[ ok ]
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/app-emulation/qemu-softmmu-0.9.0/work/qemu-0.9.0 ...
Install prefix /usr
BIOS directory /usr/share/qemu
binary directory /usr/bin
Manual directory /usr/share/man
ELF interp prefix /usr/gnemul/qemu-%M
Source path /var/tmp/portage/app-emulation/qemu-softmmu-0.9.0/work/qemu-0.9.0
C compiler powerpc-unknown-linux-gnu-gcc
Host C compiler powerpc-unknown-linux-gnu-gcc
make make
install install
host CPU powerpc
host big endian yes
target list i386-softmmu ppc-softmmu sparc-softmmu x86_64-softmmu mips-softmmu mipsel-softmmu arm-softmmu
gprof enabled no
profiler no
static build no
SDL support no
mingw32 support no
Adlib support yes
CoreAudio support no
ALSA support yes
DSound support no
FMOD support no
kqemu support no
Documentation yes

...

powerpc-unknown-linux-gnu-gcc -Wall -O2 -g -fno-strict-aliasing -I. -I.. -I/var/tmp/portage/app-emulation/qemu-softmmu-0.9.0/work/qemu-0.9.0/target-sparc -I/var/tmp/portage/app-emulation/qemu-softmmu-0.9.0/work/qemu-0.9.0 -D__powerpc__ -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/var/tmp/portage/app-emulation/qemu-softmmu-0.9.0/work/qemu-0.9.0/fpu -I/var/tmp/portage/app-emulation/qemu-softmmu-0.9.0/work/qemu-0.9.0/slirp -c -o translate.o /var/tmp/portage/app-emulation/qemu-softmmu-0.9.0/work/qemu-0.9.0/target-sparc/translate.c
powerpc-unknown-linux-gnu-gcc -Wall -O2 -g -fno-strict-aliasing -I. -I.. -I/var/tmp/portage/app-emulation/qemu-softmmu-0.9.0/work/qemu-0.9.0/target-sparc -I/var/tmp/portage/app-emulation/qemu-softmmu-0.9.0/work/qemu-0.9.0 -D__powerpc__ -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/var/tmp/portage/app-emulation/qemu-softmmu-0.9.0/work/qemu-0.9.0/fpu -I/var/tmp/portage/app-emulation/qemu-softmmu-0.9.0/work/qemu-0.9.0/slirp -c -o fpu/softfloat.o /var/tmp/portage/app-emulation/qemu-softmmu-0.9.0/work/qemu-0.9.0/fpu/softfloat.c
/var/tmp/portage/app-emulation/qemu-softmmu-0.9.0/work/qemu-0.9.0/fpu/softfloat.c: In function `float128_mul':
/var/tmp/portage/app-emulation/qemu-softmmu-0.9.0/work/qemu-0.9.0/fpu/softfloat.c:4742: internal compiler error: in choose_reload_regs, at reload1.c:5790
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:https://bugs.gentoo.org/> for instructions.
Preprocessed source stored into /var/tmp/portage/app-emulation/qemu-softmmu-0.9.0/temp/ccQdmgFf.out file, please attach this to your bugreport.
make[1]: *** [fpu/softfloat.o] Error 1
make[1]: Leaving directory `/var/tmp/portage/app-emulation/qemu-softmmu-0.9.0/work/qemu-0.9.0/sparc-softmmu'
make: *** [subdir-sparc-softmmu] Error 2
*
* ERROR: app-emulation/qemu-softmmu-0.9.0 failed.
* Call stack:
* ebuild.sh, line 1654: Called dyn_compile
* ebuild.sh, line 990: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* qemu-softmmu-0.9.0.ebuild, line 98: Called die
*
* make failed
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/app-emulation/qemu-softmmu-0.9.0/temp/build.log'.
*

* Messages for package app-emulation/qemu-softmmu-0.9.0:

*
* ERROR: app-emulation/qemu-softmmu-0.9.0 failed.
* Call stack:
* ebuild.sh, line 1654: Called dyn_compile
* ebuild.sh, line 990: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* qemu-softmmu-0.9.0.ebuild, line 98: Called die
*
* make failed
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/app-emulation/qemu-softmmu-0.9.0/temp/build.log'.
*


how to fix it ?
Back to top
View user's profile Send private message
JoseJX
Retired Dev
Retired Dev


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Tue Sep 25, 2007 6:52 pm    Post subject: Reply with quote

Okay, the compiler is failing. It's an internal error. You could try recompiling gcc-3.4 with gcc-3.4 instead of 4.1
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
ddc
Guru
Guru


Joined: 29 Aug 2006
Posts: 527

PostPosted: Tue Sep 25, 2007 9:48 pm    Post subject: Reply with quote

i've recompiled 3.4.6 with 3.4.6, no solution, still having the emerge issue with qemu
Back to top
View user's profile Send private message
ddc
Guru
Guru


Joined: 29 Aug 2006
Posts: 527

PostPosted: Tue Sep 25, 2007 10:36 pm    Post subject: Reply with quote

may it be a binutils problem ?
i see a lot of binaries in /usr/powerpc-unknown-linux-gnu/bin-utils/ {2.15, 2.16, 2.17}
Back to top
View user's profile Send private message
JoseJX
Retired Dev
Retired Dev


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Wed Sep 26, 2007 2:28 am    Post subject: Reply with quote

It built perfectly fine here.

I've put packages built for G4 at http://dev.gentoo.org/~josejx/qemu
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
ddc
Guru
Guru


Joined: 29 Aug 2006
Posts: 527

PostPosted: Wed Sep 26, 2007 10:51 am    Post subject: Reply with quote

JoseJX wrote:
It built perfectly fine here


how did you do ?
with what compiler ?
with what binutils ?
how did you downgrade the gcc to 3.4.x ?
with what CFLAGS ?

i'd like to recompile on my machine, to have all working


the status here (with gcc 3.4.6 binutils 2.17 CFLAGS -mcpu=powerpc -mtune=powerpc)
games-emulation/dosbox has success
app-emulation/qemu-softmmu has success
app-emulation/qemu-user fails
app-emulation/qemu not compiled as qemu-user fails
Back to top
View user's profile Send private message
JoseJX
Retired Dev
Retired Dev


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Wed Sep 26, 2007 12:30 pm    Post subject: Reply with quote

I built it on a ~ppc system, with the latest ~ppc versions of all software involved. I followed the directions I gave you before (emerged the 3.4.6-r2 version of gcc). Switched to that compiler and emerged qemu with my default (same as the G4 profile) CFLAGS. It worked fine. I don't know why yours didn't, just use the packages. :p
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
ddc
Guru
Guru


Joined: 29 Aug 2006
Posts: 527

PostPosted: Wed Sep 26, 2007 5:18 pm    Post subject: Reply with quote

well, i cleaned my harddisk again
i donwloaded the last stage3-g4 + the last one portage
i installed them
i emerge --sync
i emerge --update world
gcc.4.1.1 has been updated to 4.1.2
binutils is 2.17

i emerge the gentoolkit
now, revdep-rebuild reports the system has problem
i emerged python
i emerged perl
revdep-rebuild says the system is now OK

i emerge xorg-x11: success
i emerged openoffice reducing the CFLAGS: success
i emerged the gcc-3.4.6: success
i switched to it
i emerged qemu ....
... qemu-softmmu: success
... qemu-users: gcc fails in linking the objects
(in /usr/bin i have qemu* but it is emerged from qemu-softmmu)

so, what is wrong with this procedure ?
why 2007.0 has problem just out of a fresh install ?

could you tarball (.tgz) me your gcc-4.1.2 & gcc-3.4.6 ?

thankyou
Back to top
View user's profile Send private message
JoseJX
Retired Dev
Retired Dev


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Thu Sep 27, 2007 12:42 am    Post subject: Reply with quote

Like I said, it works fine for me on ~ppc. The only major difference that you could try is to use the ~ppc version of binutils (2.18).
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
ddc
Guru
Guru


Joined: 29 Aug 2006
Posts: 527

PostPosted: Thu Sep 27, 2007 10:23 am    Post subject: Reply with quote

JoseJX wrote:
Like I said, it works fine for me on ~ppc. The only major difference that you could try is to use the ~ppc version of binutils.


as i asked, i understand you have success, but i have not with a fresh install
could you please tell me if there is something wrong in the procedure i used ?
could you please tarball your gcc 3.4.6 just to understand if the problem is in its emerging ?

tonight i emerged everythingelse without errors. that means x11, firefox, abiword, openoffice, ecc

the only problem i found in the qemu-ebuilds

so, could you tell me exactly what you have done just out of a fresh 2006.1 install ?
how did you fix the "broken" reported by ldev-rebuild -p ?
also have you emerged the qemu-softmmu (that i'm able to emerge without problem) or have you also emerged the qemu and qemu-users (where i found problem) ?

i need to understand why you have success (with what environment, and with what procedure), and why i have no success (with qemu-users)
Back to top
View user's profile Send private message
JoseJX
Retired Dev
Retired Dev


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Thu Sep 27, 2007 2:30 pm    Post subject: Reply with quote

Please look at what I wrote. I am not using 2006.1. I am using a *current* ~ppc install. I did not try it on a stable system, it's certainly possible that binutils 2.17 doesn't work with 3.4.6, since ld (binutils) is what's breaking. Please just try the ~ppc version of binutils (2.18). The code that qemu uses to perform the emulation is generated, not written by hand. As such, it can have issues other code doesn't have (this is why it requires gcc-3.x). Anyway, please, please, please, just try the newer binutils. I'm pretty sure it will fix your problem.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
ddc
Guru
Guru


Joined: 29 Aug 2006
Posts: 527

PostPosted: Fri Sep 28, 2007 1:50 pm    Post subject: Reply with quote

i emerged the ~ppc binutils 2.18
i recompiled the qemu and it is working



so i think the error i had was caused by the binutils-2.17's linker
this is the previous error message

Quote:
gcc -g -Wl,-T,/var/tmp/portage/app-emulation/qemu-user-0.9.0/work/qemu-0.9.0/ppc.ld -o qemu-i386 main.o syscall.o mmap.o signal.o path.o osdep.o thunk.o elfload.o linuxload.o vm86.o libqemu.a gdbstub.o -lm
/usr/lib/gcc/powerpc-unknown-linux-gnu/3.4.6/../../../../powerpc-unknown-linux-gnu/bin/ld: qemu-i386: Not enough room for program headers (allocated 9, need 10)
Section to Segment mapping:
Segment Sections...
00: PHDR:
01: INTERP: .interp
02: LOAD: .interp .note.ABI-tag .hash .dynsym .dynstr .gnu.version .gnu.version_r .rela.got .rela.bss .rela.plt .init .text .glink .fini .rodata .eh_frame_hdr .eh_frame
03: LOAD: .ctors .dtors .jcr .got2 .dynamic .data .got .sdata .sbss
04: LOAD: .plt .bss
05: DYNAMIC: .dynamic
06: NOTE: .note.ABI-tag
07: EH_FRAME: .eh_frame_hdr
08: STACK:
09: PAX_FLAGS:
/usr/lib/gcc/powerpc-unknown-linux-gnu/3.4.6/../../../../powerpc-unknown-linux-gnu/bin/ld: final link failed: Bad value
collect2: ld returned 1 exit status



so, we have learned the lesson:

to emerge qemu you need
1) to emerge gcc 3.4.6-r2
2) to emerge binutils 2.18
3) to (temporarily) switch your dev environment to them


thread SOLVED
Back to top
View user's profile Send private message
mightymephisto
n00b
n00b


Joined: 19 Dec 2005
Posts: 9

PostPosted: Thu Oct 18, 2007 10:02 pm    Post subject: Reply with quote

I know this is marked as solved, but I have managed to get qemu to compile with gcc4 with the thanks of this patch

http://www.kju-app.org/proj/browser/trunk/patches/qemu-0.9.0-gcc4.patch?format=txt
  • Copied /usr/portage/app-emulation/qemu-softmmu into my portage overlay
  • Downloaded patch into files directory
  • Added epatch "${FILESDIR}"/qemu-0.9.0-gcc4.patch after the cd ${S} in the ebuild src_unpack
  • Comment out all of pkg_setup
Back to top
View user's profile Send private message
ddc
Guru
Guru


Joined: 29 Aug 2006
Posts: 527

PostPosted: Thu Oct 25, 2007 11:28 pm    Post subject: Reply with quote

does it work right ?

here i have 2 version of qemu-0.9.0: one compiled into a previous 2007.0 gentoo, one compiled into 2007.0
the first is perfectly working, the second stops itself with this warning

Code:
Could not configure '/dev/rtc' to have a 1024 Hz timer. This is not a fatal
error, but for better emulation accuracy either use a 2.6 host Linux kernel or
type 'echo 1024 > /proc/sys/dev/rtc/max-user-freq' as root.


the same kernel-2.6.12 is equipping both these two machines
i can't understand what is wrong with this 2007.0: too many issues !
Back to top
View user's profile Send private message
JoseJX
Retired Dev
Retired Dev


Joined: 28 Apr 2002
Posts: 2774

PostPosted: Mon Oct 29, 2007 1:26 am    Post subject: Reply with quote

This has nothing to do with 2007.0, Gentoo releases like 2007.0 are kind of like a bookmark or snapshot of the tree at a point in time. That's all. :p

Anyway, that warning is because you don't have RTC support in your kernel. It should go away if you add RTC emulation afaik. I'm not going to comment on the gcc-4 patch since I've never tried it, but I'm pretty sure Gentoo won't include it until the Qemu upstream does.
_________________
Gentoo PPC FAQ: http://www.gentoo.org/doc/en/gentoo-ppc-faq.xml
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on PPC All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
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