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 DECA43851C11 for ; Tue, 30 Jun 2020 14:09:10 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org DECA43851C11 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]:50522) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jqGwg-0003gI-1z; Tue, 30 Jun 2020 10:09:10 -0400 Received: from [176.228.60.248] (port=3368 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jqGwe-0006oe-SR; Tue, 30 Jun 2020 10:09:09 -0400 Date: Tue, 30 Jun 2020 17:09:00 +0300 Message-Id: <83wo3ozlvn.fsf@gnu.org> From: Eli Zaretskii To: Christian Biesinger , Tom Tromey , simon.marchi@polymtl.ca, Joel Brobecker Cc: gdb-patches@sourceware.org In-Reply-To: (message from Christian Biesinger on Mon, 29 Jun 2020 15:36:50 -0500) Subject: Re: Building today's snapshot of GDB with MinGW References: <83a70l20dn.fsf@gnu.org> 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: Tue, 30 Jun 2020 14:09:12 -0000 > From: Christian Biesinger > Date: Mon, 29 Jun 2020 15:36:50 -0500 > Cc: gdb-patches > > > 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.) > > Looks like this was discussed before at > https://sourceware.org/pipermail/gdb-patches/2020-April/167388.html, > no real outcome AFAICT Tom, could you please share your views on this? You seemed to be saying there that we must link libstdc++ dynamically to support exceptions thrown by source-highlight, but could you perhaps add more details about the reasons? Also, do the problems you had in mind affect GDB that is linked statically with source-highlight, and if not, could we modify the configure script to allow that with "-static-libstdc++"? > > 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. > > So reading https://sourceware.org/bugzilla/show_bug.cgi?id=25155, Nick > mentioned an RFC patch, but I can't tell if that landed. Joel, should I install the same libctf patches we had in gdb-9.1-branch in the current master? Or would you like to talk to the upstream maintainer first? > > 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. > > This also happens on Linux. I guess few people use "make TAGS"... Any reason not to delete those 2 file names from the list? > > 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. > > Possibly related to > https://sourceware.org/pipermail/gdb-patches/2020-March/166678.html ? Simon, any chance you could look into this, or instruct me how to investigate?