DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Qiu, Michael" <michael.qiu@intel.com>
To: "thomas.monjalon@6wind.com" <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Compile error with CONFIG_RTE_BUILD_COMBINE_LIBS=y
Date: Tue, 8 Dec 2015 07:08:21 +0000	[thread overview]
Message-ID: <533710CFB86FA344BFBF2D6802E6028621B9605C@SHSMSX101.ccr.corp.intel.com> (raw)

Hi, Thomas

I see you recently merged one commit:

commit 8f1c704fb0f1b867471fc692ed2c0fc5610831e2
Author: Thomas Monjalon <thomas.monjalon@6wind.com>
Date:   Tue Dec 8 01:50:17 2015 +0100

    mk: fix external library build when combine is enabled
    
    The object files are copied to prepare the internal combined library.
    It must be disabled when building an external library.
    
    It has been seen because the directory was missing:
        examples/ethtool/lib/x86_64-native-linuxapp-gcc/build/lib:
        No such file or directory
    
    Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>

It lead compile error when open CONFIG_RTE_BUILD_COMBINE_LIBS.

See below:

make -j install T=x86_64-native-linuxapp-gcc

...

 CC pipeline_acl.o                                                      
                                                                       
                                                      [1491/1853]
  CC parameters.o
  CC macfwd-retry.o
  CC testpmd.o
  CC macswap.o
  CC macfwd.o
  CC rxonly.o
  CC flowgen.o
  CC txonly.o
  CC csumonly.o
  CC icmpecho.o
  CC mempool_anon.o
  LD cmdline_test
  CC test.o
  CC commands.o
  CC test_pci.o
  CC test_prefetch.o
  CC test_byteorder.o
  CC test_per_lcore.o
  CC test_atomic.o
cmdline_test.o: In function `main':
cmdline_test.c:(.text.startup+0xc): undefined reference to
`cmdline_stdin_new'
cmdline_test.c:(.text.startup+0x1c): undefined reference to
`cmdline_interact'
cmdline_test.c:(.text.startup+0x24): undefined reference to
`cmdline_stdin_exit'
commands.o: In function `cmd_quit_parsed':
commands.c:(.text+0x4): undefined reference to `cmdline_quit'
commands.o: In function `cmd_single_parsed':
commands.c:(.text+0x1b): undefined reference to `cmdline_printf'
commands.o: In function `cmd_single_long_parsed':
commands.c:(.text+0x2b): undefined reference to `cmdline_printf'
commands.o: In function `cmd_autocomplete_1_parsed':
commands.c:(.text+0x3b): undefined reference to `cmdline_printf'
commands.o: In function `cmd_autocomplete_2_parsed':
commands.c:(.text+0x4b): undefined reference to `cmdline_printf'
commands.o: In function `cmd_num_parsed':
commands.c:(.text+0x60): undefined reference to `cmdline_printf'
commands.o:commands.c:(.text+0x7b): more undefined references to
`cmdline_printf' follow
commands.o: In function `cmd_clear_history_parsed':
commands.c:(.text+0xb5): undefined reference to `rdline_clear_history'
commands.o:(.data+0x90): undefined reference to `cmdline_token_string_ops'
commands.o:(.data+0xe0): undefined reference to `cmdline_token_string_ops'
commands.o:(.data+0x130): undefined reference to `cmdline_token_string_ops'
commands.o:(.data+0x150): undefined reference to `cmdline_token_string_ops'
commands.o:(.data+0x1a0): undefined reference to `cmdline_token_string_ops'
commands.o:(.data+0x1c0): more undefined references to
`cmdline_token_string_ops' follow
commands.o:(.data+0x210): undefined reference to `cmdline_token_num_ops'
commands.o:(.data+0x260): undefined reference to `cmdline_token_string_ops'
commands.o:(.data+0x2b0): undefined reference to `cmdline_token_string_ops'
commands.o:(.data+0x300): undefined reference to `cmdline_token_string_ops'
commands.o:(.data+0x350): undefined reference to `cmdline_token_string_ops'
commands.o:(.data+0x3a0): undefined reference to `cmdline_token_string_ops'

....



Thanks,
Michael

             reply	other threads:[~2015-12-08  7:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08  7:08 Qiu, Michael [this message]
2015-12-08  9:25 ` Qiu, Michael

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=533710CFB86FA344BFBF2D6802E6028621B9605C@SHSMSX101.ccr.corp.intel.com \
    --to=michael.qiu@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@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).