setBfree 0.8.2

Robin Gareus robin at gareus.org
Mon Jun 20 21:24:07 UTC 2016


On 06/20/2016 09:29 PM, Jaromír Mikeš wrote:
> 2016-06-20 21:09 GMT+02:00 Jaromír Mikeš <mira.mikes at gmail.com>:
>> 2016-06-20 20:28 GMT+02:00 Robin Gareus <robin at gareus.org>:
>>> Hi Mira,
>>>
>>> The problem is "-fPIE -pie" that is add (probably to LDFLAGS) by packaging.
>>>
>>> "These options are similar to -fpic and -fPIC, but generated position
>>> independent code can be only linked into executables." [1]
>>>
>>> The plugin is *not* an executable. It's a shared object.
>>>
>>> If needed I could special case LDFLAGS for binaries and LDFLAGS for
>>> plugins, but I don't see a good case for it. Is there some debian policy
>>> for that?
> 
> Hi again Robin,
> 
> I am not sure if "special case LDFLAGS for binaries and LDFLAGS for
> plugins" is usual coding practice.
> But it would solve this.
> I am giving list in copy maybe someone will comment on this issue.
> 
> BTW same is x42-plugins and qmidiroute ... where -fPIC and -fPIE conflicting
> 

I expect some other packages that build both binaries (e.g
jack-application) and shared-objects (plugins) from the same source will
have this issue.

Ardour probably as well, since it includes some libraries (libardour),
plugins (panners, rsynth) as well as a binary.

In any case what is the benefit or policy in this case?

Another alternative is to push -fPIE upstream, plugins usually include
-fPIC anyway, so upstream could add -fPIE.

ciao,
robin





More information about the pkg-multimedia-maintainers mailing list