All of lore.kernel.org
 help / color / mirror / Atom feed
From: simon schuler <simon.schuler@gmx.ch>
To: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: [PATCH] Fix linux/types.h for compiling with -ansi
Date: Sat, 27 Nov 2004 18:24:51 +0000	[thread overview]
Message-ID: <41A8C673.7050007@gmx.ch> (raw)

I've got a symple little patch to apply:
when including <linux/types.h> in a program and compiling with 'gcc 
-ansi' gcc complains:
`In file included from test.c:1:
/usr/include/linux/types.h:162: error: parse error before "__le64"
/usr/include/linux/types.h:163: error: parse error before "__be64"`

These lines are:
typedef __u64 __bitwise __le64;
typedef __u64 __bitwise __be64;

__u64 isn't defined in include/asm-386/types.h when __STRICT_ANSI__ is 
defined (as always when calling gcc -ansi):
#if defined(__GNUC__) && !defined(__STRICT_ANSI__)
typedef __signed__ long long __s64;
typedef unsigned long long __u64;
#endif

The following patch for linux-2.6.10-rc2 solves the problem:
(The patch wouldn't be needed for some 64Bit architectures, but i didn't 
find an easy way of sorting these out)

diff -up include/linux/types.h include/linux/newtypes.h
--- include/linux/types.h        2004-11-27 17:19:25.509948024 +0000
+++ include/linux/types.h_new     2004-11-27 17:24:18.630386944 +0000
@@ -157,8 +157,10 @@ typedef __u16 __bitwise __le16;
 typedef __u16 __bitwise __be16;
 typedef __u32 __bitwise __le32;
 typedef __u32 __bitwise __be32;
+#if defined(__GNUC__) && !defined(__STRICT_ANSI__)
 typedef __u64 __bitwise __le64;
 typedef __u64 __bitwise __be64;
+#endif

 struct ustat {
        __kernel_daddr_t        f_tfree;


                 reply	other threads:[~2004-11-27  6:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=41A8C673.7050007@gmx.ch \
    --to=simon.schuler@gmx.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@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 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.