xylib: fatal error: 'tr1/memory' file not found

[laew_rena24@…]

The building failed in Maverick OS X 10.9. The main.log shows that

:info:configure checking tr1/memory usability... no
:info:configure checking tr1/memory presence... no
:info:configure checking for tr1/memory... no
.
.
.
.
.
:info:build ./cache.h:31:11: fatal error: 'tr1/memory' file not found
:info:build # include <tr1/memory>
:info:build           ^
:info:build 1 error generated.
:info:build make[2]: *** [cache.lo] Error 1
:info:build make[2]: *** Waiting for unfinished jobs....
:info:build mv -f .deps/gsas.Tpo .deps/gsas.Plo
:info:build mv -f .deps/brucker_raw.Tpo .deps/brucker_raw.Plo
:info:build mv -f .deps/xylib.Tpo .deps/xylib.Plo
:info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_xylib/xylib/work/xylib-1.2/xylib'
:info:build make[1]: *** [all-recursive] Error 1
:info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_xylib/xylib/work/xylib-1.2'
:info:build make: *** [all] Error 2

[uvw2@…]

I make a patch attached this ticket (attachment:xylib.patch​), but this patch is just a quick hack. In my Mac (mavericks 10.9 and Xcode 5), xylib can be compiled as follows:

Patch file of xylib.patch is downloaded in Downloads folder (~/Downloads/). In Terminal.app,

cd /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/math/xylib
sudo patch -p1 < ~/Downloads/xylib.patch
sudo port install xylib

Is this patch right?

[ryandesign (Ryan Carsten Schmidt)]

Replying to uvw2@…:

Is this patch right?

I don't think so. Whereas before it was using system includes, you've changed it to use boost includes.

But I am not a C/C++ programmer; this problem needs to be solved by the developers of xylib. I have ​reported the problem to them.

[laew_rena24@…]

Replying to ryandesign@…:

Replying to uvw2@…:

Is this patch right?

I don't think so. Whereas before it was using system includes, you've changed it to use boost includes.

But I am not a C/C++ programmer; this problem needs to be solved by the developers of xylib. I have ​reported the problem to them.

What about fityk, is it running very well with this patch?

[wojdyr@…]

Hello, upstream developer here. I think this patch will work. Any shared_ptr should do, it can be from <tr1/memory> or from <memory> or from <boost/tr1/memory.hpp> or from <boost/shared_ptr.hpp>, wherever it is present.

The problem is caused by a bug in configure script, it will be fixed in the next release.

[uvw2@…]

Replying to laew_rena24@…:

Replying to ryandesign@…:

Replying to uvw2@…:

Is this patch right?

I don't think so. Whereas before it was using system includes, you've changed it to use boost includes.

But I am not a C/C++ programmer; this problem needs to be solved by the developers of xylib. I have ​reported the problem to them.

What about fityk, is it running very well with this patch?

Unfortunately, the building of fityk failed in OS X 10.9, regardless of xylib.

[ryandesign (Ryan Carsten Schmidt)]

Replying to wojdyr@…:

Hello, upstream developer here. I think this patch will work. Any shared_ptr should do, it can be from <tr1/memory> or from <memory> or from <boost/tr1/memory.hpp> or from <boost/shared_ptr.hpp>, wherever it is present.

The problem is caused by a bug in configure script, it will be fixed in the next release.

I'd rather apply your upstream patch; done in r113354.

[laew_rena24@…]

Replying to ryandesign@…:

Replying to wojdyr@…:

Hello, upstream developer here. I think this patch will work. Any shared_ptr should do, it can be from <tr1/memory> or from <memory> or from <boost/tr1/memory.hpp> or from <boost/shared_ptr.hpp>, wherever it is present.

The problem is caused by a bug in configure script, it will be fixed in the next release.

I'd rather apply your upstream patch; done in r113354.

It's correct, the building of fityk failed in OS X 10.9, the file.log is attached it…

[ryandesign (Ryan Carsten Schmidt)]

This ticket is about xylib and is resolved. The fityk ticket is #41218.