[MPlayer-users] possible bug in version 1.0 rc1

[Manoa Nosea]

I attempted to compile MPlayer 1.0 rc1 on a special version of mingw
with gcc-4.2 and it appears that mplayer cannot be compiled with
profile generation (-fprofile-generate) with the vidix driver :

make[2]: Entering directory
`/d/Projects/development/MPlayer-1.0rc1/vidix/drivers'
gcc -c -I. -I.. -O1 -march=athlon-xp -pipe -ffast-math
-fomit-frame-pointer -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wall
-Wdeclaration-after-statement -fPIC -o radeon_vid.o radeon_vid.c
radeon_vid.c:1: warning: -fPIC ignored for target (all code is
position independent)
gcc -shared radeon_vid.o -L../../libdha -ldha -lm -lws2_32
-Wl,-soname,radeon_vid.so -o radeon_vid.so
../../libdha/libdha.a(pci.o):pci.c:(.text+0x153c): undefined reference
to `__gcov_init'
../../libdha/libdha.a(pci.o):pci.c:(.data+0xc4): undefined reference
to `__gcov_merge_add'
../../libdha/libdha.a(pci_names.o):pci_names.c:(.text+0x137):
undefined reference to `__gcov_init'
../../libdha/libdha.a(pci_names.o):pci_names.c:(.data+0x44): undefined
reference to `__gcov_merge_add'
../../libdha/libdha.a(libdha.o):libdha.c:(.text+0x5b3): undefined
reference to `__gcov_init'
../../libdha/libdha.a(libdha.o):libdha.c:(.data+0xe4): undefined
reference to `__gcov_merge_add'
../../libdha/libdha.a(mtrr.o):mtrr.c:(.text+0x1f): undefined reference
to `__gcov_init'
../../libdha/libdha.a(mtrr.o):mtrr.c:(.data+0x44): undefined reference
to `__gcov_merge_add'
collect2: ld returned 1 exit status
make[2]: *** [radeon_vid.so] Error 1
make[2]: Leaving directory
`/d/Projects/development/MPlayer-1.0rc1/vidix/drivers'
make[1]: *** [do_drivers] Error 2
make[1]: Leaving directory `/d/Projects/development/MPlayer-1.0rc1/vidix'
make: *** [vidix/libvidix.a] Error 2

as may be already obvious I have tried to modify some of the
compilation settings for the vidix drivers and I believe that the
$(OPTFLAGS) section in the vidix directory the drivers subdirectory
and the libdha directory is the cause for the problem, becaue if
-fprofile-generate is included i nthe optflags, that flag will go into
the vidix drivers which do not work with profile genration, it is
probably possible to remove the -fprofile-generate and -fprofile-use
options only from these specific sections, there is also another
problem as you may have already noticed, the -fPIC option which is
conflicting with the config.mak's option -fno-PIC, it may be necessary
to run a string analysis of the optflags section to avoid both of
these problems.