building MPlayer: gcc-3.4.x compiler issues
Albrecht Dreß
albrecht.dress at arcor.de
Mon Jan 10 11:53:20 MST 2005
Hi Joseph!
Am 09.01.05 23:48 schrieb(en) Joseph E. Sacco, Ph.D.:
> I built gcc-3.4.3 on a G4 7410 and used it to successfully build
> MPlayer.
Good news!
> In particular, yuv2rgb_altivec.c compiles, albeit with some warnings:
>
> /usr/local/gcc/3.4.3/bin/gcc -c -I../libvo -I../../libvo
> -I/usr/X11R6/include -O4 -mcpu=7400 -mtune=7400 -maltivec
> -mabi=altivec -pipe -ffast-math -fomit-frame-pointer
> -D_REENTRANT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I.
> -I.. -I.. -o yuv2rgb_altivec.o yuv2rgb_altivec.c
> yuv2rgb_altivec.c: In function `altivec_yuv2packedX':
> yuv2rgb_altivec.c:796: warning: assignment from incompatible
> pointer type
> yuv2rgb_altivec.c:803: warning: assignment from incompatible
> pointer type
Well, I tried the command line like yours on that file:
cc -c -I../libvo -I../../libvo -I/usr/X11R6/include -O3 -mcpu=7400
-mtune=7400 -maltivec -mabi=altivec -O4 -D_REENTRANT -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -I. -I.. -I.. -o yuv2rgb_altivec.o
yuv2rgb_altivec.c
and now it also compiles with gcc 3.3.3! There seeme to be a 7400 vs. 7450
problem. Hmmm...
> * My other/2, who works in the embedded systems world, tells me than the
> G4 7410 and 7450 share the same instruction set in *user* mode, which is
> the mode we can access. So..., the compiler crash you reported is
> probably not instruction set related.
See above - looks like a weird compiler bug!
> * I am using the the 2.6.9 kernel headers.
> I don't think this is the source of the problem. I looked at the output
> from the preprocessor stage and do not see any include files from
Afaik, they didn't change a lot recently... But I replaced them by
symlinks pointing to /usr/src/linux, which in turn points to my "current"
source tree...
> * I upgraded binutils, which contains the ***assembler***,
[snip]
> binutils-2.15.92.0.2-6
Already building binutils-2.15.92.0.2-5.src.rpm from FC3 - where did you
get release 6 from, btw?
> * your compiler is named "cc"
> I noticed in your code snippet that your compiler is named "cc". I
> assume that "cc" actually points to the version of gcc that you assume
> you are using.
[albrecht at antares albrecht]$ cc --version
cc (GCC) 3.3.3 (Yellow Dog Linux 3.3.3-16.ydl.4)
> * watch the compiler crash with the "-v" option set to see if anything
> new can be learned.
Not really... I think I'll also compile gcc 3.4.3 as some other
compilations failed with "-O3 -mcpu=7450" (gstreamer from Gnome 2.8, IIRC)
Thanks, cheers,
Albrecht.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Albrecht Dreß - Johanna-Kirchner-Straße 13 - D-53123 Bonn (Germany)
Phone (+49) 228 6199571 - mailto:albrecht.dress at arcor.de
GnuPG public key: http://home.arcor.de/dralbrecht.dress/pubkey.asc
_________________________________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.terrasoftsolutions.com/pipermail/yellowdog-general/attachments/20050110/2fd28656/attachment.bin
More information about the yellowdog-general
mailing list