From: Ismail Donmez <ismail@pardus.org.tr>
To: David Miller <davem@davemloft.net>
Cc: akpm@osdl.org, netdev@vger.kernel.org,
bugme-daemon@bugzilla.kernel.org, uberlord@gentoo.org,
linux-kernel@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 7724] New: asm/types.h should define __u64 if isoc99
Date: Thu, 21 Dec 2006 23:03:15 +0200 [thread overview]
Message-ID: <200612212303.16136.ismail@pardus.org.tr> (raw)
In-Reply-To: <20061221.125850.125884789.davem@davemloft.net>
21 Ara 2006 Per 22:58 tarihinde, David Miller şunları yazmıştı:
> From: Andrew Morton <akpm@osdl.org>
> Date: Thu, 21 Dec 2006 12:49:54 -0800
>
> > > Summary: asm/types.h should define __u64 if isoc99
>
> Platform specific bug, and has nothing to do with networking.
>
> This problem will occur with any user visible interface definition
> that uses __u64, and there are several both in and outside the
> networking.
This bug hit KDE modules (kdebase/kdemultimedia/kdetv/...) many times, I
workarounded with #undef ing __STRICT_ANSI__ before including kernel headers
which is well ugly but works.
> x86 and perhaps others protect the __u64 definition with:
>
> defined(__GNUC__) && !defined(__STRICT_ANSI__)
>
> for whatever reason, probably to avoid "long long" or something like
> that. But even that theory makes no sense.
Indeed this restriction just breaks userspace apps.
Regards,
ismail
--
Bir gün yolda yürüyordum... Bir şarkı duydum... Kalbim acıdı... Bu kadar...
prev parent reply other threads:[~2006-12-21 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200612211617.kBLGHAAg028181@fire-2.osdl.org>
[not found] ` <20061221124954.6bb415e9.akpm@osdl.org>
2006-12-21 20:58 ` David Miller
2006-12-21 21:03 ` Ismail Donmez [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=200612212303.16136.ismail@pardus.org.tr \
--to=ismail@pardus.org.tr \
--cc=akpm@osdl.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=uberlord@gentoo.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
all inboxes | Powered by JetHome®