From: "Bin.Cheng" <amker.cheng@gmail.com>
To: "Bin.Cheng" <amker.cheng@gmail.com>, binutils@sourceware.org
Subject: Re: Skip ld/lto tests if plugins is disabled for binutils?
Date: Tue, 12 Aug 2014 02:52:00 -0000 [thread overview]
Message-ID: <CAHFci28bf7N3ELc-n8ObrrVMONPVQsf1QfQSrJXJnD4ESFbB7g@mail.gmail.com> (raw)
In-Reply-To: <20140811125907.GF7047@bubble.grove.modra.org>
On Mon, Aug 11, 2014 at 8:59 PM, Alan Modra <amodra@gmail.com> wrote:
> On Mon, Aug 11, 2014 at 04:21:55PM +0800, Bin.Cheng wrote:
>> On Mon, Aug 11, 2014 at 3:55 PM, Alan Modra <amodra@gmail.com> wrote:
>> > On Mon, Aug 11, 2014 at 02:26:19PM +0800, Bin.Cheng wrote:
>> >> Hi,
>> >> I found there are some FAIL ld test cases with message like "sorry -
>> >> this program has been built without plugin support", and the program
>> >> in this case is ar. I think it's because I configured/built binutils
>> >> without "--enable-plugins", the question is:
>> >> should we skip these kind of tests if plugins isn't enabled?
>> >
>> > Actually the real question is why are we enabling plugins for ld
>> > but not ar?
>>
>> Thanks Alan, is it possible for binutils to have different plugin
>> enabling for sub-programs?
>
> In ld/configure.ac we have:
>
> # Check for dlopen support and enable plugins if possible.
> enable_plugins=yes
> AC_CHECK_HEADER([dlfcn.h],[],[enable_plugins=no],[AC_INCLUDES_DEFAULT])
> AC_SEARCH_LIBS([dlopen],[dl],[],[enable_plugins=no],[])
> AC_CHECK_FUNCS([dlopen dlsym dlclose],[],[enable_plugins=no])
> # We also support plugins on Windows (MinGW).
> if test x$enable_plugins = xno ; then
> AC_CHECK_HEADERS([windows.h],[enable_plugins=yes],[],[AC_INCLUDES_DEFAULT])
> fi
> AM_CONDITIONAL([ENABLE_PLUGINS], [test x$enable_plugins = xyes])
>
> So ld plugin support is always enabled, even when you configure with
> --disable-plugins. That seems wrong to me.
Hi Alan, I searched around and found out that there was bug report on
this before at https://sourceware.org/bugzilla/show_bug.cgi?id=12402
It was resolved as invalid and said this is designed behavior, though
I am not convinced.
With this, the only choice is to enable-plugin for binutils?
Thanks,
bin
>
> --
> Alan Modra
> Australia Development Lab, IBM
next prev parent reply other threads:[~2014-08-12 2:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 6:26 Bin.Cheng
2014-08-11 7:55 ` Alan Modra
2014-08-11 8:21 ` Bin.Cheng
2014-08-11 12:59 ` Alan Modra
2014-08-12 2:52 ` Bin.Cheng [this message]
2014-08-12 4:45 ` Alan Modra
2014-08-12 5:00 ` Bin.Cheng
2014-08-12 13:14 ` Alan Modra
2014-08-13 5:58 ` Bin.Cheng
2014-08-14 4:25 ` Alan Modra
2014-08-14 14:48 ` Hans-Peter Nilsson
2014-08-15 3:29 ` Alan Modra
2014-08-15 5:29 ` Bin.Cheng
2014-08-15 9:45 ` Bin.Cheng
2014-08-15 15:17 ` Hans-Peter Nilsson
2014-08-15 15:41 ` Hans-Peter Nilsson
2014-08-19 2:28 ` Bin.Cheng
2014-08-19 3:43 ` Hans-Peter Nilsson
2014-08-19 12:29 ` Alan Modra
2014-08-19 13:00 ` Hans-Peter Nilsson
2014-08-19 2:52 ` [PATCH] Regenerate gdb/configure (Re: Skip ld/lto tests if plugins is disabled for binutils?) Yao Qi
2014-08-19 3:36 ` Yao Qi
2014-08-19 6:33 ` Joel Brobecker
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=CAHFci28bf7N3ELc-n8ObrrVMONPVQsf1QfQSrJXJnD4ESFbB7g@mail.gmail.com \
--to=amker.cheng@gmail.com \
--cc=binutils@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).