From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Ian Munsie <imunsie@au1.ibm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] perf: Allow strong and weak functions in LIB_OBJS
Date: Tue, 7 Dec 2010 12:55:16 -0200 [thread overview]
Message-ID: <20101207145516.GA7612@ghostprotocols.net> (raw)
In-Reply-To: <1291704103-sup-9818@au1.ibm.com>
Em Tue, Dec 07, 2010 at 05:42:58PM +1100, Ian Munsie escreveu:
> Excerpts from Ian Munsie's message of Mon Nov 29 11:53:07 +1100 2010:
> > I'm not seeing any of those warnings or errors on either of the systems
> > I have been testing on (x86_64 + PPC64), but it looks like the linker is
> > trying to pull in too much from the system libraries.
> >
> > Can you test the below patch to see if the messages go away - it only
> > applies the whole-archive flag to libperf.a, whereas before I was also
> > applying it to pthread, libelf, etc.
>
> Hey Arnaldo,
>
> Just wondering if you got around to testing this patch?
Yeah, fell thru the cracks, but I tested it now on several systems and
it now seems ok, applying to perf/core, thanks,
- Arnaldo
next prev parent reply other threads:[~2010-12-07 14:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 4:12 [PATCH 1/3] perf: Correct final kernel map guesses Ian Munsie
2010-11-25 4:12 ` [PATCH 2/3] perf: Allow strong and weak functions in LIB_OBJS Ian Munsie
2010-11-26 21:18 ` Arnaldo Carvalho de Melo
2010-11-29 0:53 ` Ian Munsie
2010-12-07 6:42 ` Ian Munsie
2010-12-07 14:55 ` Arnaldo Carvalho de Melo [this message]
2010-12-08 7:39 ` [tip:perf/core] perf makefile: " tip-bot for Ian Munsie
2010-11-25 4:12 ` [PATCH 3/3] perf, powerpc: Allow perf test to handle PowerPC symbol naming Ian Munsie
2010-12-10 4:47 ` Ian Munsie
2010-12-12 14:39 ` Arnaldo Carvalho de Melo
2010-12-13 0:30 ` Ian Munsie
2010-11-28 8:34 ` [tip:perf/core] perf symbols: Correct final kernel map guesses tip-bot for Ian Munsie
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=20101207145516.GA7612@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=imunsie@au1.ibm.com \
--cc=linux-kernel@vger.kernel.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