From: Denys Dmytriyenko <denis@denix.org>
To: Raphael Philipe <rapphil@gmail.com>
Cc: Denys Dmytriyenko <denys@ti.com>,
Otavio Salvador <otavio@ossystems.com.br>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] u-boot: update to 2015.01
Date: Thu, 22 Jan 2015 22:50:05 -0500 [thread overview]
Message-ID: <20150123035005.GV20639@denix.org> (raw)
In-Reply-To: <20150122212316.GU20639@denix.org>
On Thu, Jan 22, 2015 at 04:23:16PM -0500, Denys Dmytriyenko wrote:
> On Thu, Jan 22, 2015 at 07:50:28AM -0200, Raphael Philipe wrote:
> > Hey Denys, I tested u-boot-fw-utils-cross_2014.07.bb in Ubuntu 12.04
> > and got the same error .
> >
> > Can you confirm that this recipe works for you?
>
> Ok, trying to bisect the breakage of the current 2014.07 version of
> fw-utils-cross now:
>
> Poky snapshot from mid-September, when 2014.07 update patch was submitted and
> when it was validated by the autobuilder - still works fine.
>
> Since it was a feature freeze time before the release, the patch was not
> accepted and was queued for later.
>
> Poky snapshot from mid-November, when the patch was finally applied - the
> build breaks. Again, it may not be showing the issue on the autobuilder due to
> an earlier successful sstate.
>
> So, somewhere in between a change was introduced that breaks fw-utils-cross.
> BTW, neither 2014.07 update nor 2015.01 change anything to the way
> fw-utils-cross gets built.
Heh, and the commit that breaks (on purpose!) building 2014.07 version of
u-boot-fw-utils-cross is the one from Richard (which does make sense):
gcc: poison default sysroot path
Various pieces of the code assume that the --sysroot option gets passed
into the compiler tools. By having a "sane" default, we don't always
spot when this occurs and this can later show up as breakage in sstate,
or in usage of the external toolchain.
We've long since talked about poisoning the default such that it will
break unless the correct option is specified. This patch does just that.
If this patch causes something to fail to build, it most likely means
the various compiler flags and commands are not correctly being passed
through to the underlying piece of software and that there is a real
problem that needs fixing, its not the fault of this patch.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=678e8798ebe0f4fd1bd347db136f1499b8fe00c9
--
Denys
next prev parent reply other threads:[~2015-01-23 3:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 16:09 [PATCH] u-boot: update to 2015.01 Denys Dmytriyenko
2015-01-20 20:19 ` Denys Dmytriyenko
2015-01-21 13:17 ` Otavio Salvador
2015-01-21 19:11 ` Denys Dmytriyenko
2015-01-21 20:11 ` Otavio Salvador
2015-01-21 20:20 ` Denys Dmytriyenko
2015-01-22 9:50 ` Raphael Philipe
2015-01-22 12:05 ` Burton, Ross
2015-01-22 14:57 ` Denys Dmytriyenko
2015-01-22 15:02 ` Burton, Ross
2015-01-22 15:12 ` Raphael Philipe
2015-01-22 15:17 ` Denys Dmytriyenko
2015-01-22 15:40 ` Otavio Salvador
2015-01-22 16:00 ` Denys Dmytriyenko
2015-01-22 16:05 ` Otavio Salvador
2015-01-22 21:23 ` Denys Dmytriyenko
2015-01-23 3:50 ` Denys Dmytriyenko [this message]
2015-01-22 16:07 ` Denys Dmytriyenko
2015-01-22 16:12 ` Otavio Salvador
2015-01-22 16:33 ` Denys Dmytriyenko
2015-01-21 20:25 ` Raphael Philipe
2015-01-21 20:28 ` Denys Dmytriyenko
2015-01-21 20:31 ` Raphael Philipe
2015-01-21 20:35 ` Denys Dmytriyenko
2015-01-21 20:48 ` Raphael Philipe
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=20150123035005.GV20639@denix.org \
--to=denis@denix.org \
--cc=denys@ti.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=rapphil@gmail.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