From: Igor Grinberg <grinberg@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [Almost solved] M5282EVB undefined reference to `environment'
Date: Wed, 30 Nov 2011 08:58:30 +0200 [thread overview]
Message-ID: <4ED5D416.1070709@compulab.co.il> (raw)
In-Reply-To: <4ED563B3.1080107@inchipdesign.com.au>
On 11/30/11 00:58, James Steward wrote:
> On 25/11/11 14:52, James Steward wrote:
>
>> So it compiles env_embedded.c, but doesn't include it in libcommon.o?
>>
>> <hack>
>> vim common/Makefile
>>
>> XCOBJS-$(CONFIG_ENV_IS_IN_FLASH) += env_embedded.o
>>
>> becomes
>>
>> COBJS-$(CONFIG_ENV_IS_IN_FLASH) += env_embedded.o
>>
>> :q
>> </hack>
>>
>> make all
>>
>> Hey, presto, build now completes!
>>
>> So how should this be corrected properly?
>
> Can anyone suggest how the build process should be fixed?
I don't fully understand the logic behind what's done
to have ENV_IS_EMBEDDED, as it is used mostly on architectures
I haven't worked with (at least till now).
So, probably, I will not be the right person to ask...
My suggestion would be to look into those linker scripts,
Wolfgang mentioned in one of the previous emails and if you think
it should be done in some different way, send a patch and start
a discussion. But, really, I'm not the right person to ask...
--
Regards,
Igor.
next prev parent reply other threads:[~2011-11-30 6:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 22:00 [U-Boot] M5282EVB undefined reference to `environment' James Steward
2011-11-22 4:51 ` Marek Vasut
2011-11-22 5:22 ` James Steward
2011-11-23 12:19 ` Igor Grinberg
2011-11-23 23:58 ` James Steward
2011-11-24 6:36 ` Igor Grinberg
2011-11-24 23:27 ` James Steward
2011-11-25 5:42 ` Wolfgang Denk
2011-11-25 3:52 ` [U-Boot] [Almost solved] " James Steward
2011-11-29 22:58 ` James Steward
2011-11-30 6:58 ` Igor Grinberg [this message]
2011-11-30 21:10 ` James Steward
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=4ED5D416.1070709@compulab.co.il \
--to=grinberg@compulab.co.il \
--cc=u-boot@lists.denx.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