From: Con Kolivas <kernel@kolivas.org>
To: Boris <boris@boris.ca>, linux-kernel@vger.kernel.org
Subject: Re: [2.4.21rc8] possible header problems[byteorder.h/swab.h]
Date: Thu, 12 Jun 2003 13:13:49 +1000 [thread overview]
Message-ID: <200306121313.49440.kernel@kolivas.org> (raw)
In-Reply-To: <002101c3308e$5580cea0$43444218@raiden>
On Thu, 12 Jun 2003 12:57, Boris wrote:
> I am running 2.4.21rc8 with gcc 3.3 and it seems that after the 2.4.20
> kernel, I can't compile kde anymore. I have written a message to the kde
> mailing list and they suggest its a kernel problem. Heres an example.
>
> make[5]: Leaving directory `/tmp/kdemultimedia/mpeglib/lib/util'
>
> > make[4]: Leaving directory `/tmp/kdemultimedia/mpeglib/lib/util'
> > Making all in input
> > make[4]: Entering directory `/tmp/kdemultimedia/mpeglib/lib/input'
> > if /bin/sh ../../../libtool --silent --mode=compile --tag=CXX g++
> > -DHAVE_CONFIG_H -I. -I. -I../../.. -I/opt/kde/include
> > -I/usr/lib/qt/include -I/usr/X11R6/include -DQT_THREAD_SUPPORT
> > -D_REENTRANT -Wnon-virtual-dtor -Wno-long-long -Wundef -Wall -pedantic
> > -W -Wpointer-arith -Wwrite-strings -ansi -D_XOPEN_SOURCE=500
> > -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -DNDEBUG
> > -DNO_DEBUG -O2 -Wformat-security -Wmissing-format-attribute
> > -fno-exceptions
> > -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST
> > -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT cdromAccess.lo -MD
> > -MP -MF ".deps/cdromAccess.Tpo" \
> > -c -o cdromAccess.lo `test -f 'cdromAccess.cpp' || echo
> > './'`cdromAccess.cpp; \
> > then mv -f ".deps/cdromAccess.Tpo" ".deps/cdromAccess.Plo"; \
> > else rm -f ".deps/cdromAccess.Tpo"; exit 1; \
> > fi
> > In file included from /usr/include/linux/cdrom.h:14,
> > from cdromAccess_Linux.cpp:17,
> > from cdromAccess.cpp:30:
> > /usr/include/asm/byteorder.h:38: error: syntax error before `(' token
> > /usr/include/asm/byteorder.h:42: error: '__u64' is used as a type, but is
> > not
> > defined as a type.
> > /usr/include/asm/byteorder.h:43: error: parse error before `}' token
> > /usr/include/asm/byteorder.h:44: error: syntax error before `.' token
> > /usr/include/asm/byteorder.h:50: error: syntax error before `.' token
> > /usr/include/asm/byteorder.h:51: error: syntax error before `.' token
> > /usr/include/asm/byteorder.h:52: error: parse error before `:' token
> > In file included from /usr/include/linux/byteorder/little_endian.h:11,
> > from /usr/include/asm/byteorder.h:65,
> > from /usr/include/linux/cdrom.h:14,
> > from cdromAccess_Linux.cpp:17,
> > from cdromAccess.cpp:30:
> > /usr/include/linux/byteorder/swab.h:199: error: syntax error before `('
> > token /usr/include/linux/byteorder/swab.h:209: error: syntax error before
> > `(' token /usr/include/linux/byteorder/swab.h:213: error: `__u64' was not
> > declared in this scope
> > /usr/include/linux/byteorder/swab.h:213: error: `addr' was not declared
> > in this scope
> > /usr/include/linux/byteorder/swab.h:214: error: variable or field
> > `__swab64s'
> > declared void
> > /usr/include/linux/byteorder/swab.h:214: error: `__swab64s' declared as
> > an `inline' variable
> > /usr/include/linux/byteorder/swab.h:214: error: syntax error before `{'
> > token make[4]: *** [cdromAccess.lo] Error 1
> > make[4]: Leaving directory `/tmp/kdemultimedia/mpeglib/lib/input'
> > make[3]: *** [all-recursive] Error 1
> > make[3]: Leaving directory `/tmp/kdemultimedia/mpeglib/lib'
> > make[2]: *** [all-recursive] Error 1
> > make[2]: Leaving directory `/tmp/kdemultimedia/mpeglib'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/tmp/kdemultimedia'
> > make: *** [all] Error 2
Read this about kernel headers please:
http://www.kernelnewbies.org/faq/index.php3#headers
Con
prev parent reply other threads:[~2003-06-12 3:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 2:57 [2.4.21rc8] possible header problems[byteorder.h/swab.h] Boris
2003-06-12 3:13 ` Con Kolivas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200306121313.49440.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=boris@boris.ca \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.