From: Stephen Hemminger <stephen@networkplumber.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Roman Mashak <mrv@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>, Phil Sutter <phil@nwl.cc>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: iproute2 compile and linking errors on Fedora 19
Date: Tue, 31 Oct 2017 22:06:31 +0100 [thread overview]
Message-ID: <20171031220631.2297cdf8@shemminger-XPS-13-9360> (raw)
In-Reply-To: <1509477915.3828.41.camel@edumazet-glaptop3.roam.corp.google.com>
On Tue, 31 Oct 2017 12:25:15 -0700
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> On Tue, 2017-10-31 at 15:16 -0400, Roman Mashak wrote:
> > Eric Dumazet <eric.dumazet@gmail.com> writes:
> >
> >
> > [...]
> >
> > > CC iplink_xstats.o
> > > CC ipseg6.o
> > > LINK ip
> > > xfrm_state.o: In function `xfrm_state_modify.constprop.3':
> > > xfrm_state.c:(.text+0x2458): undefined reference to `strlcpy'
> > > ipnetns.o: In function `netns_identify_pid':
> > > ipnetns.c:(.text+0x12e0): undefined reference to `strlcpy'
> > > ipxfrm.o: In function `xfrm_state_info_print':
> > > ipxfrm.c:(.text+0x1c3b): undefined reference to `strlcat'
> > > ipxfrm.c:(.text+0x1c4d): undefined reference to `strlcat'
> > > ipxfrm.c:(.text+0x215f): undefined reference to `strlcat'
> > > ipxfrm.o: In function `xfrm_policy_info_print':
> > > ipxfrm.c:(.text+0x2299): undefined reference to `strlcat'
> > > ipxfrm.c:(.text+0x22ab): undefined reference to `strlcat'
> > > iproute_lwtunnel.o: In function `parse_encap_seg6':
> > > iproute_lwtunnel.c:(.text+0xa8f): undefined reference to `strlcpy'
> > > ipvrf.o: In function `vrf_switch':
> > > ipvrf.c:(.text+0x87d): undefined reference to `strlcpy'
> > > ipvrf.o: In function `vrf_identify.constprop.2':
> > > ipvrf.c:(.text+0xe4d): undefined reference to `strlcpy'
> > > ../lib/libutil.a(bpf.o): In function `bpf_find_mntpt.constprop.10':
> > > bpf.c:(.text+0x766): undefined reference to `strlcpy'
> > > ../lib/libutil.a(bpf.o): In function `bpf_get_work_dir':
> > > bpf.c:(.text+0xb07): undefined reference to `strlcpy'
> > > ../lib/libutil.a(fs.o):fs.c:(.text+0x44f): more undefined references to
> > > `strlcpy' follow
> > > collect2: error: ld returned 1 exit status
> > > make[1]: *** [ip] Error 1
> > > make[1]: Leaving directory `/usr/src/iproute2/ip'
> > > make: *** [all] Error 2
> >
> > Latest iproute2 has config.mk instead of Config, where a new kludge
> > -DNEED_STRLCPY has been added.
>
> Oh right, I only was missing a ./configure run to generate things
> properly.
>
>
>
>
>
If you do a
$ make distclean
then
$ make
It should take care of it.
next prev parent reply other threads:[~2017-10-31 21:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 17:58 iproute2 compile and linking errors on Fedora 19 Cong Wang
2017-10-31 18:27 ` Cong Wang
2017-10-31 18:59 ` Eric Dumazet
2017-10-31 19:16 ` Roman Mashak
2017-10-31 19:25 ` Eric Dumazet
2017-10-31 21:06 ` Stephen Hemminger [this message]
2017-10-31 21:10 ` Stephen Hemminger
2017-10-31 23:28 ` Cong Wang
2017-11-01 6:52 ` Stephen Hemminger
2018-11-27 0:06 ` Stephen Hemminger
2018-11-27 11:58 ` Phil Sutter
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=20171031220631.2297cdf8@shemminger-XPS-13-9360 \
--to=stephen@networkplumber.org \
--cc=eric.dumazet@gmail.com \
--cc=mrv@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=phil@nwl.cc \
--cc=xiyou.wangcong@gmail.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