From: Kevin Hilman <khilman@deeprooted.net>
To: "Hunter, Jon" <jon-hunter@ti.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: RE: Build error with latest GIT tree
Date: Wed, 12 Jul 2006 09:11:01 -0500 [thread overview]
Message-ID: <1152713461.12527.57.camel@vence.internal.net> (raw)
In-Reply-To: <C51F43ABFC95844490F0529B60753BF4055F32C0@dlee02.ent.ti.com>
This was caused by a cleanup I did for gcc4 compatability and I
admittedly did not test w/CONFIG_OMAP_RESET_CLOCKS. Oops.
I've pushd a fix for this and compile tested for gcc3 and gcc4, with and
without CONFIG_OMAP_RESET_CLODKS.
http://source.mvista.com/git/gitweb.cgi?p=linux-omap-2.6.git;a=commit;h=64929d882591a213cb51407992f28c42121b2f7d
Kevin
On Tue, 2006-07-11 at 11:11 -0500, Hunter, Jon wrote:
> I did a diff between the clock.h file in the include/asm/arch/ directory
> and found the following differences between v2.6.17 and v2.6.17-rc6
> (which I belive is the latest);
>
> --- include/asm/arch/clock.h 2006-07-11 10:45:46.000000000 -0500
> +++ ../linux-omap-2.6.git/include/asm/arch/clock.h 2006-07-10
> 16:34:40.000000000 -0500
> @@ -48,8 +48,6 @@
> };
>
> extern unsigned int mpurate;
> -extern struct list_head clocks;
> -extern spinlock_t clockfw_lock;
>
> I believe the removal of "clocks" variable is why the compiler is
> complaining below. Let me know if you have any thoughts.
>
> Cheers,
> Jon
>
>
>
> > Is anyone seeing the following build error with the latest GIT tree?
> > Seemed similar to the following issue, but the exact error looks
> > different:
> > http://linux.omap.com/pipermail/linux-omap-open-source/2006-Ju
> > ne/007473.
> > html
> >
> >
> > CC arch/arm/mach-omap1/clock.o
> > arch/arm/mach-omap1/clock.c: In function `omap1_late_clk_reset':
> > arch/arm/mach-omap1/clock.c:609: error: `clocks' undeclared
> > (first use in this function)
> > arch/arm/mach-omap1/clock.c:609: error: (Each undeclared
> > identifier is reported only once
> > arch/arm/mach-omap1/clock.c:609: error: for each function it appears
> > in.)
> > make[1]: *** [arch/arm/mach-omap1/clock.o] Error 1
> > make: *** [arch/arm/mach-omap1] Error 2
> >
> > Cheers,
> > Jon
> > _______________________________________________
> > Linux-omap-open-source mailing list
> > Linux-omap-open-source@linux.omap.com
> > http://linux.omap.com/mailman/listinfo/linux-omap-open-source
> >
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
next prev parent reply other threads:[~2006-07-12 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 16:11 Build error with latest GIT tree Hunter, Jon
2006-07-12 5:06 ` Dirk Behme
2006-07-12 14:11 ` Kevin Hilman [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-11 14:57 Hunter, Jon
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=1152713461.12527.57.camel@vence.internal.net \
--to=khilman@deeprooted.net \
--cc=jon-hunter@ti.com \
--cc=linux-omap-open-source@linux.omap.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.