linux-kernel - Re: [PATCH 1/3] perf tools: Separate lbfd check out of NO

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87li2cm5je.fsf@sejong.aot.lge.com>
Date:	Wed, 02 Oct 2013 17:38:13 +0900
From:	Namhyung Kim <namhyung@...nel.org>
To:	Jiri Olsa <jolsa@...hat.com>
Cc:	linux-kernel@...r.kernel.org,
	Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
	Ingo Molnar <mingo@...e.hu>, Paul Mackerras <paulus@...ba.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	David Ahern <dsahern@...il.com>
Subject: Re: [PATCH 1/3] perf tools: Separate lbfd check out of NO_DEMANGLE condition

Hi Jiri,

On Wed, 2 Oct 2013 10:17:57 +0200, Jiri Olsa wrote:
> On Wed, Oct 02, 2013 at 10:18:32AM +0900, Namhyung Kim wrote:
>> It seems that it needs libdl for loading plugins.  Adding -ldl makes
>> above build successfully.  So we need to add -ldl for EXTLIBS IMHO.
>> Without it, make NO_GTK2=1 NO_LIBPERL=1 NO_LIBPYTHON=1 will fail to
>> check libbfd correctly (FYI, libperl and libpython add -ldl to the
>> dependency list).
>
> hum, so on my system -liberty check wins without -lbfd,
> so 'NO_GTK2=1 NO_LIBPERL=1 NO_LIBPYTHON=1' passes
>
> I need to check Ingo's latest changes on this, not sure how
> if this problem is relevant any longer ;-)

AFAICS, Ingo's patch does "-lbfd -ldl" rather than "-lbfd".  So probably
there's no problem then. :)

Thanks,
Namhyung
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/