Bug 43921

Summary:	gcc warning options always set
Product:	[Applications] kdevelop	Reporter:	heithecker
Component:	kdevelop 2.x (obsolete)	Assignee:	KDevelop-Devel List <kdevelop-devel>
Status:	RESOLVED FIXED
Severity:	major
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description heithecker 2002-06-14 11:55:33 UTC

(*** This bug was imported into bugs.kde.org ***)

Package:           kdevelop
Version:           KDE 3.0.1 
Severity:          normal
Installed from:    SuSE RPMs
Compiler:          Not Specified
OS:                Linux
OS/Compiler notes: Not Specified

The warning options of gcc are alwas set regardless of the checkmarks in the project options/compiler folder. For example even if I deselect all warning checkmarks the compiler ist started with "g++ -DHAVE_CONFIG_H -I. -I. -I.. -Wnon-virtual-dtor -Wno-long-long -Wbad-function-cast -Wundef -Wall -pedantic -W -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -O2 -O0 -g3 -fno-exceptions -fno-check-new -c -o main.o main.cpp"


(Submitted via bugs.kde.org)

Comment 1 heithecker 2002-06-14 14:39:41 UTC

I forgot to state that my project "Terminal C++" one not a KDE/Qt one. This 
might be of interest because after having a look at admin/acinclude.m4.in I 
found that for KDE projects some flags seem to be set as default. 

Regards Sveb

-- 
Dipl.-Ing. Sven Heithecker
Institute of Computer and Communication Network Engineering
Technical University of Braunschweig Germany
heithecker@ida.ing.tu-bs.de
www.ida.ing.tu-bs.de/~svenh

Comment 2 heithecker 2002-06-14 16:07:44 UTC

Hi sorry for bothering again 

but I got other info: when I select the "Dont use predefined -O switch"-Option 
in the project/configure-settings tab all the warning options disappear. 
However in this case also the extra compiler flags (cpp/c/c++) dont appear. 

On my friend's project the project/configure-settings tab is completely 
grayed out and he does not have an "admin" folder in his project directory. 
Also he works with automake-1.4 while on my system I had to switch to 
automake-1.5 to get it running at all. We both work with "Terminal-C++" 
projects.

This is completely strange ...

-- 
Dipl.-Ing. Sven Heithecker
Institute of Computer and Communication Network Engineering
Technical University of Braunschweig Germany
heithecker@ida.ing.tu-bs.de
www.ida.ing.tu-bs.de/~svenh

Comment 3 Caleb Tennis 2002-10-09 21:08:36 UTC

There won't be any more fixes for the 2.2.x series.  This bug doesn't seem to 
be an issue with Gideon (3.0).