All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Derek Nielson <dereknielson@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Best place to ask this question: error with compiler.h when switching from 2.6.32 to 2.6.36
Date: Mon, 22 Nov 2010 13:12:59 -0500	[thread overview]
Message-ID: <9466.1290449579@localhost> (raw)
In-Reply-To: Your message of "Mon, 22 Nov 2010 09:55:14 MST." <AANLkTikt2k8jC4ykYqYG_hQPAZt0-GXAvD1DPogu+AB0@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 962 bytes --]

On Mon, 22 Nov 2010 09:55:14 MST, Derek Nielson said:

> In file included from include/linux/string.h:10,
>                  from
> /mnt/local/home/linux-omap-2.6/arch/arm/include/asm/uaccess.h:14,
>                  from /home/my_module/my_module.c:24:
> include/linux/compiler.h:62: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘struct’
> make[2]: *** [/home/my_module/my_module.o] Error 1
> make[1]: *** [_module_/home/my_module] Error 2
> make[1]: Leaving directory `/mnt/local/home/linux-omap-2.6'
> make: *** [release] Error 2

> I found this thread http://lkml.org/lkml/2007/10/17/213 and tried
> following their solution but it didn't fix the problem.
> 
> Does anyone know how to fix this error?

What does 'gcc -v' say?  And can you give the entire 'make' command that
you issued to do the build?

Other likely possibility is that you haven't done a 'make <something>config' in the
2.6.36 directory tree.



[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

      parent reply	other threads:[~2010-11-22 18:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22 16:55 Best place to ask this question: error with compiler.h when switching from 2.6.32 to 2.6.36 Derek Nielson
2010-11-22 17:35 ` Bruno Prémont
2010-11-22 22:37   ` Derek Nielson
2010-11-22 18:12 ` Valdis.Kletnieks [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=9466.1290449579@localhost \
    --to=valdis.kletnieks@vt.edu \
    --cc=dereknielson@gmail.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 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.