DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] mk: fix build 32bits shared libs on 64bits system
Date: Mon, 1 Dec 2014 09:51:25 +0000	[thread overview]
Message-ID: <91383E96CE459D47BCE92EFBF5CE73B004EF72FD@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <8053165.4G51We95Ac@xps13>

> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Friday, November 28, 2014 3:49 PM
> Hi Sergio,
> 2014-10-22 17:36, Sergio Gonzalez Monroy:
> > Incompatible libraries error when building shared libraries for 32bits
> > on a 64bits system.
> > Fix issue by passing CPU_CFLAGS to CC when LINK_USING_CC is enabled.
> This issue looks really strange. If that's the only way to fix it, it would be
> better to have a comment in the makefile and a detailed explanation in the
> commit log.
Hi Thomas,

There may be a better way to deal with this, please feel free to suggest alternate method.
We do specify -m32 or -m64 when building the DPDK.
The issue is that we were not specifying -m32 when linking, therefore the wrong libraries were being picked.

At the time CPU_CFLAGS was only being set with -m32/-m64, reason why I used such variable.
Would it be better to create another var and pass it down?


> Thanks
> --
> Thomas

  reply	other threads:[~2014-12-01  9:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22 16:36 Sergio Gonzalez Monroy
2014-10-28 16:30 ` De Lara Guarch, Pablo
2014-11-28 15:48 ` Thomas Monjalon
2014-12-01  9:51   ` Gonzalez Monroy, Sergio [this message]
2014-12-08 14:52 ` [dpdk-dev] " Neil Horman
2014-12-11  0:49   ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=91383E96CE459D47BCE92EFBF5CE73B004EF72FD@IRSMSX108.ger.corp.intel.com \
    --to=sergio.gonzalez.monroy@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.com \


* 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).