On Tue, 11 Jun 2019, Bruce Korb wrote:
> I should probably update the e-address as well. Yes, I still receive
> gnu.org email, but not daily. As infrequent as monthly. Can I do
> something to auto-forward it to an e-address I process daily?
You can log in to fencepost.gnu.org and edit /com/mailer/
On 5/31/19 12:15 PM, Jonathan Wakely wrote:
>> Alright, thanks for the hint. I was just following the instructions in
>> gcc-9.1.0/fixincludes/README:
>>
>> """
>> Please also send relevant information to gcc-b...@gcc.gnu.org,
>> gcc-patches@gcc.gnu.org and,
>> please, to me: bk...@gnu.org.
>> """
On 5/31/19 6:35 AM, Jonas Jelten wrote:
> This code snippet of mingw's stdio.h:
>
>
> #ifdef _WIN64
> _CRTIMP FILE *__cdecl __iob_func(void);
> #define _iob __iob_func()
> #else
> [.]
> #if (!defined(NO_OLDNAMES) || defined(__GNUC__))
> __MINGW_EXTENSION typedef __int64 fpos_t;
> #define
On 31/05/19 17:18 +0200, Jonas Jelten wrote:
On 31/05/2019 16.38, Jonathan Wakely wrote:
On 31/05/19 15:35 +0200, Jonas Jelten wrote:
Hi!
I'm trying to build the x86_64-w64-mingw64 crosscompiler on gentoo.
It breaks because a fixincludes-fix is applied at a place where it should not
be applie
On 31/05/2019 16.38, Jonathan Wakely wrote:
> On 31/05/19 15:35 +0200, Jonas Jelten wrote:
>> Hi!
>>
>> I'm trying to build the x86_64-w64-mingw64 crosscompiler on gentoo.
>> It breaks because a fixincludes-fix is applied at a place where it should
>> not be applied.
>>
>> This broke the cross-gcc
On 31/05/19 15:35 +0200, Jonas Jelten wrote:
Hi!
I'm trying to build the x86_64-w64-mingw64 crosscompiler on gentoo.
It breaks because a fixincludes-fix is applied at a place where it should not
be applied.
This broke the cross-gcc build for gcc-8.3.0 and 9.1.0 with error messages that
made i
