This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: ping^5: plugin directory

From: Matthias Klose <doko at ubuntu dot com>
To: Basile Starynkevitch <basile at starynkevitch dot net>
Cc: gcc-patches at gcc dot gnu dot org
Date: Wed, 24 Mar 2010 14:18:00 +0100
Subject: Re: ping^5: plugin directory
References: <4B9E8837.7040007@starynkevitch.net> <d1e3ff2b1003160019l75a18effw73728cf3be1b314f@mail.gmail.com> <4B9F3B82.2050601@starynkevitch.net>

On 16.03.2010 09:04, Basile Starynkevitch wrote:
[...]

the patch in its current form doesn't search in a default location; only if -iplugindir is passed to the driver, a plugin directory is searched. If -iplugindir is not passed, plugins are not found. Is this intended?

what is the motivation of adding an extra "libexec"? the values given to -iplugindir isn't really the plugin directory, but some kind of prefix.

The default for the plugin directory should be

<exec_prefix>/<alias>/<version>/plugin

Is it really necessary to append "libexec" to this path? It doesn't hurt, but now the exec prefix is encoded twice in the path.

Matthias

Follow-Ups:
- Re: ping^5: plugin directory
  - From: Richard Guenther

References:
- ping^5: plugin directory
  - From: Basile Starynkevitch
- Re: ping^5: plugin directory
  - From: Laurynas Biveinis
- Re: ping^5: plugin directory
  - From: Basile Starynkevitch

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]