From: Namhyung Kim <namhyung@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Thomas Backlund <tmb@mageia.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Jiri Olsa <jolsa@redhat.com>
Subject: Re: perf 3.8-rc build failure: undefined reference to `strlcpy'
Date: Wed, 30 Jan 2013 11:15:55 +0900 [thread overview]
Message-ID: <87ehh3v2jo.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <20130129103722.GE14444@pd.tnic> (Borislav Petkov's message of "Tue, 29 Jan 2013 11:37:22 +0100")
Hi Borislav,
On Tue, 29 Jan 2013 11:37:22 +0100, Borislav Petkov wrote:
> On Tue, Jan 29, 2013 at 06:22:53AM +0200, Thomas Backlund wrote:
>>
>> [tmb@tmb linux-3.8-rc5]$ make -C tools/perf -s V=1
>> HAVE_CPLUS_DEMANGLE=1 prefix=%{_prefix} all
>>
>> ...
>>
>> /tmp/ccJEJv6m.o: In function `main':
>> :(.text+0x14): undefined reference to `strlcpy'
>> collect2: ld returned 1 exit status
>>
>> ...
>>
>> This did not show up in 3.7
>
> Ditto here:
>
> /tmp/ccC1kLwn.o: In function `main':
> :(.text+0x14): undefined reference to `strlcpy'
> collect2: error: ld returned 1 exit status
>
> Someone needs to get HAVE_STRLCPY and tools/perf/util/path.c in order so
> that the linker sees it, IMHO.
Please see my reply on another post from Thomas:
https://lkml.org/lkml/2013/1/29/32
It's not like a build failure of perf tools, it's just a result of
feature test so should not affect the build of perf itself, right? Why
it confuses us is that we don't show any compile message if -s option is
given to make, so I posted a patch to hide CHK and above failure message
when -s option is specified.
Thanks,
Namhyung
next prev parent reply other threads:[~2013-01-30 2:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 4:22 perf 3.8-rc build failure: undefined reference to `strlcpy' Thomas Backlund
2013-01-29 10:37 ` Borislav Petkov
2013-01-30 2:15 ` Namhyung Kim [this message]
2013-01-30 3:28 ` Borislav Petkov
2013-01-30 4:56 ` Namhyung Kim
2013-01-30 5:42 ` Borislav Petkov
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=87ehh3v2jo.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=acme@redhat.com \
--cc=bp@alien8.de \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tmb@mageia.org \
/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