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

Hugo.Mildenberger at web.de Hugo.Mildenberger at web.de
Mon Mar 25 15:34:07 EDT 2013


Hi Boris,
  
   Boris Kolpackov <boris at codesynthesis.com> wrote:

  > If configure's libdir or libexecdir is a prefix of the GCC plugin 
  > directory (i.e., `gcc --print-file-name=plugin`), then ODB should
  > install there automatically. If that's the case but this doesn't
  > happen for you, then it is definitely a bug that I would like to
  > track down.
  > 
  > The test in question is in m4/gcc-plugin.m4, starts at line 63.
  
I've put some trace statements therein. This is the result:

|    checking whether to install ODB plugin into default GCC plugin directory... 
|               prefix='/usr'
|    ac_default_prefix='/usr/local'
|        e_exec_prefix='/usr'
|               libdir='/usr/lib64'
|             e_libdir='/usr/lib64'
|         e_libexecdir='/usr/libexec'
|            ld_suffix='/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.2/plugin'
|           led_suffix='/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.2/plugin'
|                  dir='/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.2/plugin'
|    no


  > Yes, as I said before, you would need to split the ODB compiler into
  > the driver package (/usr/bin/odb plus documentation) and plugin packages,
  > one for each version of GCC.

I hesitate to split up this package on the fly. I'd assumed that you thought about making the plugin a separate package?

 
  > Nop, at this stage I am only concerned with supporting multiple version
  > of GCC (so that if the user switches the GCC version, ODB will still work).

Ok, but you said so, before. 
 

  > Nop, we only guarantee things will work properly if the ODB compiler
  > driver and all the runtime libraries have exactly the same major and
  > minor version (i.e., X.Y in odb-X.Y.Z). Which means that to support
  > multiple ODB versions one would need to supports "switching" a lot
  > of libraries, headers, etc. I don't think this is worth the trouble 
  > at this stage. Let's first get a single ODB version working from the
  > official repository.

God willing...


Hugo




More information about the odb-users mailing list