[odb-users] odb-2.2.1 should install the odb.so plugin into $(gcc -print-file-name=plugin)

[Hugo.Mildenberger at web.de]

Hi Boris,

  On Wed, 6 Mar 2013 13:32:10 +0200
  Boris Kolpackov <boris at codesynthesis.com> wrote:

  > Probably a better approach would be for /usr/bin/odb to first check if
  > a GCC-specific version of the plugin was installed (i.e., run GCC with
  > -print-file-name=plugin and stat() odb.so in that directory). If one
  > exists, then pass that using absolute plugin path (so that it works
  > with GCC 4.5).

Yes, this would be a clean solution! 
 
  > > If gcc was built without plugin support, does -print-file-name=plugin
  > > result in an error condition? If so, one could base a run-time test
  > > on it, finally covering all cases. Else it's a GCC bug.
  > 
  > The point I am trying to make is that it is the host GCC (as opposed
  > to target GCC) that needs to be built with plugin support. And we can't
  > do any runtime checks with host GCC since we cannot run it.

And I was trying to say that one has to defer this test until ODB runs on the designated target machine ("run-time test"). The strategy you described above would cover this idea implicitly. 


Hugo