linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@mvista.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Patch for PCORE on linuxppc_2_4_devel
Date: Mon, 07 Apr 2003 11:22:26 -0700	[thread overview]
Message-ID: <3E91C1E2.4060502@mvista.com> (raw)
In-Reply-To: <20030407174355.GD16622@ip68-0-152-218.tc.ph.cox.net>


Tom Rini wrote:

>On Fri, Apr 04, 2003 at 06:12:17PM -0700, Mark A. Greer wrote:
>
>
>
>>This patch does the following:
>>a) Modifies the CONFIG_MORE_COMPILE_OPTIONS setup at the bottom of
>>arch/ppc/config.in.  The way that it was didn't work well and seemed
>>difficult to read.  I believe that the new way is "more correct" and
>>easier to understand
>>
>>
>
>Didn't work well when?  Then intent is that if you don't select this
>option, you still get -g added when CONFIG_KGDB=y so that you can
>effectivly use gdb.
>
Try playing with it a little...

I understand the intent, it just didn't work well.  The option is still
there with a reasonable default.  If they want it, they can use it; if
they don't, they don't.  If they don't know that they probably want -g
if they have KGDB, they'll find out soon enough.  Simple.

Mark


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-04-07 18:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-05  1:12 Patch for PCORE on linuxppc_2_4_devel Mark A. Greer
2003-04-07 17:43 ` Tom Rini
2003-04-07 18:22   ` Mark A. Greer [this message]
2003-04-07 20:10     ` Tom Rini
2003-04-07 20:59       ` Mark A. Greer

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=3E91C1E2.4060502@mvista.com \
    --to=mgreer@mvista.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).