From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id 3C798386EC42 for ; Mon, 29 Jun 2020 18:27:45 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 3C798386EC42 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=gnu.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=eliz@gnu.org Received: from fencepost.gnu.org ([2001:470:142:3::e]:36213) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jpyVM-0000k6-5f for gdb-patches@sourceware.org; Mon, 29 Jun 2020 14:27:44 -0400 Received: from [176.228.60.248] (port=2259 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jpyVJ-00008a-Qf for gdb-patches@sourceware.org; Mon, 29 Jun 2020 14:27:42 -0400 Date: Mon, 29 Jun 2020 21:27:32 +0300 Message-Id: <83a70l20dn.fsf@gnu.org> From: Eli Zaretskii To: gdb-patches@sourceware.org Subject: Building today's snapshot of GDB with MinGW X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2020 18:27:46 -0000 At Joel's request I've built today's (29 June) snapshot of GDB using mingw.org's MinGW and GCC 9.2.0. There are a few issues I bumped into related to Gnulib and MinGW runtime (which I recently upgraded to a newer version), and I'm still working on those. So what's below is an interim report of issues related to GDB itself: 1. The configure script doesn't allow --with-static-standard-libraries when GDB is built with source-highlight. Is this limitation going to stay (and if so, why), or could it be lifted? (I needed to hack the configure script to get past the error message.) 2. Building in libctf produces the same errors I reported back in February for GDB 9.1. I thought the libctf developer fixed them up-stream (or was I dreaming?), so why isn't the fix in our repository? I fixed those exactly as I fixed them for GDB 9.1. 3. "make TAGS" in the gdb/ directory fails because HFILES_NO_SRCDIR includes files that no longer exist: gdb_select.h and tui/tui-windata.h. Once these are removed from the list, TAGS is built. 4. Running "maint selftests" produces several warnings and failures: warning: A handler for the OS ABI "Windows" is not built into this configuration of GDB. Attempting to continue with the default i386:x86-64 settings. warning: A handler for the OS ABI "Windows" is not built into this configuration of GDB. Attempting to continue with the default i386:x64-32 settings. warning: A handler for the OS ABI "Windows" is not built into this configuration of GDB. Attempting to continue with the default i8086 settings. warning: A handler for the OS ABI "Windows" is not built into this configuration of GDB. Attempting to continue with the default i386:x86-64:intel settings. warning: A handler for the OS ABI "Windows" is not built into this configuration of GDB. Attempting to continue with the default i386:x64-32:intel settings. warning: A handler for the OS ABI "Windows" is not built into this configuration of GDB. Attempting to continue with the default i386:x86-64:nacl settings. warning: A handler for the OS ABI "Windows" is not built into this configuration of GDB. Attempting to continue with the default i386:x64-32:nacl settings. Self test failed: self-test failed at unittests/format_pieces-selftests.c:37 Self test failed: self-test failed at utils.c:2971 Self test failed: arch i386:x86-64: Cannot access memory at address 0x0 Self test failed: arch i386:x64-32: Cannot access memory at address 0x0 Self test failed: arch i386:x86-64:intel: Cannot access memory at address 0x0 Self test failed: arch i386:x64-32:intel: Cannot access memory at address 0x0 Self test failed: arch i386:x86-64:nacl: Cannot access memory at address 0x0 Self test failed: arch i386:x64-32:nacl: Cannot access memory at address 0x0 Self test failed: self-test failed at selftest-arch.c:85 warning: Could not recognize version of Intel Compiler in: "Intel(R) foo bar" Self test failed: Could not convert character to `UTF-8' character set Self test failed: self-test failed at unittests/scoped_fd-selftests.c:80 Is this something I should investigate? (I have never before run selftests in the MinGW build, so I have no "prior art" to compare with.) That's all for now. HTH.