Possible issues with FC5's gcc

Hello, Everyone
I just posted two error message on the kde list relating to errors that
I have been getting while compiling certain KDE modules from their SVN
tree. I have received responses from one person so far, and he said
this:

Are you using GCC 4.x ? In that case you'd better file a bug report
about that.

Kind regards,

and:

Op zaterdag 25 maart 2006 14:23, schreef Steven P. Ulrick:
Please forgive my ignorance, but what in the error message leads to
the conclusion that gcc is at fault?

Not all code is ready for GCC >4, sometimes some small adaptions are
necessary to make it compile. I'm not really into that stuff, but I
think posting your error message should be sufficient.

And even if it's not GCC's fault, it doesn't hurt to report this
problem.

Kind regards,

So, I would appreciate if you would peruse these error messages and see
if you see any reason for me to file a report against FC5's gcc:
---------------------------------------------------------------------------------------------------------
-- digiKamImagePlugins configure results --------
-- digiKam found.................. YES
-------------------------------------------------
digikamimageplugins/filmgrain/Makefile.am: rest $(all_includes) $(LIBDIGIKAM_CFLAGS)

compiling /home/kdefc5/CVS/KDE-SVN/extragear/graphics/digikam/libs/dmetadata/loaders/dmetaloader.cpp
g++ -DHAVE_CONFIG_H -I./digikam/libs/dmetadata/loaders -I/home/kdefc5/CVS/KDE-SVN/extragear/graphics/digikam/libs/dmetadata/loaders -I. -I/home/kdefc5/CVS/KDE-SVN/extragear/graphics/digikam/libs/dmetadata -I/home/kdefc5/CVS/KDE-SVN/extragear/graphics/digikam/libs/dimg -I/home/kdefc5/CVS/KDE-SVN/extragear/graphics/digikam/digikam -I/usr/local/kde-svn-fc5/include -I/usr/local/qt-src/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -g3 -fno-inline -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_CLEAN_NAMESPACE -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -fexceptions -fPIC -!
DPIC -c /home/kdefc5/CVS/KDE-SVN/extragear/graphics/digikam/libs/dmetadata/loaders/dmetaloader.cpp -o ./digikam/libs/dmetadata/loaders/.libs/dmetaloader.o -Wp,-MD,./digikam/libs/dmetadata/loaders/.deps/dmetaloader.TUlo
/home/kdefc5/CVS/KDE-SVN/extragear/graphics/digikam/libs/dimg/dcolor.h:63: error: extra qualification ‘Digikam::DColor::’ on member ‘setColor’
/home/kdefc5/CVS/KDE-SVN/extragear/graphics/digikam/libs/dimg/dcolor.h:70: error: extra qualification ‘Digikam::DColor::’ on member ‘setPixel’
Error creating ./digikam/libs/dmetadata/loaders/dmetaloader.lo. Exit status 1.
---------------------------------------------------------------------------------------------------------

---------------------------------------------------------------------------------------------------------
compiling /home/kdefc5/CVS/KDE-SVN/extragear/multimedia/kaffeine/src/input/dvb/dvbevents.cpp
g++ -DHAVE_CONFIG_H -I./kaffeine/src/input/dvb
-I/home/kdefc5/CVS/KDE-SVN/extragear/multimedia/kaffeine/src/input/dvb
-I. -I/home/kdefc5/CVS/KDE-SVN/extragear/multimedia/kaffeine/src/input/
-I/usr/local/kde-svn-fc5/include -I/usr/local/qt-src/include -I.
-DQT_THREAD_SUPPORT -D_REENTRANT -Wno-long-long -Wundef -ansi
-D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion
-Wchar-subscripts -Wall -W -Wpointer-arith -g3 -fno-inline
-Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor
-fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE
-DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION
-DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT
-DQT_NO_TRANSLATION -fPIC -DPIC
-c /home/kdefc5/CVS/KDE-SVN/extragear/multimedia/kaffeine/src/input/dvb/dvbevents.cpp
-o ./kaffeine/src/input/dvb/.libs/dvbevents.o
-Wp,-MD,./kaffeine/src/input/dvb/.deps/dvbevents.TUlo /usr/include/linux/dvb/dmx.h:165:
error: ‘__u64’ does not name a type Error
creating ./kaffeine/src/input/dvb/dvbevents.lo. Exit status 1.
---------------------------------------------------------------------------------------------------------

So if any of you see any reason for me to report this against FC5's gcc
4, I would love to know. I will ask you for the same information that
I asked the guy on the KDE for:
1. Description of problem:
2. How reproducible:
3. Steps to Reproduce:
4. Actual results:
5. Expected results:

Have a Great Day,
Steven P. Ulrick

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages

  • Re: Function call before main.
    ... he said compiling it in gcc gave him the error message ... Isn't it just as valid to say "I was cooking dinner, ...
    (comp.lang.c)
  • Re: Function call before main.
    ... Kenneth Brody said: ... he said compiling it in gcc gave him the error message ...
    (comp.lang.c)
  • Re: KDE blacklist of Fedora Cores gcc 4
    ... Rahul Sundaram wrote: ... >>the root of each KDE module? ... > Well I havent had the oppurtunity to try compiling a large beast like ... email should be considered my personal feelings on gcc 4, ...
    (Fedora)
  • [PATCH] drm: Fixes error with gcc 3.3.5 in i915 driver.
    ... When compiling with gcc 3.3.5 I got the following error message in the ... This error did not occur when compiling the same code in gcc 4.3.2. ... More majordomo info at http://vger.kernel.org/majordomo-info.html ...
    (Linux-Kernel)
  • Re: Possible issues with FC5s gcc
    ... I have been getting while compiling certain KDE modules from their SVN ... It's a bug in the code, not gcc. ... think posting your error message should be sufficient. ...
    (Fedora)