On 5/28/2017 3:37 AM, niXman wrote:
Edward Diener 2017-05-27 23:37:
Hi,
Do I use msys2 in order to build libbacktrace ? When building do I
need to use the version of mingw-64/gcc for which I will be using
libbacktrace when I eventually use mingw-64/gcc as my compiler ? If I
need to do that do I just add the mingw-64/gcc compiler to the
beginning of my msys2 path ?
I have used various versions of mingw-64/gcc binaries in order to test
Boost libraries but I have never built another library for use by any
particular version of mingw-64/gcc, which is why I am asking these
questions.
You can just use the mingw-builds[1] scripts that are used to build the
official mingw-w64 toolchains.
But the problem is yesterday I rebuild gcc-7-branch and in the logs of
the builbing I can see libbacktrace has successfully builded, but not
installed.
In accordance with this message[2], the libbacktrace should not be
installed in the destination directory because the developers find an it
inner instrument of GCC.
Are you essentially saying that:
1) libbacktrace can not be part of a mingw-64 distribution because it
relies on gcc files which are not part of mingw-64 ?
2) libbacktrace can be part of a mingw-64 distribution but relies on
other files in that distribution ?
I see in [2] below that there was a discussion of making libbacktrace
standalone, but it appears that in the 4 years from that discussion that
it was never followed through.
[1] https://github.com/niXman/mingw-builds
[2] https://gcc.gnu.org/ml/gcc/2013-05/msg00174.html
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
