Test: gcc-14.2.1+20241102-0.1

[Thomas Wolff]

Am 04.11.2024 um 21:26 schrieb Brian Inglis via Cygwin:
> On 2024-11-04 12:00, ASSI wrote:
>> The native Gcc compilers have been updated to the latest upstream
>> snapshot version of the gcc-13 branch:
>>
>>   gcc-14.2.1+20241102
>>
>> This build incorporates the experimental v4 patch from T. Yano to use
>> the newlib locale function in libstdc++ so that other locales (aside
>> from "C") become usable.
>>
>> Cygwin does not allow multiple versions of the compilers to be installed
>> concurrently.
>>
>> For this build, the D compiler has been disabled since it does not
>> bootstrap due to the missing Phobos runtime on Cygwin.  No testing
>> beyond the compiler testsuite has been done.  Libgccjit is now building
>> and part of the release again.
>
> I realised there are docs provided only for gcc/g++, objc/objc++,
> gccint, gfortran, libgccjit, libgomp, libquadmath, but nothing for
> libstdc++, not even info or man pages.
>
> Is there any chance we could possibly get libstdc++.info* or man pages
> included with the build, or as (a) separate -doc package(s), and
> possibly other libraries or components where info or man pages are
> available, and may not currently be built or installed?
>
> I struggled to find any Cygwin or online docs mentioning libstdc++,
> until a poster linked:
>
> https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html,
>
> One upstream refuses to support distros that do not support C++20
> compilers!
>
> Given that cygwin/-devel is built with the old ABI, is there any point
> in trying to build libraries/packages that *require* the new ABI
> features in C++20?
>
> I am asking to adopt dependent orphaned packages, just so I *can*
> rebuild them with the new ABI, so is trying this exercise going to be
> futile?

Mintty fails to build with gcc-14 and gcc-15. There are some peculiar
settings of #define WINVER which mintty does for a purpose; however,
this was not a problem until gcc-13.
Thomas