From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 50520 invoked by alias); 12 Aug 2015 13:59:53 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 50511 invoked by uid 89); 12 Aug 2015 13:59:52 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Wed, 12 Aug 2015 13:59:50 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 8B31C2906E; Wed, 12 Aug 2015 09:59:48 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 4vZz1RxEGxhc; Wed, 12 Aug 2015 09:59:48 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 6526B29063; Wed, 12 Aug 2015 09:59:48 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id EB9F146992; Wed, 12 Aug 2015 06:59:46 -0700 (PDT) Date: Wed, 12 Aug 2015 13:59:00 -0000 From: Joel Brobecker To: Paul_Koning@Dell.com Cc: gdb@sourceware.org Subject: Re: GDB on Mac OS Message-ID: <20150812135946.GL22225@adacore.com> References: <1739A299-ACE9-4D7F-A1DF-E64C89ECC8D1@dell.com> <20150812031208.GJ22225@adacore.com> <95D02D49-26D2-454E-8E11-70EBF7CB5EC5@dell.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <95D02D49-26D2-454E-8E11-70EBF7CB5EC5@dell.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2015-08/txt/msg00019.txt.bz2 > > The fact that it has build warnings is not too surprising. Outside > > of GNU/Linux, I'm not sure it's building warning-free on any > > other host. Building with --disable-werror is how we do it. > > Ok, but it would make sense for the default configure to select the > correct compile options that the build will run to completion. This is really a separate discussion, but my take on it is that the goal is to have warning-free builds on all platforms. Turning this feature off for some targets would hide those warnings away, and reduce our chances of anyone working on them. Building a snapshot of the day is considered to be building GDB in developer mode, so the warnings are fatal by default. If you were to build from a release or from a release branch, on the other hand, the configure settings have been changed to make the warnings non-fatal. Note that having a warning-free build is not entirely within GDB's control. For instance, you'll need a certain version of bison for it to generate files that compile warning-free. I don't believe it is worth spending time trying to come up with a list of tests that will tell us whether warnings should be fatal or not. > So is that the reason why so many tests fail? I know of the > codesigning requirement from actually using the debugger (or rather, > answering the prompt for my password, which is the alternative). > Where would I look for information on how to do this? It would seem > logical for “make check” either to do it, or to report that it needs > to be done. I'm not a specialist, but I don't think codesigning can happen automagically. Codesigning requires for instance the name of a certificate, which is yours to choose. Creating that certificate involves the use of graphical tools. That's why we left the codesigning to the user - especially since the binaries are transportable but the codesigning needs to be redone on every machine to match the certificates provided by each machine. https://sourceware.org/gdb/wiki/BuildingOnDarwin -- Joel