DPDK patches and discussions
 help / color / mirror / Atom feed
From: Meir Tseitlin <mirots@gmail.com>
To: Olivier MATZ <olivier.matz@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Pcap question
Date: Mon, 3 Mar 2014 21:31:19 +0200	[thread overview]
Message-ID: <CA+Typ9kW8gp4fLL7=q95ZbBjB030hAjMzh-CBn_iydWC1mPT4w@mail.gmail.com> (raw)
In-Reply-To: <5313905E.7000603@6wind.com>

Hi Olivier,

The patch did solved compilation errors (Thanks!), but now I am again
experiencing linkage error with executables I had in previous versions as
well:

  LD dump_cfg
/usr/bin/ld: unrecognized option '-Wl'
/usr/bin/ld: use the --help option for usage information
collect2: error: ld returned 1 exit status
make[3]: *** [dump_cfg] Error 1
make[2]: *** [dump_cfg] Error 2
make[2]: *** Waiting for unfinished jobs....

  LD cmdline_test
/usr/bin/ld: unrecognized option '-Wl'
/usr/bin/ld: use the --help option for usage information
collect2: error: ld returned 1 exit status
make[3]: *** [cmdline_test] Error 1
make[2]: *** [cmdline_test] Error 2

  LD testpmd
/usr/bin/ld: unrecognized option '-Wl'
/usr/bin/ld: use the --help option for usage information
collect2: error: ld returned 1 exit status
make[3]: *** [testpmd] Error 1
make[2]: *** [test-pmd] Error 2


I tried it with binutils 2.22 and 2.24.

It does not happen when compiling without pcap flag enabled

Can you please put some light on it?

Many thanks
Meir Tseitlin


On Sun, Mar 2, 2014 at 10:11 PM, Olivier MATZ <olivier.matz@6wind.com>wrote:

> Hi Meir,
>
>
> On 03/02/2014 08:13 PM, Meir Tseitlin wrote:
>
>> I am experiencing problem with compiling libpcap extension with all recent
>> versions
>>
>
> Indeed, I can reproduce the compilation error on current dev version.
> The cause seems to be a conflict between the patches I submitted
> (rte_kvargs) and the one from Mats Liljegren which was commited the
> day before:
>
> http://dpdk.org/browse/dpdk/commit/?h=1.5.2&id=
> 4c745617a18fc37bd2a08aad512846a416665ae3
>
> I will submit a fix.
>
> Olivier
>
>


-- 
Kind regards,
*Meir Tseitlin*
Software architect*Mobile:* +972.54.7647417
*Fax:* +972.72.2812365
*Email:* meir.tech@gmail.com
 *http://il.linkedin.com/in/meirts <http://il.linkedin.com/in/meirts>*
*Independent consultant*
<http://maps.google.com/maps?q=&hl=en>
See who we know in
common<http://www.linkedin.com/e/wwk/6408776/?hs=false&tok=2g4qg82N8Sb5U1>Want
a signature like
this?<http://www.linkedin.com/e/sig/6408776/?hs=false&tok=20mz9jA_USb5U1>

  reply	other threads:[~2014-03-03 19:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-02 19:13 Meir Tseitlin
2014-03-02 20:11 ` Olivier MATZ
2014-03-03 19:31   ` Meir Tseitlin [this message]
2014-03-03 20:32     ` Olivier MATZ
2014-03-03 21:09       ` Meir Tseitlin
2014-03-03 21:31         ` Olivier MATZ
2014-03-03 21:37           ` Olivier MATZ
2014-03-03 21:45             ` Meir Tseitlin
2014-03-05 20:32               ` Meir Tseitlin
2014-03-06  9:00                 ` liljegren.mats2
2014-03-06  9:00                   ` [dpdk-dev] [PATCH] pcap: Remove check for pcap_sendpacket liljegren.mats2
2014-03-06 10:10                   ` [dpdk-dev] Pcap question David Marchand
2014-03-20 16:38               ` 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='CA+Typ9kW8gp4fLL7=q95ZbBjB030hAjMzh-CBn_iydWC1mPT4w@mail.gmail.com' \
    --to=mirots@gmail.com \
    --cc=dev@dpdk.org \
    --cc=olivier.matz@6wind.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).