View previous topic :: View next topic |
Author |
Message |
davidgurvich Veteran
Joined: 23 Apr 2004 Posts: 1063
|
Posted: Tue May 09, 2006 9:57 pm Post subject: Is portage system gcc-4.1.0 compatible? Opinions |
|
|
Much better experience for me than aborted attempt with gcc-4.0.2. Aside from having gcc built with objc-gc. Once that flag was turned off, most packages either emerge cleanly or have versions in ~ppc that do.
Haven't noticed any speedier compilation though size of executable is slightly smaller. Openoffice still took 16 hours, but is smaller. Incidentally, have openoffice binary for G4 gcc-3.4.5/glibc-2.3.5 and gcc-4.1.0/glibc-2.3.6. |
|
Back to top |
|
|
davidgurvich Veteran
Joined: 23 Apr 2004 Posts: 1063
|
Posted: Tue May 09, 2006 10:31 pm Post subject: |
|
|
Have actually emerged packages that failed with gcc-3.4.5. Amarok looks good and doesn't segfault. |
|
Back to top |
|
|
fb l33t
Joined: 08 Dec 2003 Posts: 636 Location: New Zealand
|
Posted: Tue May 09, 2006 10:42 pm Post subject: |
|
|
Which version of openoffice? 2.0.1-r*?
I agree that very few package won't work with gcc4.1.0.
Here is a small list:
*Maxima seems to have problems being built with lisp compilers built with gcc4.1.0 both in ppc and ~ppc,
I guess that will go away eventually.
*transfig and xfig, unfortunately those two are quite unmaintened upstream and they use antiquated headers
that have been removed from gcc4.1.0 (use varargs.h should be migrated to stdarg.h).
*blas-atlas in ~ppc works but I think there are problems with atlas (don't remember if it was ppc or ~ppc
I removed it from my system as nothing was depending on it).
*libquicktime had some issues but it seems ~ppc now works provided that you remove the previous
ppc version of libquicktime Code: | >>> Merging media-libs/libquicktime-0.9.7-r1 to /
* For compatibility with other quicktime libraries, libquicktime was
* going to create a /usr/include/quicktime symlink, but for some
* reason that is a directory on your system.
* Please check that is empty, and remove it, or submit a bug
* telling us which package owns the directory. |
Why, it is libquicktime-0.9.4!
I had problems that I didn't pursue with:
*vnc
*euler |
|
Back to top |
|
|
davidgurvich Veteran
Joined: 23 Apr 2004 Posts: 1063
|
Posted: Wed May 10, 2006 1:11 am Post subject: |
|
|
Vnc did not work with gcc-3.4.x. Compiled cleanly and did not work at all, so I doubt that is an issue with gcc-4.1.0 and is an issue with vnc. I think vnc has been trouble for ppc, 64-bit x86, and some other architectures.
Euler I don't know about, but euler-1.61.0 compiled cleanly, though 1.60 had trouble.
Blas-atlas needs to be emerged in a special syntax as well as needing the ~ppc version.
Code: | interactive=1 emerge =blas-atlas-3.7.11 |
Maxima will take some time and I'll update the post to reflect that.
Openoffice version 2.0.1-r1 with:
Code: | USE="binfilter eds gnome gtk java kde mozilla xml -ldap" |
Last edited by davidgurvich on Wed May 10, 2006 2:51 am; edited 1 time in total |
|
Back to top |
|
|
fb l33t
Joined: 08 Dec 2003 Posts: 636 Location: New Zealand
|
Posted: Wed May 10, 2006 2:13 am Post subject: |
|
|
davidgurvich wrote: | Vnc did not work with gcc-3.4.x. Compiled cleanly and did not word at all, so I doubt that is an issue with gcc-4.1.0 and is an issue with vnc. I think vnc has been trouble for ppc, 64-bit x86, and some other architectures.
Euler I don't know about, but euler-1.61.0 compiled cleanly, though 1.60 had trouble.
Blas-atlas needs to be emerged in a special syntax as well as needing the ~ppc version.
Code: | interactive=1 emerge =blas-atlas-3.7.11 |
Maxima will take some time and I'll update the post to reflect that.
Openoffice version 2.0.1-r1 with:
Code: | USE="binfilter eds gnome gtk java kde mozilla xml -ldap" |
|
I was sure I had vnc compiled with 3.4.x (and it was working for me) however
for what I wanted a vnc server for x11vnc was better suited and it works.
I didn't insist on euler because I wasn't really using it. So away it did go.
I don't need to do anything special for blas-atlas (I just gave it another go and
it doesn't seem to need any interactive input) - you said in another thread
that you have a ~ppc version of portage it may be related.
Last time I tried OOo-2.0.1-r1 it was broken there may have been a fix, I should
give it another go, although from my last try with 2.0.2-r2 I think glibc2.4 breaks
the version of STLport shipped with OOo. |
|
Back to top |
|
|
davidgurvich Veteran
Joined: 23 Apr 2004 Posts: 1063
|
Posted: Wed May 10, 2006 3:04 am Post subject: |
|
|
Maxima with all dependencies using the ~ppc version seems to be compile happily with clisp, and seems to run with no problems.
Prior to getting OO-2.0.1-r1 to compile cleanly I did the following:
- Removed the other gcc versions except for 4.1.0 after using fix_libtool_files.sh. Then rebuilt the toolchain once I had a gcc-4.1.0 that was able to compile cleanly more than once. Before that OO2 had failed during uno build.
- Modified the CFLAGS to the following:
Quote: | CFLAGS="-O -mtune=G4 -mcpu=G4 -mabi=altivec" | from Quote: | CFLAGS="-O2 -mtune=G4 -altivec -mabi=altivec -pipe -fomit-frame-pointer" |
PS:
I am also using glibc-2.3.6-r3, not sure about 2.4 yet. |
|
Back to top |
|
|
fb l33t
Joined: 08 Dec 2003 Posts: 636 Location: New Zealand
|
Posted: Wed May 10, 2006 3:12 am Post subject: |
|
|
By rebuilding the toolchain you mean "gcc binutils and glibc" or is there something else I am forgetting?
I am checking for maxima with clisp again.
I am clean in regards to hardlink to gcc3.4.x so that bit shouldn't be a problem. |
|
Back to top |
|
|
davidgurvich Veteran
Joined: 23 Apr 2004 Posts: 1063
|
Posted: Wed May 10, 2006 1:58 pm Post subject: |
|
|
I was having problems with cruft, so I took every package that would be installed with -e system upto and including gcc. |
|
Back to top |
|
|
fb l33t
Joined: 08 Dec 2003 Posts: 636 Location: New Zealand
|
Posted: Wed May 10, 2006 11:48 pm Post subject: |
|
|
I am quite surprised. I reemerge clisp and maxima and it seems to run fine now.
I problably had some problem with my tool chain the last time I tried.
So maxima is out of trouble.
Now I will have to try rebuilding OOo-2.0.1-r1.
Update
Rebuilding OOo-2.0.1-r1 failed in STLport as OOo-2.0.2-r2 now does.
I highely suspect glibc 2.4 but I will try an "emerge -eD system" as
well to see if there are any effects.
For info the error is as follow: Code: | g++ -D_REENTRANT -DGXX_INCLUDE_PATH=/usr/lib/gcc/powerpc-unknown-linux-gnu/4.1.0/include/g++-v4 -fexceptions -I../stlport -Wall -W -Wno-sign-compare -Wno-unused -Wno-uninitialized -ftemplate-depth-32 -fno-strict-aliasing -O2 -fPIC dll_main.cpp -c -o ../lib/obj/GCCppc/ReleaseD/dll_main.o
../stlport/cstdio:111: error: '__std_alias::vsnprintf' has not been declared
make[1]: *** [../lib/obj/GCCppc/ReleaseD/dll_main.o] Error 1
make[1]: Leaving directory `/var/tmp/portage/openoffice-2.0.1-r1/work/ooo-build-2.0.1.3/build/ooa680-m1/stlport/unxlngppc.pro/misc/build/STLport-4.5/src'
dmake: Error code 2, while making './unxlngppc.pro/misc/build/so_built_so_stlport'
'---* tg_merge.mk *---'
ERROR: Error 65280 occurred while making /var/tmp/portage/openoffice-2.0.1-r1/work/ooo-build-2.0.1.3/build/ooa680-m1/stlport
make: *** [stamp/build] Error 1
|
|
|
Back to top |
|
|
davidgurvich Veteran
Joined: 23 Apr 2004 Posts: 1063
|
Posted: Thu May 11, 2006 1:36 am Post subject: |
|
|
I think that is the reason I am not using glibc-2.4. I had tried 2.4 accidentally, when I added ~ppc to my make.conf ACCEPT_KEYWORDS. It was sometime in 2005. That is when I removed ~ppc from make.conf and started using portage.keywords with '=' for each package. Along with package.mask, package.provided, and package.use.
I also remember having a problem with STLport and oo-2.0.0, but haven't had problems with the 2.0.1 series. Probably due to the above. |
|
Back to top |
|
|
|