From: Thomas Weber <thomas.weber.linux@googlemail.com>
To: "Nori, Sekhar" <nsekhar@ti.com>
Cc: Thomas Weber <weber@corscience.de>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>,
Russell King <linux@arm.linux.org.uk>
Subject: Re: [RFC/PATCH] ARM: OMAP: Fix build for OMAP3 only builds
Date: Wed, 02 Nov 2011 13:37:31 +0100 [thread overview]
Message-ID: <4EB1398B.80901@gmail.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB5930328C7C406@dbde02.ent.ti.com>
Am 27.10.2011 07:32, schrieb Nori, Sekhar:
> On Wed, Oct 12, 2011 at 17:33:56, Thomas Weber wrote:
>> When building for OMAP3 only I get the
>> following errors:
>>
>> In function `omap2420_init_early':
>> undefined reference to `omap2_set_globals_242x'
>> undefined reference to `omap2xxx_voltagedomains_init'
>> undefined reference to `omap242x_powerdomains_init'
>> undefined reference to `omap242x_clockdomains_init'
>> undefined reference to `omap2420_hwmod_init'
>>
>> In function `omap2430_init_early':
>> undefined reference to `omap2_set_globals_243x'
>> undefined reference to `omap2xxx_voltagedomains_init'
>> undefined reference to `omap243x_powerdomains_init'
>> undefined reference to `omap243x_clockdomains_init'
>> undefined reference to `omap2430_hwmod_init'
>>
>> In function `omap4430_init_early':
>> undefined reference to `omap2_set_globals_443x'
>> undefined reference to `omap44xx_voltagedomains_init'
>> undefined reference to `omap44xx_powerdomains_init'
>> undefined reference to `omap44xx_clockdomains_init'
>> undefined reference to `omap44xx_hwmod_init'
>> undefined reference to `omap4xxx_clk_init'
>>
>> With this patch the omapXXXX_init_early will be compiled only
>> when their SOC's are selected.
>>
>> Signed-off-by: Thomas Weber <weber@corscience.de>
>
> I was facing the same problem and this patch helped
> me get rid of it.
>
> Tested-by: Sekhar Nori <nsekhar@ti.com>
>
> Thanks,
> Sekhar
>
> --
Hello Tony,
what is the status of this patch?
There is also another patch fixing the same problem.
[PATCH v2] arm: omap: Fix errors and warnings when building for one board
Thomas
next prev parent reply other threads:[~2011-11-02 11:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 12:03 [RFC/PATCH] ARM: OMAP: Fix build for OMAP3 only builds Thomas Weber
2011-10-27 5:32 ` Nori, Sekhar
2011-11-02 12:37 ` Thomas Weber [this message]
2011-11-02 17:16 ` Tony Lindgren
2011-11-03 18:30 ` Tony Lindgren
2011-11-03 21:24 ` Thomas Weber
2011-11-07 17:06 ` Russell King - ARM Linux
2011-11-07 17:29 ` Tony Lindgren
-- strict thread matches above, loose matches on Subject: below --
2011-10-29 4:42 Thomas Weber
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=4EB1398B.80901@gmail.com \
--to=thomas.weber.linux@googlemail.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nsekhar@ti.com \
--cc=tony@atomide.com \
--cc=weber@corscience.de \
/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