All of lore.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Roland McGrath <roland@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Dave Jones <davej@redhat.com>, Paul Mackerras <paulus@samba.org>
Subject: Re: [POWERPC] Fix for assembler -g
Date: Mon, 20 Aug 2007 23:28:33 +0200	[thread overview]
Message-ID: <7666a3cee89296540b8ade4bedc1e52e@kernel.crashing.org> (raw)
In-Reply-To: <20070820201818.A68C54D05F2@magilla.localdomain>

> Hmm.  Check the V=1 make output to see that the lparmap.c really got 
> the -g0.
> The log says it didn't.  Oops!  It looks like the patch that got 
> committed is
> the one that sets CFLAGS_lparmap.s, but really it needs to set
> CFLAGS_lparmap.o instead (go kbuild).  Did I post the wrong one?  
> (It's only
> one letter different.)  Sorry about that!

But there is no lparmap.o!  lparmap.s is the generated file.

Maybe the best fix is

	$(obj)/lparmap.s: CFLAGS += -g0

This whole, erm, "cleverness" will go away soon fwiw.


Segher


  parent reply	other threads:[~2007-08-20 21:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200708181959.l7IJxJ5q020206@hera.kernel.org>
2007-08-20 20:08 ` [POWERPC] Fix for assembler -g Dave Jones
2007-08-20 20:18   ` Roland McGrath
2007-08-20 20:23     ` Dave Jones
2007-08-20 21:29       ` Segher Boessenkool
2007-08-20 21:35         ` Roland McGrath
2007-08-20 22:26           ` Segher Boessenkool
2007-08-20 21:28     ` Segher Boessenkool [this message]
2007-08-20 21:32       ` Roland McGrath
2007-08-20 22:29         ` Segher Boessenkool
2007-08-25 13:02           ` Sam Ravnborg
2007-08-25 13:56             ` Segher Boessenkool
2007-08-20 23:14     ` Paul Mackerras

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=7666a3cee89296540b8ade4bedc1e52e@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=roland@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.