From: "gmail Vladimir Koković via Gdb-patches" <gdb-patches@sourceware.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: mingw --enable-tui
Date: Sun, 22 Nov 2020 17:19:49 +0100 [thread overview]
Message-ID: <562f0b99-1fd9-27d4-997e-d4e53c790d03@gmail.com> (raw)
In-Reply-To: <83h7phxvb0.fsf@gnu.org>
Hi,
checking build system type... x86_64-pc-linux-gnu
checking host system type... i686-w64-mingw32
checking target system type... i686-w64-mingw32
make[1]: Entering directory
'/home/vlada/AUR/mingw-w64-gdb/mingw-w64-gdb/vk/build-i686-w64-mingw32'
...
CXX tui/tui-regs.o
CXX tui/tui-source.o
CXX tui/tui-stack.o
CXX tui/tui-win.o
CXX tui/tui-wingeneral.o
CXX tui/tui-winsource.o
CXX tui/tui.o
...
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-w64-mingw32
checking target system type... x86_64-w64-mingw32
...
CXX tui/tui-regs.o
CXX tui/tui-source.o
CXX tui/tui-stack.o
CXX tui/tui-win.o
CXX tui/tui-wingeneral.o
CXX tui/tui-winsource.o
CXX tui/tui.o
../../../src/gdb-10.1/gdb/tui/tui-win.c:130:1: error: narrowing
conversion of ‘2147483648’ from ‘chtype’ {aka ‘long long unsigned int’}
to ‘int’ [-Wnarrowing]
130 | };
| ^
../../../src/gdb-10.1/gdb/tui/tui-win.c:130:1: error: narrowing
conversion of ‘2483027968’ from ‘chtype’ {aka ‘long long unsigned int’}
to ‘int’ [-Wnarrowing]
make[2]: *** [Makefile:1614: tui/tui-win.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory
'/home/vlada/AUR/mingw-w64-gdb/mingw-w64-gdb/vk/build-x86_64-w64-mingw32/gdb'
make[1]: *** [Makefile:10078: all-gdb] Error 2
make[1]: Leaving directory
'/home/vlada/AUR/mingw-w64-gdb/mingw-w64-gdb/vk/build-x86_64-w64-mingw32'
make: *** [Makefile:866: all] Error 2
On 22.11.20. 16:31, Eli Zaretskii wrote:
>> Date: Sun, 22 Nov 2020 12:44:56 +0100
>> From: gmail Vladimir Koković via Gdb-patches
>> <gdb-patches@sourceware.org>
>>
>> I managed to make mingw cross build 32 and 64, but I had to change
>> gdb/tui//tui-win.c because of mingw64.
> Can you tell what was the problem you saw without that change?
>
> Thanks.
next prev parent reply other threads:[~2020-11-22 16:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-22 11:44 gmail Vladimir Koković via Gdb-patches
2020-11-22 12:13 ` gmail Vladimir Koković via Gdb-patches
2020-11-22 15:31 ` Eli Zaretskii via Gdb-patches
2020-11-22 16:19 ` gmail Vladimir Koković via Gdb-patches [this message]
2020-11-22 16:23 ` Eli Zaretskii via Gdb-patches
2020-11-22 16:35 ` gmail Vladimir Koković via Gdb-patches
2020-11-22 16:55 ` Eli Zaretskii via Gdb-patches
2020-11-22 17:06 ` gmail Vladimir Koković via Gdb-patches
2020-11-22 17:20 ` Tom Tromey
2020-11-22 18:24 ` Eli Zaretskii via Gdb-patches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=562f0b99-1fd9-27d4-997e-d4e53c790d03@gmail.com \
--to=gdb-patches@sourceware.org \
--cc=eliz@gnu.org \
--cc=vladimir.kokovic@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox