linux-kernel - Re: [POWERPC] Fix for assembler -g

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070820202356.GA31712@redhat.com>
Date:	Mon, 20 Aug 2007 16:23:56 -0400
From:	Dave Jones <davej@...hat.com>
To:	Roland McGrath <roland@...hat.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Paul Mackerras <paulus@...ba.org>
Subject: Re: [POWERPC] Fix for assembler -g

On Mon, Aug 20, 2007 at 01:18:18PM -0700, Roland McGrath wrote:
 > > I'm still seeing failures with this.
 > > http://koji.fedoraproject.org/koji/getfile?taskID=110854&name=build.log
 > > shows..
 > > 
 > > lparmap.c: Assembler messages:
 > > lparmap.c:84: Error: file number 1 already allocated
 > > make[1]: *** [arch/powerpc/kernel/head_64.o] Error 1
 > > 
 > > Anything I can provide to help diagnose this?
 > 
 > 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!  (I committed the right one to
 > Fedora, which you'd think would help Dave, but no.)
 
Ahh, my eyes missed that the one upstream was subtley different, so I
dropped the one you committed to Fedora without trying it.
In a way though, good thing, or mainline would have continued to be
broken :)

	Dave

-- 
http://www.codemonkey.org.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/