On 27/09/14 16:05, Zolnai Tamás wrote:
2014-09-27 15:23 GMT+02:00 Miklos Vajna <vmiklos@collabora.co.uk
<mailto:vmiklos@collabora.co.uk>>:
On Sat, Sep 27, 2014 at 08:26:38AM +0200, Zolnai Tamás
<zolnaitamas2000@gmail.com <mailto:zolnaitamas2000@gmail.com>>
wrote:
> So the only question is:
> Is it possible to replace the 4.3.1 and 4.3.2 linux packages with
new ones
> which are compiled with newer compilers? (expecting this is the
problem)
> To fix the bug mentioned above.
Isn't it possible to stick to boost::shared_ptr on -4-3, given that's
what other code does?
It's the collada2gltf code which uses std::shared_ptr at many places so
it would be much work to replace all of them with boost::shared_ptr, but
actually can be done if necessary. I just thought packages are created
with newer compilers, since they generate more better output (in theory).
Other thing is that I need to know whether this is the problem indeed.
So can I know what compilers are used for packages? Are they support
std::shared_ptr?
for LO 4.3 and earlier releases the RHEL5 gcc is used, i don't remember
if it is gcc 4.1 or 4.4; we're only switching to a C++11 compiler for LO
4.4.
actually most users will use the distro provided LO packages anyway and
those don't suffer from our ancient upstream RHEL5 baseline.
anyway, std::shared_ptr and boost::shared_ptr should be mostly the same,
so "find ... | xargs sed -i ..." should be able to fix things up quite
quickly to get a patch for the 4.3 branch.
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.