[uuid] stale 1.55 source/build
Hello,
I'm not 100% positive, I downloaded stale source and/or binary build
of boost 1.55, supposedly, but I am finding that tickets which were
reported to have been included in that version are not in the build.
I'll retrace my steps to find where that build came from, but I
seriously question whether this build included the latest 1.55 code.
i.e. uuid fixes, which I am finding are still happening in the download:
Error 1 error C4996: 'std::_Swap_ranges': Function call with
parameters that may be unsafe - this call relies on the caller to
check that the passed values are correct. To disable this warning, use
-D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++
'Checked Iterators' c:\program files (x86)\microsoft visual studio
12.0\vc\include\algorithm 925 1 xml
and with reported fixes:
https://svn.boost.org/trac/boost/attachment/ticket/9503/uuid.hpp
This is not in the code that I have.
i.e. typedef uint8_t value_type;
typedef uint8_t& reference;
typedef uint8_t const& const_reference;
typedef uint8_t* iterator;
typedef uint8_t const* const_iterator;
typedef std::size_t size_type;
typedef std::ptrdiff_t difference_type;
versus: typedef uint8_t value_type;
typedef std::array
Update: this is straight from the Boost downloads. First, the binaries
that are available are definitely different in size from the previous
file I downloaded. Not sure that's because of a workspace directory
what may have been intentionally or inadvertently included. Second,
still reflects code that is out of sync with the documented update, at
least where uuid, and likely several other spots, are concerns. Here
it is 7 months since the version was available and the issue is still
there. Would someone verify this please? Thank you...
On Sat, Jul 5, 2014 at 12:39 PM, Michael Powell
Hello,
I'm not 100% positive, I downloaded stale source and/or binary build of boost 1.55, supposedly, but I am finding that tickets which were reported to have been included in that version are not in the build.
I'll retrace my steps to find where that build came from, but I seriously question whether this build included the latest 1.55 code.
i.e. uuid fixes, which I am finding are still happening in the download:
Error 1 error C4996: 'std::_Swap_ranges': Function call with parameters that may be unsafe - this call relies on the caller to check that the passed values are correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See documentation on how to use Visual C++ 'Checked Iterators' c:\program files (x86)\microsoft visual studio 12.0\vc\include\algorithm 925 1 xml
and with reported fixes:
https://svn.boost.org/trac/boost/attachment/ticket/9503/uuid.hpp
This is not in the code that I have.
i.e. typedef uint8_t value_type; typedef uint8_t& reference; typedef uint8_t const& const_reference; typedef uint8_t* iterator; typedef uint8_t const* const_iterator; typedef std::size_t size_type; typedef std::ptrdiff_t difference_type;
versus: typedef uint8_t value_type; typedef std::array
data_type; typedef data_type::size_type size_type; typedef data_type::difference_type difference_type; typedef data_type::iterator iterator; typedef data_type::const_iterator const_iterator; typedef data_type::reference reference; typedef data_type::const_reference const_reference; in the reported patch.
In two attempts to 1) build from source myself, 2) download read-built binaries, both have stale versions of source, without the reported patches.
This is not the first time I've encountered such an issue, with the first being failure to build from source several weeks ago now at least.
What with the Git submodule advances, could it be Git submodule(s) were not updated or something along those lines? Any thoughts? Recommendations where to find a reliable 1.55 build?
Thank you...
Best regards,
Michael Powell
"Michael Powell"
I'm not 100% positive, I downloaded stale source and/or binary build of boost 1.55, supposedly, but I am finding that tickets which were reported to have been included in that version are not in the build.
and with reported fixes:
https://svn.boost.org/trac/boost/attachment/ticket/9503/uuid.hpp
That ticket was created after 1.55 was released. "Version: Boost 1.55.0" means that the reported problem is in that version. Also, the suggested code was rejected and the ticket was closed with "wontfix". The developer suggested to define _SCL_SECURE_NO_WARNINGS to solve the problem.
What with the Git submodule advances, could it be Git submodule(s) were not updated or something along those lines? Any thoughts? Recommendations where to find a reliable 1.55 build?
Git wasn't used for 1.55. Regards, Niklas Angare
Thanks for the clarification. I ended up following the suggested fix.
On Fri, Jul 11, 2014 at 6:36 PM, Niklas Angare
"Michael Powell"
wrote: I'm not 100% positive, I downloaded stale source and/or binary build of boost 1.55, supposedly, but I am finding that tickets which were reported to have been included in that version are not in the build.
and with reported fixes:
https://svn.boost.org/trac/boost/attachment/ticket/9503/uuid.hpp
That ticket was created after 1.55 was released. "Version: Boost 1.55.0" means that the reported problem is in that version. Also, the suggested code was rejected and the ticket was closed with "wontfix". The developer suggested to define _SCL_SECURE_NO_WARNINGS to solve the problem.
What with the Git submodule advances, could it be Git submodule(s) were not updated or something along those lines? Any thoughts? Recommendations where to find a reliable 1.55 build?
Git wasn't used for 1.55.
Regards,
Niklas Angare
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
participants (2)
-
Michael Powell
-
Niklas Angare