All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>,
	Alexander Kanavin <alexander.kanavin@linux.intel.com>
Cc: OpenEmbedded Devel List
	<openembedded-devel@lists.openembedded.org>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] State of bitbake world, Failed tasks 2015-10-02
Date: Fri, 9 Oct 2015 17:19:24 +0200	[thread overview]
Message-ID: <20151009151924.GC2384@jama> (raw)
In-Reply-To: <CAJTo0LYSc3TV1D2OhmO4KN9ucJLm+d_U2BgrCq40Pk=+RiXqFA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]

On Mon, Oct 05, 2015 at 03:40:39PM +0100, Burton, Ross wrote:
> On 3 October 2015 at 14:33, Martin Jansa <martin.jansa@gmail.com> wrote:
> 
> >     * /openembedded-core/meta/recipes-gnome/libsecret/libsecret_0.18.2.bb,
> > do_compile
> >
> 
> This fails with a giant number of assembler warnings, but works when I try
> with current master.  Does your build change some tunes?

Yes, it's caused by thumb(1).

I thought it's caused by upgrade to gcc-5.2, but
ARM_INSTRUCTION_SET = "arm"
was removed by Alexander when importing libsecret from meta-oe to
oe-core, without even mentioning it in commit message :/.

The same with webkitgtk now failing to build for thumb.. old webkit-gtk
already had ARM_INSTRUCTION_SET which was silently removed.

I'll stop accepting recipe removals in meta-oe layers for recipes moved
to oe-core unless the submitter proves that they weren't modified/broken
in the process. I hate overlayed/duplicated recipes, but breaking them
is even worse.

Regards,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>,
	Alexander Kanavin <alexander.kanavin@linux.intel.com>
Cc: OpenEmbedded Devel List
	<openembedded-devel@lists.openembedded.org>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: State of bitbake world, Failed tasks 2015-10-02
Date: Fri, 9 Oct 2015 17:19:24 +0200	[thread overview]
Message-ID: <20151009151924.GC2384@jama> (raw)
In-Reply-To: <CAJTo0LYSc3TV1D2OhmO4KN9ucJLm+d_U2BgrCq40Pk=+RiXqFA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]

On Mon, Oct 05, 2015 at 03:40:39PM +0100, Burton, Ross wrote:
> On 3 October 2015 at 14:33, Martin Jansa <martin.jansa@gmail.com> wrote:
> 
> >     * /openembedded-core/meta/recipes-gnome/libsecret/libsecret_0.18.2.bb,
> > do_compile
> >
> 
> This fails with a giant number of assembler warnings, but works when I try
> with current master.  Does your build change some tunes?

Yes, it's caused by thumb(1).

I thought it's caused by upgrade to gcc-5.2, but
ARM_INSTRUCTION_SET = "arm"
was removed by Alexander when importing libsecret from meta-oe to
oe-core, without even mentioning it in commit message :/.

The same with webkitgtk now failing to build for thumb.. old webkit-gtk
already had ARM_INSTRUCTION_SET which was silently removed.

I'll stop accepting recipe removals in meta-oe layers for recipes moved
to oe-core unless the submitter proves that they weren't modified/broken
in the process. I hate overlayed/duplicated recipes, but breaking them
is even worse.

Regards,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  parent reply	other threads:[~2015-10-09 15:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-03 13:33 State of bitbake world, Failed tasks 2015-10-02 Martin Jansa
2015-10-05 14:40 ` [OE-core] " Burton, Ross
2015-10-05 14:40   ` Burton, Ross
2015-10-05 14:45   ` [OE-core] " Martin Jansa
2015-10-05 14:45     ` Martin Jansa
2015-10-09 15:19   ` Martin Jansa [this message]
2015-10-09 15:19     ` Martin Jansa
2015-10-09 15:52     ` [OE-core] " Khem Raj
2015-10-09 15:52       ` Khem Raj

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=20151009151924.GC2384@jama \
    --to=martin.jansa@gmail.com \
    --cc=alexander.kanavin@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=ross.burton@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.