Re: ping^5: plugin directory

[Matthias Klose <doko at ubuntu dot com>]

On 24.03.2010 14:30, Richard Guenther wrote:
> On Wed, Mar 24, 2010 at 2:18 PM, Matthias Klose<doko@ubuntu.com>  wrote:
> > 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.
>
> If any we should simply search where we find crt*.o and friends.  No
> need for yet-another-option.  Thus, simply lib/gcc/<alias>/<version>/.
> Or maybe where we find cc1 and friends.

yes, I missed the "gcc/" subdir. No strong opinion on <exec_prefix> or <prefix>.
Why not use the plugin subdir? Is this only meant to be used for the development 
files? It would avoid errors for things like -fplugin=libstdc++ and other shared 
libs installed in this location.

  Matthias