Now, my system is quite weird when it comes to xFLAGS, and sometimes I just want to ease'em a bit; or two;) I even have a bunch of aliases for different CFLAGS/LDFLAGS combinations )))) like "easy", "safe", "safest" etc. :))
I'm experiencing some troubles with Superkaramba apps complaining I don't have PyQt. Whereas I do, of course. Some forum browsing put me into an attempt to recompile PyQt while omitting -fvisibility-inlines-hidden and -fvisibility=hidden from CXXFLAGS. BUT.
Whenever I specify wanted CXXFLAGS on the command line just before the words "emerge PyQt"
OR CHANGE THEM EXPLICITLY IN MAKE.CONF, PyQt gets compiled with my usual not-so-sane flags. I can even try -Os -- but it remains -O2 in compile log, just like it would have been normally.
(Besides, those compilation lines in the log look a bit odd, gcc options are partly doubled, like this:
g++ -c -pipe -fvisibility=hidden -fvisibility-inlines-hidden -O2 -march=pentium4 -pipe -fomit-frame-pointer -fno-ident -funroll-loops -ftracer -fvisibility-inlines-hidden -fPIC -O2 -march=pentium4 -pipe -fno-ident -fno-strict-aliasing -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -I. -I/usr/include/python2.4 -I/usr/qt/3/include -I/usr/X11R6/include -o sipqtQUuid.o sipqtQUuid.cpp
Is it strange or is it that I've never noticed such stuff??)
Why is this so? I know PyQt needs sip and qscintilla (and Qt :) - may be so much it insists being compiled with just the same options as they were?? I didn't see nothing suspicious in this sence in the ebuild.
1) Anyone to workaround the main mentioned problem?
2) Anyone to explain such behaviour of an ebuild?