Re: Bug#957532: mes: ftbfs with GCC-10

[Jan Nieuwenhuizen]

Vagrant Cascadian writes:

Hello!

> Control: forwarded 957532 bug-mes@gnu.org
> Control: tags 957532 upstream

> On 2020-04-17, Matthias Klose wrote:
>> The package fails to build in a test rebuild on at least amd64 with
>> gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
>> severity of this report will be raised before the bullseye release,
>> so nothing has to be done for the buster release.
>>
>> The full build log can be found at:
>> http://people.debian.org/~doko/logs/gcc10-20200225/mes_0.22-1_unstable_gcc10.log
>> The last lines of the build log are at the end of this report.
>>
>> To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
>> or install the gcc, g++, gfortran, ... packages from experimental.
>>
>>   apt-get -t=experimental install g++ 
>>
>> Common build failures are new warnings resulting in build failures with
>> -Werror turned on, or new/dropped symbols in Debian symbols files.
>> For other C/C++ related build failures see the porting guide at
>> http://gcc.gnu.org/gcc-10/porting_to.html
>>
>> [...]
>> /usr/bin/ld:
>> gcc-lib/libc.a(isatty.o):./gcc-lib/../include/mes/lib-mini.h:43:
>> multiple definition of `environ';
>> crt1.o:./gcc-lib/../include/mes/lib-mini.h:43: first defined here
>> /usr/bin/ld:

Ah yes, this used to be silently allowed.  This should be fixed
on master with commits 9a1c50c1cfa0218a62c556330e2882cb94a6cc18
and 84ff05a839fa39f07fe5f3ccf8dda396eae305c7.

Note that the "36-compare-arithmetic" test has broken, I'm looking into
that.

> Debian has switched to gcc 10 by default for the development releases,
> and that currently breaks building mes.
>
> Please let me know if there is anything I can do to help!

Thanks for the report and sorry for the delay!

Greetings,
Janneke

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com