Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: OE Staging ABI Change Warning
Date: Thu, 06 Mar 2008 13:58:32 +0100	[thread overview]
Message-ID: <fqoppp$2c9$1@ger.gmane.org> (raw)
In-Reply-To: <1204807332.8034.0.camel@dax.rpnet.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Richard Purdie schreef:
| On Tue, 2008-03-04 at 17:53 +0100, Koen Kooi wrote:
|> Richard Purdie schreef:
|> | Hi,
|> |
|> | OE.dev is now just about ready to switch to using sysroot. The
compilers
|> | have been updated to activate sysroot and the fixes I/Poky have for
|> | various pkgconfig issues have been committed. The final change is to
|> | actually change the layout.
|> |
|> | I've attached the patch I have locally for doing this. Since it changes
|> | the layout of staging I've gone for changing the ABI and warning users
|> | using the newly added mechanism.
|> |
|> | insane.bbclass will warn about potentially problematic .pc files and I
|> | suspect a few people will hit that since there are a lot of broken ones
|> | around. I'll give a summary of the problem and the way to solve it:
|>
|> When are we going to make insane halt on .la files referring to
|> ${WORKDIR}? Right now those are the biggest problem for packaged-staging
|> and rm_work.
|
| I don't remember seeing too many warnings about these? Are there many
| problematic packages?

Almost every native package suffers from it, which is why the efl stuff
fails, since that is needing the native evas, edje, etc tools.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHz+p4MkyGM64RGpERAqA+AKCIBCY03/myptRoMYuB5S1/KOoNrwCginMe
gD2gozgUxlmFAPcrPJEY/z0=
=uG24
-----END PGP SIGNATURE-----




      reply	other threads:[~2008-03-06 13:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-29 16:46 OE Staging ABI Change Warning Richard Purdie
2008-02-29 17:24 ` Leon Woestenberg
2008-02-29 18:04   ` Richard Purdie
2008-02-29 18:29     ` Leon Woestenberg
2008-02-29 22:43       ` Richard Purdie
2008-03-03  1:07 ` Holger Freyther
2008-03-03  9:37   ` Richard Purdie
2008-03-03 12:12     ` Holger Freyther
2008-03-03 12:46       ` Koen Kooi
2008-03-03 14:34         ` Richard Purdie
2008-03-03 14:43           ` Koen Kooi
2008-03-03 15:46           ` Rod Whitby
2008-03-03 16:14             ` Leon Woestenberg
2008-03-03 16:39               ` Leon Woestenberg
2008-03-03 17:20 ` Mike (mwester)
2008-03-04  0:08 ` Koen Kooi
2008-03-04 16:53 ` Koen Kooi
2008-03-06 12:42   ` Richard Purdie
2008-03-06 12:58     ` Koen Kooi [this message]

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='fqoppp$2c9$1@ger.gmane.org' \
    --to=koen@dominion.kabel.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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