[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#232107: linux-kernel-headers: linux/videodev2.h:432 gives syntax errors with gcc-3.2 and 3.3



On Wednesday 11 February 2004 03:49, GOTO Masanori wrote:
> At Wed, 11 Feb 2004 00:23:07 +0100,
> Achim Bohnet wrote:
> > > I bet this is another of those g++ -ansi -pedantic programs.  That
> > > causes Linux headers not to define u64 - correctly, because in strict
> > > ANSI mode 64-bit integers are not required to be supported.  I have no
> > > idea how you expect to use an interface with 64-bit data members in a
> > > compilation mode which does not support 64-bit numbers without a
> > > warning.
> > 
> > I've tried:
> > 	o removing only -pedantic:  does not help
> > 	o removing only -ansi	: stuff compiles
> > 
> > Stupid as I am I've no idea if ISO C++ has to define 64 bit data types
> > or not but at least I know how to fix it ;)
> > 
> > I'll try to figure out the origin of -ansi in CXXFLAGS in
> > all the auto* tools generated files, remove it remove it and
> > send the patch to the upstream author of konference.
> 
> Thanks for your checking.  Could you or can I close this bug, or
> reassign other packages? (I didn't find konference package)

Konference author [cc] confirmed that pwlib/openh323 has no problems
with kernel 2.4 headers but obviously with kernel 2.5/2.6 headers.

Because I'm no C/C++ Standard expert I would like that you
decide what the most appropiate pkg for reassignment:
		kdelibs4-dev
		libpt-dev

Below some more information:

Konference is not in debian yet (in case I like the apps I plan
to pkg it ;)  You can find konference at:

	http://www.kde-apps.org/content/show.php?content=10395
and
	https://developer.berlios.de/projects/konference/


But _all_ KDE apps should suffer from this problem because
the only file with -ansi and -pedantic is after a clean cvs
checkout:

allee(0) ~/src/konference/cvs/head $ tcgrep -re '-ansi|-pedantic' .
./admin/acinclude.m4.in:CXXFLAGS="$CXXFLAGS -pedantic-errors"
./admin/acinclude.m4.in:        CXXFLAGS="+K0 -Wall -pedantic -W -Wpointer-arith -Wwrite-strings $CXXFLAGS"
./admin/acinclude.m4.in:            CFLAGS="-ansi -W -Wall -pedantic -Wchar-subscripts -Wshadow -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -D_XOPEN_SOURCE=500 -D_BSD_SOURCE $CFLAGS"
./admin/acinclude.m4.in:            CXXFLAGS="-ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts $CXXFLAGS"
                                              ^^^^^
./admin/acinclude.m4.in:        CXXFLAGS="-Wall -pedantic -W -Wpointer-arith -Wwrite-strings $CXXFLAGS"


This file comes from the KDE CVS module kde-common/admin.  _All_ kde apps
I know use a copy of the kde-common/admin build environment.  Here's the
relevant code snippet:

...
  if test "$kde_use_warnings" = "yes"; then
      if test "$GCC" = "yes"; then
        case $host in
          *-*-linux-gnu)
            CFLAGS="-ansi -W -Wall -pedantic -Wchar-subscripts -Wshadow -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -D_XOPEN_SOURCE=500 -D_BSD_SOURCE $CFLAGS"
            CXXFLAGS="-ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts $CXXFLAGS"
                      ^^^^^
            KDE_CHECK_COMPILER_FLAG(Wmissing-format-attribute, [CXXFLAGS="$CXXFLAGS -Wformat-security -Wmissing-format-attribute"; CFLAGS="$CFLAGS -Wformat-security -Wmissing-format-attribute"])

          ;;
        esac
        CXXFLAGS="-Wall -pedantic -W -Wpointer-arith -Wwrite-strings $CXXFLAGS"
        KDE_CHECK_COMPILER_FLAG(Wundef,[CXXFLAGS="-Wundef $CXXFLAGS"])
        KDE_CHECK_COMPILER_FLAG(Wno-long-long,[CXXFLAGS="-Wno-long-long $CXXFLAGS"])
        KDE_CHECK_COMPILER_FLAG(Wnon-virtual-dtor,[CXXFLAGS="-Wnon-virtual-dtor $CXXFLAGS"])
     fi
  fi
...

> 
> Regards,
> -- gotom
> 
> 
> 
> 

-- 
  To me vi is Zen.  To use vi is to practice zen. Every command is
  a koan. Profound to the user, unintelligible to the uninitiated.
  You discover truth everytime you use it.
                                      -- reddy@lion.austin.ibm.com



Reply to: