Bug#892861: libglm-dev: removal of default type initialization breaking packages

Guus Sliepen guus at debian.org
Wed Mar 28 20:12:35 UTC 2018


tags 892861 - wontfix
thanks

On Wed, Mar 28, 2018 at 01:19:44PM +1300, Andrew Caudwell wrote:

> Upstream has implemented my suggestion to re-add default initialization as
> opt-in via a new define:
> 
> https://github.com/g-truc/glm/issues/735
> https://github.com/g-truc/glm/commit/8390a77b3a278b15259e5ca6e67f7e41badc457b
> 
> Could you apply the commit as a patch so maintainers can then define
> GLM_FORCE_CTOR_INIT and avoid having to modifying code?

Sure. However, I'm running into problems trying to apply the patch: it
doesn't apply cleanly on 0.9.9~a2, and if I just package the latest
revision from git, then I am getting internal compiler errors from GCC.
I can still compile 0.9.9~a2 without problems, so I will try to see if I
can just adapt the commit which adds GLM_FORCE_CTOR_INIT to 0.9.9~a2.

> Let me know as then I can then avoid having to embed the current release in
> my software.

Yeah, that would be less than optimal.

-- 
Met vriendelijke groet / with kind regards,
      Guus Sliepen <guus at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/debian-science-maintainers/attachments/20180328/57ab3ab4/attachment.sig>


More information about the debian-science-maintainers mailing list