Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Paul_Koning@Dell.com
Cc: gdb@sourceware.org
Subject: Re: GDB on Mac OS
Date: Wed, 12 Aug 2015 13:59:00 -0000	[thread overview]
Message-ID: <20150812135946.GL22225@adacore.com> (raw)
In-Reply-To: <95D02D49-26D2-454E-8E11-70EBF7CB5EC5@dell.com>

> > 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


  parent reply	other threads:[~2015-08-12 13:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12  0:15 Paul_Koning
     [not found] ` <20150812031208.GJ22225@adacore.com>
2015-08-12 13:38   ` Paul_Koning
2015-08-12 13:53     ` Jonas Maebe
2015-08-12 13:59     ` Joel Brobecker [this message]
2015-08-12 14:06       ` Paul_Koning
2015-08-12 15:14         ` Joel Brobecker
2015-08-12 15:35           ` Stan Shebs

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=20150812135946.GL22225@adacore.com \
    --to=brobecker@adacore.com \
    --cc=Paul_Koning@Dell.com \
    --cc=gdb@sourceware.org \
    /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