From: Dirk Behme <dirk.behme@googlemail.com>
To: "Hunter, Jon" <jon-hunter@ti.com>, Kevin Hilman <khilman@deeprooted.net>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Build error with latest GIT tree
Date: Wed, 12 Jul 2006 07:06:54 +0200 [thread overview]
Message-ID: <44B4836E.1080203@gmail.com> (raw)
In-Reply-To: <C51F43ABFC95844490F0529B60753BF4055F32C0@dlee02.ent.ti.com>
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.
For me, recent git compiles okay regarding this for OSK.
Seems that I use
# CONFIG_OMAP_RESET_CLOCKS is not set
and therefore the failing part isn't used by me.
Kevin, any idea? Do we have to readd
extern struct list_head clocks;
if CONFIG_OMAP_RESET_CLOCKS is enabled?
Jon: Try to disable CONFIG_OMAP_RESET_CLOCKS for the moment.
Regards
Dirk
>>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 5:06 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 [this message]
2006-07-12 14:11 ` Kevin Hilman
-- 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=44B4836E.1080203@gmail.com \
--to=dirk.behme@googlemail.com \
--cc=jon-hunter@ti.com \
--cc=khilman@deeprooted.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox