Wait, isn't the compiler trying to remind us that 0x80 does not actually fit in a char? (It doesn't.) Wouldn't the correct fix actually be to define log4cxx::logchar as unsigned char, instead of char?
On Thu, Feb 21, 2019 at 5:44 AM Thorsten Schöning <tschoen...@am-soft.de> wrote: > Guten Tag Noory, Robert, > am Freitag, 21. Dezember 2018 um 16:33 schrieben Sie: > > > I found an issue with log4cxx built from sources on Ubuntu 18.04 > > (gcc 7.3). When I execute "make check", I get the error shown below. > > Thanks for reporting. The problem should be fixed now using the same > approach like in the past instead of applying your patch directly, > simply to be more consistent. > > https://issues.apache.org/jira/browse/LOGCXX-400 > > Mit freundlichen Grüßen, > > Thorsten Schöning > > -- > Thorsten Schöning E-Mail: thorsten.schoen...@am-soft.de > AM-SoFT IT-Systeme http://www.AM-SoFT.de/ > > Telefon...........05151- 9468- 55 > Fax...............05151- 9468- 88 > Mobil..............0178-8 9468- 04 > > AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln > AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow > >
