[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/21423] New: ./configure --enable-plugins

From: dilyan.palauzov at aegee dot org
Subject: [Bug ld/21423] New: ./configure --enable-plugins
Date: Sun, 23 Apr 2017 22:32:20 +0000


            Bug ID: 21423
           Summary: ./configure --enable-plugins
           Product: binutils
           Version: 2.29 (HEAD)
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: ld
          Assignee: unassigned at sourceware dot org
          Reporter: dilyan.palauzov at aegee dot org
  Target Milestone: ---

I read in config/plugins.m4 that
-- plugins can be enabled only if either dlfcn.h or windows.h is present
-- plugins are enabled, except --disable-plugins is provided

Under these circumstances, where --enable-plugins is the default, ./configure
-help shall print "disable-plugins" to show the use, what action she has to
make, in order to enforce that option.

This is the convention for reading ./configure --help, in order to understand
what is the default, and for tweaking which features, an additional argument is

This is unfortunately not the default behaviour of gold/configure , so running
`binutils.git/configure` inconsistently disables plugin support in gold and
enables plugin support in ld.bfd.

Related to https://sourceware.org/bugzilla/show_bug.cgi?id=15599 and
https://sourceware.org/bugzilla/show_bug.cgi?id=12402 .  However, it is
irrelevant, whether ld/configure.ac includes config/plugins.m4 .  The fact that
./configure --help prints "--enable-plugins" means, that "--enable-plugins" has
to be provided in order to enable plugins.

I tried ./configure --disable-plugins and ld --plugin shows now "unrecognized

You are receiving this mail because:
You are on the CC list for the bug.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]