Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Stefan Müller-Klieser" <s.mueller-klieser@phytec.de>
To: Marek Vasut <marex@denx.de>, Denys Dmytriyenko <denis@denix.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/4] u-boot: Update to 2016.09.01 release
Date: Thu, 27 Oct 2016 13:44:25 +0200	[thread overview]
Message-ID: <5811E899.6050000@phytec.de> (raw)
In-Reply-To: <83c5347a-3962-7b3b-30d3-d5ee876fc2aa@denx.de>

On 25.10.2016 21:24, Marek Vasut wrote:
> On 10/25/2016 08:32 PM, Denys Dmytriyenko wrote:
>> On Sat, Oct 22, 2016 at 10:32:12PM +0200, Marek Vasut wrote:
>>> On 10/21/2016 09:47 AM, Burton, Ross wrote:
>>>
>>> Hi!
>>>
>>>> On 20 October 2016 at 14:35, Marek Vasut <marex@denx.de
>>>> <mailto:marex@denx.de>> wrote:
>>>>
>>>>     Upgrade U-Boot to the latest version.
>>>>
>>>>
>>>> As usual, u-boot-mkimage broke again:
>>>
>>> That's weird, I successfully built it for nios2 during my tests.
>>> Can you tell me how I can replicate the issue , so I can test for it to
>>> prevent regression and roll out a patch ?
>>
>> Marek, Ross,
>>
>> Any progress on this? Need any help testing?
>>
> Yeah, how do you replicate this issue ?
> 
Hi!
I am just looking at a similar problem and want to jump into the discussion.
As Ross said, the problem is to not respect host/target -- cc/cflags/ldflags.
So to replicate the issue, you can use a bare minimum build host with no
cross toolchain installed, and I guess all targets will fail to build.
As this has been broken so many times, I want to discuss some possible fixes:
In the top level Makefile we have:
HOSTCC = cc
HOSTCFLAGS = ...
The problem is, you cannot properly override those variables, as they get used
a lot to do different things, e.g. in tools/Makefile we have (for cross tools
target) HOSTCC = $(CC) and for HOSTCFLAGS we have appends for configuration. 
Thats why we have the current workaround with a squashed override. I see many
possible solutions and would like to hear your opinion:
1. Make top level Makefile HOST assignments conditional "?="
   - easy
   - will probably not be accepted upstream
2. add "override" to appends in sublevel Makefiles
   - adds complexity/one level of override hierarchy
3. Don't use appends for those variables (like in the kernel Makefile), overrides
   in the recipe
   - clean
   - quite some rework in uboot
4. Hack around in the recipe with class overrides and exports
   - quickfix, no patch required
   - fails easily in the future

Any thoughts?
Stefan


  reply	other threads:[~2016-10-27 11:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-20 13:35 [PATCH 1/4] u-boot: Update to 2016.09.01 release Marek Vasut
2016-10-20 13:35 ` [PATCH 2/4] u-boot: Drop the +git part from PV Marek Vasut
2016-10-20 13:46   ` Denys Dmytriyenko
2016-10-20 13:35 ` [PATCH V2 3/4] u-boot: Drop PV altogether Marek Vasut
2016-10-20 13:45   ` Denys Dmytriyenko
2016-10-20 13:48   ` [PATCH V3 " Marek Vasut
2016-10-20 13:58     ` Denys Dmytriyenko
2016-10-20 13:35 ` [PATCH 4/4] u-boot: Drop redundant comment Marek Vasut
2016-10-20 13:46   ` Denys Dmytriyenko
2016-10-20 13:46 ` [PATCH 1/4] u-boot: Update to 2016.09.01 release Denys Dmytriyenko
2016-10-20 15:16 ` Burton, Ross
2016-10-20 18:28   ` Marek Vasut
2016-10-21  7:47 ` Burton, Ross
2016-10-22 20:32   ` Marek Vasut
2016-10-25 18:32     ` Denys Dmytriyenko
2016-10-25 19:24       ` Marek Vasut
2016-10-27 11:44         ` Stefan Müller-Klieser [this message]
2016-10-28  0:18           ` Marek Vasut
2016-10-28  2:11             ` Denys Dmytriyenko
2016-10-28  2:14               ` Marek Vasut
2016-10-28 15:16                 ` Burton, Ross
2016-10-30 18:18                   ` Marek Vasut
2016-10-31 14:59                     ` Burton, Ross
2016-11-02 12:08                       ` Marek Vasut
2016-10-28  4:23             ` Khem Raj
2016-10-30 18:19               ` Marek Vasut

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=5811E899.6050000@phytec.de \
    --to=s.mueller-klieser@phytec.de \
    --cc=denis@denix.org \
    --cc=marex@denx.de \
    --cc=openembedded-core@lists.openembedded.org \
    /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