http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47723
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-02-14 16:19:39 UTC --- (In reply to comment #4) > > So if I understand what you need, you need me to build kdelibs with 4.5.2 to > the point of failure with? > > cmake ../ \ > -DCMAKE_C_COMPILER="/usr/bin/gcc -save-temps" \ > -DCMAKE_CXX_COMPILER="/usr/bin/g++ -save-temps" \ No, you can just run it to the point of failure, then repeat the command that failed, adding -save-temps. You don't need to use -save-temps for everything. > Then I need to attach the precompiled sources -- which if I'm doing an out > of > source build in a temporary kdebase/src directory are which files? Are the > precompiled sources going to end up in the kdebase/src/kcontrol/iccconfig > directory -or- do you need the entire kdebase/src directory? Please don't send the whole directory. Just generate the preprocessed file for the one source file that fails to compile, and send us that preprocessed file, the one with a .ii extension. > I'm happy to get you anything that you need, but as I mentioned, this is the > first possible compiler error I've run into. I want to do my part and get you > everything that is needed so we can either rule-in or rule-out a gcc issue, > but > I just need a bit of explanation of what "what you need" is. I obviously > misunderstood what the precompiled sources were, but I'm happy to go rebuild > with -save-temps. I just need to know if simply adding -save-temps to the gcc > flags will do it? Yes, but only do it for the gcc command that fails. We don't want dozens of preprocessed files for the things that compile ok, that's no use to anyone.
