Hi,
I just wanted to say that I "solved" the problem for now by adding
--disable-libcc1
to the configure flags as suggested on the GCC's IRC channel.
For the other problem I opened a ticket:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78756
and moved the file manually in the "post-install" step of the package manage.
Mojca
On 9 December 2016 at 17:58, Mojca Miklavec wrote:
> Hello,
>
> I created packages for MinGW-w64 for MacPorts, but there's one more
> issue that I need to solve before I could publish the packages.
>
> Both i686-w64-mingw32-gcc and x86_64-w64-mingw32-gcc (created with
> "make && make install" from GCC) contain the same three files:
>
> /opt/local/lib/x86_64/libcc1.0.so
> /opt/local/lib/x86_64/libcc1.la
> /opt/local/lib/x86_64/libcc1.so
>
> I checked the configure flags for the (native) gcc6 package and that one uses
> --libdir=${prefix}/lib/gcc6
> to avoid the clash between different versions of gcc. But if I do the
> same for MinGW, the files end up under
> ${prefix}l/lib/x86_64-w64-mingw32/gcc/x86_64-w64-mingw32/
> which is somewhat suboptimal.
>
> How could I move those three files somewhere else?
>
> See also
> https://gcc.gnu.org/ml/gcc/2015-01/msg00190.html
> without a satisfactory answer.
>
> Another problem is the location of
> ${prefix}/share/info/gfortran.info
> which should have been
> ${prefix}/share/info/x86_64-w64-mingw32-gfortran.info
> but that one is at least easy to fix (it should nevertheless be
> reported upstream).
>
> Thank you,
> Mojca
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
