From: Martin Jansa <martin.jansa@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gcc-4.6: Some small performance tweaks
Date: Tue, 14 Feb 2012 20:08:00 +0100 [thread overview]
Message-ID: <20120214190800.GC23843@jama.jama.net> (raw)
In-Reply-To: <20120214185506.GA11340@sakrah.homelinux.org>
[-- Attachment #1: Type: text/plain, Size: 1784 bytes --]
On Tue, Feb 14, 2012 at 10:55:06AM -0800, Khem Raj wrote:
> On (14/02/12 13:16), Martin Jansa wrote:
> > On Sat, Feb 11, 2012 at 5:24 PM, Richard Purdie
> > <richard.purdie@linuxfoundation.org> wrote:
> > > On Fri, 2012-02-10 at 17:58 -0800, Khem Raj wrote:
> > >> On (10/02/12 13:40), Richard Purdie wrote:
> > >> > On Thu, 2012-02-09 at 16:39 -0800, Khem Raj wrote:
> > >> > > On Thu, Feb 9, 2012 at 4:06 PM, Richard Purdie
> > >> > > <richard.purdie@linuxfoundation.org> wrote:
> > >> > > >
> > >> > > > +NATIVEDEPS = "mpfr-native gmp-native libmpc-native zlib-native"
> > >> > >
> > >> > >
> > >> > > note that we will need to ship zlib-nativesdk as well if we do this
> > >> > > so hopefully that case is covered by this.
> > >> >
> > >> > Yes, zlib has a BBCLASSEXTEND on zlib-nativesdk so this should be fine.
> > >>
> > >> OK and this is bundled with meta-toolchain too right ?
> > >
> > > By anything that depends on it by the shlibs code in the usual way, yes.
> >
> > But zlib is build time dependency, isn't it?
>
> yes it must be added to target gcc recipe
>
> >
> > Now it fails to build target gcc because it depends only on
> > zlib-native not target zlib and zlib.h is not found.
>
> whats the exact error? usually zlib is needed for gcj. are you building
> gcj ?
I don't have that log anymore, but I'm building default gcc
configuration from oe-core/meta-oe (iirc without gcj) and IIRC it was
from lto (gcc/lto-compress.c:#include <zlib.h>).
Cheers,
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2012-02-14 19:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 0:06 [PATCH] gcc-4.6: Some small performance tweaks Richard Purdie
2012-02-10 0:39 ` Khem Raj
2012-02-10 13:40 ` Richard Purdie
2012-02-11 1:58 ` Khem Raj
2012-02-11 16:24 ` Richard Purdie
2012-02-14 12:16 ` Martin Jansa
2012-02-14 18:55 ` Khem Raj
2012-02-14 19:08 ` Martin Jansa [this message]
2012-02-14 19:13 ` Khem Raj
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=20120214190800.GC23843@jama.jama.net \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@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