From: Martin Schlemmer <azarah@nosferatu.za.org>
To: MALET JL <malet.jean-luc@laposte.net>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>
Subject: Re: [linux 2.6.3] [gcc 3.3.3] compile errors
Date: Mon, 23 Feb 2004 22:52:20 +0200 [thread overview]
Message-ID: <1077569540.19268.13.camel@nosferatu.lan> (raw)
In-Reply-To: <403A2ADB.9040002@laposte.net>
[-- Attachment #1: Type: text/plain, Size: 1934 bytes --]
On Mon, 2004-02-23 at 18:31, MALET JL wrote:
> Randy.Dunlap a écrit :
>
> >On Sun, 22 Feb 2004 21:31:47 +0100 mjl <malet.jean-luc@laposte.net> wrote:
> >
> >| hello please cc me since I'm not a member
> >| all my builds fails with this error
> >|
> >| In file included from ../include/swab.h:20,
> >| from ../include/misc.h:12,
> >| from io.c:21:
> >| /usr/include/linux/byteorder/swab.h:133: error: syntax error before "__u16"
> >| /usr/include/linux/byteorder/swab.h:146: error: syntax error before "__u32"
> >
> >You are using userspace headers for building the kernel.
> >Maybe you have a symbolic link from linux/include/asm to the
> >userspace headers. If so, Don't Do That.
> >In any case, don't use userspace headers to build the kernel.
> >
> >
> the problem is that this is a part of compile log from a userspace
> program....... I builded the kernel right but can't compile some
> userspace programs (such as Mplayer, linux-utils.....)
> the configuration I use :
> copy from /usr/src/linux/include/asm to /usr/include/asm
> copy from /usr/src/linux/include/asm-generic to /usr/include/asm-generic
> copy from /usr/src/linux/include/linux to /usr/include/linux
>
> is this wrong ? I've done this all the time (since 2.4.2 kernel) without
> problem..... if i'm wrong please correct my behaviour
>
Just edit offending files and take out the '__attribute_const__'s - I am
guessing you tried to compile cdrtools ... =)
> >
> >| make[1]: *** [io.o] Error 1
> >| make[1]: Leaving directory `/usr/src/sorcery/reiserfsprogs-3.6.13/lib'
> >| make: *** [all-recursive] Error 1
> >|
> >|
> >| I looked into the source and the line is
> >|
> >|
> >| static __inline__ __attribute_const__ __u16 __fswab16(__u16 x)
> >| {
> >|
> >|
> >| which don't looks bad ......
> >
> >
> >
> >--
> >~Randy
> >
> >
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-02-23 20:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-22 20:31 [linux 2.6.3] [gcc 3.3.3] compile errors mjl
2004-02-23 15:42 ` Randy.Dunlap
2004-02-23 16:31 ` MALET JL
2004-02-23 16:58 ` Chris Lingard
2004-02-24 8:42 ` MALET JL
2004-02-24 10:46 ` [linux 2.6.3] [gcc 3.3.3] compile errors. Now OT Chris Lingard
2004-02-23 20:52 ` Martin Schlemmer [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=1077569540.19268.13.camel@nosferatu.lan \
--to=azarah@nosferatu.za.org \
--cc=linux-kernel@vger.kernel.org \
--cc=malet.jean-luc@laposte.net \
--cc=rddunlap@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox