All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Phil Blundell <pb@pbcl.net>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] ARM: handle missing thumb suffix
Date: Thu, 15 Oct 2015 14:09:34 +0200	[thread overview]
Message-ID: <20151015120934.GD2588@jama> (raw)
In-Reply-To: <1444909889.5251.68.camel@pbcl.net>

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

On Thu, Oct 15, 2015 at 12:51:29PM +0100, Phil Blundell wrote:
> On Thu, 2015-10-15 at 13:31 +0200, Martin Jansa wrote:
> 
> > It's package architecture for binary feeds with -mtune=arm926ejs and
> > it
> > can be built with or without -mthumb, that's why packages can be
> > built
> > in arm926ejse or arm926ejste package feed.
> 
> Yes, I understand that.  But the point is that there doesn't seem to be
> any good reason to distinguish those two cases by PACKAGE_ARCH, any
> more than we use separate PACKAGE_ARCH values for binaries built with 
> -O2, or -fpie, or any number of other options.
> 
> ARM926EJ-S, by definition, can execute both ARM and Thumb code so there
> is no meaningful situation where arm926ejse binaries might be usable
> yet arm926ejste ones are not.  

What about consistency with less specific PACKAGE_ARCHs which use "t" to
show if it was built with or without thumb?

Or more strange case when some DISTRO without PR service enables thumb
and package manager can in theory migrate/upgrade packages from arm926ejse feed
to arm926ejste ones even when the version is the same (doesn't work with
opkg)

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

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

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13 20:37 [PATCH 2/2] ARM: handle missing thumb suffix Jens Rehsack
2015-10-13 21:18 ` Martin Jansa
2015-10-15 10:49 ` Phil Blundell
2015-10-15 11:18   ` Jens Rehsack
2015-10-15 11:31   ` Martin Jansa
2015-10-15 11:51     ` Phil Blundell
2015-10-15 12:09       ` Martin Jansa [this message]
2015-10-15 13:39         ` Phil Blundell

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=20151015120934.GD2588@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pb@pbcl.net \
    /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.