All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Phil Blundell <pb@pbcl.net>
Cc: openembedded-devel@lists.openembedded.org,
	openembedded-core@lists.openembedded.org
Subject: Re: [oe] Public TSC / OE Workgroup meeting today
Date: Tue, 14 Jan 2014 14:33:39 +0100	[thread overview]
Message-ID: <20140114133339.GC3717@jama> (raw)
In-Reply-To: <1389704128.19023.11.camel@phil-desktop.brightsign>

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

On Tue, Jan 14, 2014 at 12:55:28PM +0000, Phil Blundell wrote:
> On Tue, 2014-01-14 at 13:13 +0100, Martin Jansa wrote:
> > Not sure if it's worth new item on agenda, but maybe we should move
> > meta/classes/image-prelink.bbclass functionality to package.bbclass,
> > maybe we have more cases like this where image build is changing files
> > which are provided by normal packages (such cases are lost after
> > upgrading on device with packagemanager).
> 
> How would that work?  I'm not sure that it's possible (in the general
> case) to prelink in any sensible way prior to rootfs construction.  The
> same applies to image-mklibs.bbclass.

Hmm, you're right.

The reason why I was thinking about this, is that someone reported to me
that libc-dbg doesn't work after prelink changed libc headers in
do_rootfs (external toolchain).

IIRC there was some discussion about issues caused by prelink changing headers,
I'll try to find it in archives, sorry for noise.
-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

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

WARNING: multiple messages have this Message-ID (diff)
From: Martin Jansa <martin.jansa@gmail.com>
To: Phil Blundell <pb@pbcl.net>
Cc: openembedded-devel@lists.openembedded.org,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] Public TSC / OE Workgroup meeting today
Date: Tue, 14 Jan 2014 14:33:39 +0100	[thread overview]
Message-ID: <20140114133339.GC3717@jama> (raw)
In-Reply-To: <1389704128.19023.11.camel@phil-desktop.brightsign>

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

On Tue, Jan 14, 2014 at 12:55:28PM +0000, Phil Blundell wrote:
> On Tue, 2014-01-14 at 13:13 +0100, Martin Jansa wrote:
> > Not sure if it's worth new item on agenda, but maybe we should move
> > meta/classes/image-prelink.bbclass functionality to package.bbclass,
> > maybe we have more cases like this where image build is changing files
> > which are provided by normal packages (such cases are lost after
> > upgrading on device with packagemanager).
> 
> How would that work?  I'm not sure that it's possible (in the general
> case) to prelink in any sensible way prior to rootfs construction.  The
> same applies to image-mklibs.bbclass.

Hmm, you're right.

The reason why I was thinking about this, is that someone reported to me
that libc-dbg doesn't work after prelink changed libc headers in
do_rootfs (external toolchain).

IIRC there was some discussion about issues caused by prelink changing headers,
I'll try to find it in archives, sorry for noise.
-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

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

  reply	other threads:[~2014-01-14 13:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14 10:08 Public TSC / OE Workgroup meeting today Paul Eggleton
2014-01-14 12:13 ` [oe] " Martin Jansa
2014-01-14 12:13   ` Martin Jansa
2014-01-14 12:55   ` [oe] " Phil Blundell
2014-01-14 13:33     ` Martin Jansa [this message]
2014-01-14 13:33       ` [OE-core] " Martin Jansa
2014-01-14 15:54   ` [oe] " Mark Hatle
2014-01-14 16:10 ` Trevor Woerner
2014-01-14 16:45 ` Trevor Woerner

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=20140114133339.GC3717@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@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.