Re: Trouble cross-compiling GCC on Linux.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 4/26/2015 8:13 PM, Maxwell Dreytser wrote:
>
> I am having trouble compiling GCC 5.1.0 for Windows using Linux
> MinGW-w64.
> This is the error I am getting, along with the command that is being
> executed: http://paste.ubuntu.com/10904608/
>
> Configure line: ../gcc-5.1.0/configure  --build=x86_64-linux-gnu
> --prefix=/usr --includedir='/usr/include' --mandir='/usr/share/man'
> --infodir='/usr/share/info' --sysconfdir=/etc --localstatedir=/var
> --libexecdir='/usr/lib/gcc-mingw-w64' --disable-maintainer-mode
> --disable-dependency-tracking --prefix=/usr --enable-shared
> --enable-static --disable-multilib --with-system-zlib
> --libexecdir=/usr/lib --without-included-gettext --libdir=/usr/lib
> --enable-libstdcxx-time=yes --with-tune=generic
> --enable-version-specific-runtime-libs --enable-threads=posix
> --enable-fully-dynamic-string --enable-sjlj-exceptions
> --enable-libgomp --enable-languages=c,c++,fortran,objc,obj-c++
> --enable-lto --with-plugin-ld --target=x86_64-w64-mingw32
> --with-gxx-include-dir=/usr/include/c++/4.8
> --with-as=/usr/bin/x86_64-w64-mingw32-as
> --with-ld=/usr/bin/x86_64-w64-mingw32-ld
>
>
Where is your error report?
Did you not run into the 2 apparently erroneous usages of const char *
in winnt.c such as I reported in PR65835?
It seems adequate to use any ugly means for removing the const
attribute, but a clean fix would be appreciated.
I suppose the source code has been like that for some time but only
recently has there been checking.

-- 
Tim Prince





[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux