From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [META-OE][PATCH 1/1] oscam: fixed QA issue where binary was being stripped
Date: Thu, 21 Aug 2014 09:44:59 +0200 [thread overview]
Message-ID: <lt481r$hms$1@ger.gmane.org> (raw)
In-Reply-To: <CAHQecY6bxmkDi3U6nN3MhF4x6-ysPnXyb0nwrjXwq3-xX5NdcQ@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Tom King schreef op 21-08-14 08:13:
> http://lists.openembedded.org/pipermail/openembedded-core/2014-August/095778.html
>
> WARNING: QA Issue: File '/usr/bin/oscam' from oscam was already
> stripped, this will prevent future debugging! [already-stripped]
>
> Fix above warning by telling cmake to do Debug type build, which
> prevents linking with '-s' flag that removed symbols before bitbake could
> put them into dbg package.
>
> Signed-off-by: S. Lockwood-Childs <sjl@vctlabs.com> Signed-off-by: Tom
> King<ka6sox@gmail.com> --- meta-multimedia/recipes-dvb/oscam/oscam_svn.bb
> | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta-multimedia/recipes-dvb/oscam/oscam_svn.bb
> b/meta-multimedia/recipes-dvb/oscam/oscam_svn.bb index e3f2708..c4a4d99
> 100644 --- a/meta-multimedia/recipes-dvb/oscam/oscam_svn.bb +++
> b/meta-multimedia/recipes-dvb/oscam/oscam_svn.bb @@ -14,5 +14,5 @@ S =
> "${WORKDIR}/trunk"
>
> inherit cmake
>
> -EXTRA_OECMAKE = "-DDEFAULT_CS_CONFDIR=${sysconfdir}" +EXTRA_OECMAKE =
> "-DDEFAULT_CS_CONFDIR=${sysconfdir} -DCMAKE_BUILD_TYPE=Debug"
Whitespace damage due to mailer?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFT9aN7MkyGM64RGpERAocuAJ41630bimczFzLdBtpxDkCRY33h6QCeO80c
myBws3uS1pXaavua8+O9vo8=
=xjKT
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2014-08-21 7:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 6:13 [META-OE][PATCH 1/1] oscam: fixed QA issue where binary was being stripped Tom King
2014-08-21 7:44 ` 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='lt481r$hms$1@ger.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@lists.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