From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] mk: --no-as-needed by default for linux exec-env
Date: Wed, 5 Nov 2014 15:02:01 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D89726833407@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1414666662-14966-1-git-send-email-sergio.gonzalez.monroy@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Sergio Gonzalez
> Monroy
> Sent: Thursday, October 30, 2014 10:58 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] mk: --no-as-needed by default for linux exec-
> env
>
> Ubuntu/Debian toolchain passes --as-needed flag to the linker by default.
> Add --no-as-needed flag by default in linuxapp exec-env to ensure correct
> linking.
>
> Signed-off-by: Sergio Gonzalez Monroy
> <sergio.gonzalez.monroy@intel.com>
Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Anyway, it is worth stating that as Neil and Sergio have pointed out, we should probably
change the way we build the libraries, considering all problems that we have encountered recently.
next prev parent reply other threads:[~2014-11-05 14:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 10:57 Sergio Gonzalez Monroy
2014-10-30 11:05 ` Gonzalez Monroy, Sergio
2014-10-30 14:01 ` Neil Horman
2014-10-30 16:20 ` Gonzalez Monroy, Sergio
2014-10-30 19:21 ` Neil Horman
2014-10-31 9:02 ` Gonzalez Monroy, Sergio
2014-11-05 15:02 ` De Lara Guarch, Pablo [this message]
2014-11-28 15:35 ` Thomas Monjalon
2014-11-29 15:02 ` Neil Horman
2014-11-29 20:20 ` Thomas Monjalon
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=E115CCD9D858EF4F90C690B0DCB4D89726833407@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=sergio.gonzalez.monroy@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).