Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] error out on .la files pointing to ${WORKDIR}
Date: Wed, 19 Mar 2008 16:25:43 +0100	[thread overview]
Message-ID: <frrb9n$5eh$1@ger.gmane.org> (raw)
In-Reply-To: <1205929346.4555.34.camel@dax.rpnet.com>

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

Richard Purdie schreef:
| Hi,
|
| On Wed, 2008-03-19 at 11:50 +0100, Koen Kooi wrote:
|> Things in stagin (e.g. .la files) point to ${WORKDIR} are broken and
|> should die. If we want packaged-staging and rm_work to function we
|> need to fix them. Since we are all lazy we need some incentive:
| [...]
|> --- classes/insane.bbclass      0712df99743c442ed311e6b4d4be0d28f29d525f
|> +++ classes/insane.bbclass      fa6b704f402965c8123dfa90527b5a11a8cd3288
|> @@ -178,7 +178,7 @@ def package_qa_make_fatal_error(error_cl
|>
|>       TODO: Load a whitelist of known errors
|>       """
|> - -    return not error_class in [0, 5, 7, 8]
|> +    return not error_class in [0, 5, 7]
|>
|>   def package_qa_write_error(error_class, name, path, d):
|>       """
|
| I'm ok with applying that since we do really need to sort out these
| issues.
|
| I did a load of cleanup in this area in poky and found in a lot of cases
| this happened since we weren't using oe_libinstall which mangles the .la
| files if it notices anything wrong with them.

Richard and I have now finally fixed the native.bbclass staging logic
for autotoolws packages. This means virtually all -native autotooled
recipes now get sanitized automagically.

regards,

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

iD8DBQFH4TB3MkyGM64RGpERAnvLAKC0++o3ntLzOjqv5pmrbcLrFl4pQwCgmRAj
9EL16VVjDtR54mR2axB8dPA=
=FemV
-----END PGP SIGNATURE-----




  reply	other threads:[~2008-03-19 15:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-19 10:50 [RFC] error out on .la files pointing to ${WORKDIR} Koen Kooi
2008-03-19 11:24 ` Florian Boor
2008-03-19 11:35   ` Koen Kooi
2008-03-19 12:23   ` Richard Purdie
2008-03-19 12:00 ` Stanislav Brabec
2008-03-19 12:35   ` Koen Kooi
2008-03-19 13:06     ` Stanislav Brabec
2008-03-19 12:22 ` Richard Purdie
2008-03-19 15:25   ` Koen Kooi [this message]
2008-03-19 22:26 ` Koen Kooi

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='frrb9n$5eh$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