public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Arnd Bergmann <arndbergmann@googlemail.com>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: include/asm-generic/int-ll64.h kernel 2.6.31.4
Date: Thu, 22 Oct 2009 18:21:06 +0200	[thread overview]
Message-ID: <20091022182106.3bdf7b5d.skraw@ithnet.com> (raw)
In-Reply-To: <200910221629.59818.arnd@arndb.de>

On Thu, 22 Oct 2009 16:29:59 +0200
Arnd Bergmann <arndbergmann@googlemail.com> wrote:

> On Tuesday 20 October 2009, Stephan von Krawczynski wrote:
> > I lately compiled some app that stumbled across this, and someone smarter than
> > me should judge if this is right or wrong:
> > 
> > 
> > * asm-generic/int-ll64.h
> >  *
> >  * Integer declarations for architectures which use "long long"
> >  * for 64-bit types.
> >  */
> > 
> > #ifndef _ASM_GENERIC_INT_LL64_H
> > #define _ASM_GENERIC_INT_LL64_H
> > 
> > #include <asm/bitsperlong.h>
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > 
> > 
> > Is it correct to include from linked "asm" instead of asm-generic ?
> > 
> > My link goes to "asm-x86" but for some reason asm-generic/types.h is included
> > which ends at int-ll64.h trying to include a not existing bitsperlong.h from
> > directory asm-x86.
> 
> Hi Stephan,
> 
> Most likely you are using the kernel headers in an unsupported way, like
> trying to point to $(HOME)/linux-2.6/include for include files when building
> an application.
> 
> Please see http://kernelnewbies.org/KernelHeaders for how to fix that.
> 
> 	Arnd <><

I am the wrong person to tell that, the story belongs to keepalived.
Nevertheless reading other header files in the same dir makes me think that
pointing to "asm" instead of "asm-generic" looks flakey, or why do others
point to -generic then?

-- 
Regards,
Stephan

  reply	other threads:[~2009-10-22 16:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-20 13:43 include/asm-generic/int-ll64.h kernel 2.6.31.4 Stephan von Krawczynski
2009-10-22 14:29 ` Arnd Bergmann
2009-10-22 16:21   ` Stephan von Krawczynski [this message]
2009-10-22 18:38     ` Sam Ravnborg

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=20091022182106.3bdf7b5d.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=arndbergmann@googlemail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox