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

Re: gcc plugins and rebuilds

Ricardo Mones, le Wed 21 Mar 2012 18:16:04 +0100, a écrit :
> On Wed, Mar 21, 2012 at 05:33:23PM +0100, Samuel Thibault wrote:
> > Hello,
> > 
> > One of my packages (starpu) will ship a gcc plugin (already in
> > experimental).  The problem is that the gcc plugin infrastructure checks
> > for exact version matching (in plugin_default_version_check()), i.e.
> > plugins are supposed to be loaded only by the exact gcc that built it.
> > That would mean that we have to rebuild the package on each gcc upload.
> > Some other packages shipping plugins, such as dragonegg, bypass the test
> > if some environment variable is set by the user, but that is really not
> > safe.
> > 
> > I'm afraid we will just have to rebuild each time?
>   Looks that's the same that happens with claws-mail and the plugins
> shipped in claws-mail-extra-plugins. But unless the version check includes
> the Debian revision you only have to rebuild when gcc upstream version
> changes, not every upload.

Apparently the check includes hashes that are unique to the build.


Reply to: