Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#11012 closed Bug Report - General (Won't Fix)

mythtv-0.25.2_p20120716 - configure sets incorrect CFLAGS

Reported by: klamp <klampiar@…> Owned by:
Priority: minor Milestone: unknown
Component: MythTV - General Version: Unspecified
Severity: medium Keywords: CFLAGS
Cc: Ticket locked: yes


This is basically copy of bug reported at

configure apparently constructs incorrect CFLAGS to pass to gcc.

for given system CFLAGS (from emerge --info): CFLAGS="-march=native -O2 -pipe -ggdb" CXXFLAGS="-march=native -O2 -pipe -ggdb"

configure is called with (config.log): ./configure --cc=i686-pc-linux-gnu-gcc --cxx=i686-pc-linux-gnu-g++ --ar=i686-pc-linux-gnu-ar --extra-cflags=-march=native -O2 -pipe -ggdb --extra-cxxflags=-march=native -O2 -pipe -ggdb --extra-ldflags=-Wl,-O1 -Wl,--as-needed --prefix=/usr --libdir=/usr/lib --libdir-name=lib --mandir=/usr/share/man --enable-audio-alsa --disable-audio-jack --disable-audio-pulseoutput --disable-altivec --disable-dvb --disable-firewire --disable-lirc --enable-libxvid --dvb-path=/usr/include --enable-xrandr --enable-xv --enable-x11 --enable-nonfree --disable-libcec --disable-libdns-sd --enable-libtheora --enable-libvorbis --enable-libmp3lame --enable-libx264 --enable-libvpx --enable-libfaac --with-bindings=perl,python --python=python2.7 --compile-type=release --enable-debug --disable-stripping --enable-vdpau --enable-vaapi --disable-joystick-menu --enable-symbol-visibility --enable-pic --cpu=host --disable-distcc --disable-ccache

and produces (config.mak): CFLAGS=-march=native -O2 -pipe -ggdb -march=native -O2 -pipe -ggdb -march=pentium4 -std=c99 -fomit-frame-pointer -fPIC -pthread -g -Wall -Wno-parentheses -Wno-switch -Wdisabled-optimization -Wpointer-arith -Wredundant-decls -Wno-pointer-sign -Wcast-qual -Wwrite-strings -Wtype-limits -Wundef -Wmissing-prototypes -O3 -fno-math-errno -fno-signed-zeros -fno-tree-vectorize

which results in gcc call: i686-pc-linux-gnu-gcc -c -pipe -D_ISOC99_SOURCE -D_POSIX_C_SOURCE=200112 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -DPIC -march=native -O2 -pipe -ggdb -march=native -O2 -pipe -ggdb -march=pentium4 -std=c99 -fomit-frame-pointer -fPIC -pthread -g -Wall -Wno-parentheses -Wno-switch -Wdisabled-optimization -Wpointer-arith -Wredundant-decls -Wno-pointer-sign -Wcast-qual -Wwrite-strings -Wtype-limits -Wundef -Wmissing-prototypes -O3 -fno-math-errno -fno-signed-zeros -fno-tree-vectorize -DMMX -Di386 -D_GNU_SOURCE -I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include -I/usr -I/usr/include/libxml2 -o dummy.o dummy.c

While I expect system CFLAGS, or CFLAGS as close to system as possible, to be used.

Doug Goldstein: Take it up with upstream. I don't like how they mess with CFLAGS. For the longest time they insisted we block all user CFLAGS and use what they generate.

I have to second Doug Goldstein here, I dont like how you mess with CFLAGS either. Can you please just follow behavior of majority of software and honor user set CFLAGS?

Change History (6)

comment:1 Changed 9 years ago by danielk

Resolution: Won't Fix
Status: newclosed

We don't want to deal with the bug reports that result from users messing with CFLAGS.

comment:2 Changed 9 years ago by klamp <klampiar@…>

Hm, that's exactly something I would expect from developers of software that segfaults every 60 minutues or so. No hard feelings involved, just observation of performance of your code @ gentoo.

comment:3 Changed 9 years ago by Doug Goldstein <cardoe@…>

Don't lump Gentoo into your own feelings. MythTV is open source, you are more than welcome to take the source and modify it.

comment:4 Changed 9 years ago by klampiar@…

I never did, and I was explicit that my comment was based on objective facts of observation of code perfomace, not feelings. I also believe that this performance will be more or less equal on other distros. Maintaning own fork of "moving target" project is problematic.

comment:5 Changed 9 years ago by danielk

Ticket locked: set

comment:6 Changed 9 years ago by Raymond Wagner

Trac is not a forum for discussion. If you wish to continue the discussion, please do so on one of the mailing lists.

See existing responses...

Note: See TracTickets for help on using tickets.