All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Ram <vshrirama@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel compilation - errors
Date: Mon, 8 Jan 2007 12:28:59 -0800	[thread overview]
Message-ID: <20070108202858.GA28406@atomide.com> (raw)
In-Reply-To: <8bf247760701080518s3f58f5aax4250bca4a43e9d59@mail.gmail.com>

Hi,

* Ram <vshrirama@gmail.com> [070108 05:18]:
> Hi,
>   Im using linux-2.6.14-omap2430.
> 
>   Im using TI omap 2430 SDP.
> 
>   When i compile it with the eldk toolchain.
> 
>   I get an error listed at the end of this mail.
> 
>  The error is simple - case values should be constants, However, the
> toolchain gcc 4.0
>  is complaining that case values are not constant.
> 
>  Actually, the some of the case values are defined as -
> 
>  case (u32)&CM_ICLKEN_WKUP:
>  case (u32)&CM_FCLKEN_WKUP:
> 
> However, the same code compiles with some other compilers (lower
> versions of gcc).
> 
>  I think all compilers should give the same error
> 
>  Why the difference in behaviour?.
> 
> Not sure, if the source located at linux.omap.com/pub is broken.
> Couldnt find the sources of linux kernel for omap2430 with higher
> versions of the linux kernel higher than 2.6.14.

Sounds like you're using TI's tree. In that case please contact TI for
support.

If you want to use the current git tree, please see:

http://www.kernel.org/git/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=summary

and

http://muru.com/linux/omap

Only minimal 2340 code is currently merged in the linux-omap git tree,
so YMMV.

Regards,

Tony

  reply	other threads:[~2007-01-08 20:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-08 13:18 kernel compilation - errors Ram
2007-01-08 20:28 ` Tony Lindgren [this message]
2007-01-08 20:43 ` Jan Engelhardt

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=20070108202858.GA28406@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vshrirama@gmail.com \
    /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.