From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/7] binutils-cross.inc, binutils.inc: Overhaul for new cross dir structure.
Date: Mon, 26 Jul 2010 13:12:57 -0700 [thread overview]
Message-ID: <4C4DEC49.9050708@mentor.com> (raw)
In-Reply-To: <1280174528-27682-3-git-send-email-raj.khem@gmail.com>
Khem Raj wrote:
> * Install the symlinks instead of copied of tools.
> * Dont build shared libopcodes
Is that intended to fix the relocation issue with pstaging+relocatable?
If so I was just about to push a PREPROCESS_RELOCATE_DIRS to deal with
that. Or is there some other reason to disable shared versions of these
libraries?
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-07-26 20:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 20:02 [PATCH 0/7] Make multi-machine toolchains to co-exist (revised) Khem Raj
2010-07-26 20:02 ` [PATCH 1/7] bitbake.conf: Define HOST_SYS and TARGET_SYS based on target sub-arch Khem Raj
2010-07-26 20:02 ` [PATCH 2/7] binutils-cross.inc, binutils.inc: Overhaul for new cross dir structure Khem Raj
2010-07-26 20:12 ` Tom Rini [this message]
2010-07-26 20:19 ` Khem Raj
2010-07-26 20:02 ` [PATCH 3/7] gcc-cross: Use EXTRA_OECONF_PATHS in initial and intermediate recipes Khem Raj
2010-07-26 20:02 ` [PATCH 4/7] sdk.bbclass: override BASEPKG_HOST_SYS as it is used to make TARGET_SYS Khem Raj
2010-07-26 20:02 ` [PATCH 5/7] machines: Add new variable TARGET_SUB_ARCH Khem Raj
2010-07-26 20:02 ` [PATCH 6/7] cross.bbclass, packaged-staging.bbclass, bitbake.conf: construct *VENDOR variable from TARGET_SUB_ARCH and DISTRO_VENDOR Khem Raj
2010-07-26 20:02 ` [PATCH 7/7] recipes: Replace usage of MULTIMACH_TARGET_SYS with TARGET_SYS Khem Raj
2010-07-26 20:17 ` Koen Kooi
2010-07-26 20:24 ` Khem Raj
2010-07-26 20:30 ` Koen Kooi
2010-07-26 20:39 ` Khem Raj
2010-07-26 22:58 ` [PATCH 0/7] Make multi-machine toolchains to co-exist (revised) Tom Rini
2010-07-27 4:47 ` Khem Raj
2010-07-27 17:16 ` Tom Rini
2010-07-27 7:34 ` Phil Blundell
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=4C4DEC49.9050708@mentor.com \
--to=tom_rini@mentor.com \
--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 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.