All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/8] Various fixes to obey LDFLAGS
Date: Thu, 18 Sep 2014 00:30:06 -0700	[thread overview]
Message-ID: <541A89FE.9070509@gmail.com> (raw)
In-Reply-To: <cover.1409764769.git.chris_larson@mentor.com>

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



On 9/3/14 10:27 AM, Christopher Larson wrote:
> From: Christopher Larson <chris_larson@mentor.com>
> 
> This patch series fixes 8 recipes to obey LDFLAGS. These issues are easy to
> miss, now that the internal toolchain defaults to passing the correct
> GNU_HASH, so GNU_HASH warnings when LDFLAGS isn't obeyed are only seen when
> using an external toolchain. These were kept in meta-sourcery or meta-mentor,
> but given these are general correctness fixes, regardless of the lack of
> warnings for most users, I think they're appropriate for upstream inclusion.

may be they should be sent to respective component upstreams first

> 
> The following changes since commit e72aac2ae9e5fce1715fa04b7e94034fd06892d9:
> 
>   alsa-lib: libasound should runtime depends on alsa-conf (2014-09-03 11:30:11 +0100)
> 
> are available in the git repository at:
> 
>   git@github.com:kergoth/openembedded-core ldflags-fixes
>   https://github.com/kergoth/openembedded-core ldflags-fixes
> 
> for you to fetch changes up to 2cddd349eb9cafbbaf5257fb61beb9dc249df85c:
> 
>   python: obey LDFLAGS (2014-09-03 10:18:37 -0700)
> 
> ----------------------------------------------------------------
> Christopher Larson (8):
>       zlib: obey LDFLAGS for tests
>       gdbm-1.8.3: obey LDFLAGS
>       ossp-uuid: obey LDFLAGS
>       setserial: obey LDFLAGS
>       hostap-utils: obey LDFLAGS
>       blktrace: obey LDFLAGS for btrecord
>       irda-utils: obey LDFLAGS
>       python: obey LDFLAGS
> 
>  .../hostap/hostap-utils-0.4.7/ldflags.patch        | 27 ++++++++
>  meta/recipes-bsp/hostap/hostap-utils_0.4.7.bb      |  1 +
>  meta/recipes-bsp/setserial/setserial/ldflags.patch | 23 +++++++
>  meta/recipes-bsp/setserial/setserial_2.17.bb       |  1 +
>  .../irda-utils/irda-utils-0.9.18/ldflags.patch     | 79 ++++++++++++++++++++++
>  .../irda-utils/irda-utils_0.9.18.bb                | 18 +++--
>  .../zlib/zlib-1.2.8/ldflags-tests.patch            | 45 ++++++++++++
>  meta/recipes-core/zlib/zlib_1.2.8.bb               |  1 +
>  .../ossp-uuid/ossp-uuid/ldflags.patch              | 23 +++++++
>  meta/recipes-devtools/ossp-uuid/ossp-uuid_1.6.2.bb |  1 +
>  meta/recipes-devtools/python/python_2.7.3.bb       |  3 +-
>  .../recipes-kernel/blktrace/blktrace/ldflags.patch |  8 ++-
>  meta/recipes-support/gdbm/gdbm-1.8.3/ldflags.patch | 22 ++++++
>  meta/recipes-support/gdbm/gdbm_1.8.3.bb            |  3 +-
>  14 files changed, 245 insertions(+), 10 deletions(-)
>  create mode 100644 meta/recipes-bsp/hostap/hostap-utils-0.4.7/ldflags.patch
>  create mode 100644 meta/recipes-bsp/setserial/setserial/ldflags.patch
>  create mode 100644 meta/recipes-connectivity/irda-utils/irda-utils-0.9.18/ldflags.patch
>  create mode 100644 meta/recipes-core/zlib/zlib-1.2.8/ldflags-tests.patch
>  create mode 100644 meta/recipes-devtools/ossp-uuid/ossp-uuid/ldflags.patch
>  create mode 100644 meta/recipes-support/gdbm/gdbm-1.8.3/ldflags.patch
> 

- -- 
- -Khem
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - https://gpgtools.org

iEYEARECAAYFAlQaif4ACgkQuwUzVZGdMxSgGACdGG6xSxCtB+8Fe71rw7Uscd/H
LA4AmgNOrOnTSCYUFDTjPPMXsgmnMejp
=IrqW
-----END PGP SIGNATURE-----


      parent reply	other threads:[~2014-09-18  7:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-03 17:27 [PATCH 0/8] Various fixes to obey LDFLAGS Christopher Larson
2014-09-03 17:27 ` [PATCH 1/8] zlib: obey LDFLAGS for tests Christopher Larson
2014-09-03 17:27 ` [PATCH 2/8] gdbm-1.8.3: obey LDFLAGS Christopher Larson
2014-09-03 17:27 ` [PATCH 3/8] ossp-uuid: " Christopher Larson
2014-09-04 10:39   ` Burton, Ross
2014-09-03 17:27 ` [PATCH 4/8] setserial: " Christopher Larson
2014-09-04 10:39   ` Burton, Ross
2014-09-03 17:27 ` [PATCH 5/8] hostap-utils: " Christopher Larson
2014-09-04 10:48   ` Burton, Ross
2014-09-03 17:27 ` [PATCH 6/8] blktrace: obey LDFLAGS for btrecord Christopher Larson
2014-09-04 10:48   ` Burton, Ross
2014-09-03 17:27 ` [PATCH 7/8] irda-utils: obey LDFLAGS Christopher Larson
2014-09-04 10:48   ` Burton, Ross
2014-09-03 17:27 ` [PATCH 8/8] python: " Christopher Larson
2014-09-17  1:16 ` [PATCHv2 0/8] Various fixes to " Christopher Larson
2014-09-17  1:16 ` [PATCH v2 1/8] zlib: obey LDFLAGS for tests Christopher Larson
2014-09-17  1:16 ` [PATCH v2 2/8] gdbm-1.8.3: obey LDFLAGS Christopher Larson
2014-09-17  1:16 ` [PATCH v2 3/8] ossp-uuid: " Christopher Larson
2014-09-17  1:16 ` [PATCH v2 4/8] setserial: " Christopher Larson
2014-09-17  1:16 ` [PATCH v2 5/8] hostap-utils: " Christopher Larson
2014-09-17  1:17 ` [PATCH v2 6/8] blktrace: obey LDFLAGS for btrecord Christopher Larson
2014-09-18  7:26   ` Khem Raj
2014-09-18 20:51     ` Christopher Larson
2014-09-19  4:42       ` Khem Raj
2014-09-17  1:17 ` [PATCH v2 7/8] irda-utils: obey LDFLAGS Christopher Larson
2014-09-17  1:17 ` [PATCH v2 8/8] python: " Christopher Larson
2014-09-18  7:30 ` Khem Raj [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=541A89FE.9070509@gmail.com \
    --to=raj.khem@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 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.