linux-kernel - linux-next: build failure in dwarf-regs.c

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>] [day] [month] [year] [list]

Message-ID: <CAOvdn6WemnDgO4wb5xutMiVBVTrZUrX3Nn8hQXVsJML6cRMPcg@mail.gmail.com>
Date:	Mon, 1 Oct 2012 21:10:57 -0400
From:	Ben Guthro <ben.guthro@...il.com>
To:	Ian Munsie <imunsie@...ibm.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: linux-next: build failure in dwarf-regs.c

I pulled the latest bits up to
797b9e5ae93270ec27a1f1ed48cd697d01b2269f - but am seeing the following
build failure with gcc 4.6.3

 CC arch/x86/util/dwarf-regs.o
arch/x86/util/dwarf-regs.c:72:13: error: no previous prototype for
'get_arch_regstr' [-Werror=missing-prototypes]
cc1: all warnings being treated as errors
make[3]: *** [arch/x86/util/dwarf-regs.o] Error 1
make[3]: Leaving directory
`/data/home/bguthro/dev/orc-newdev.git/linux/build/tools/tools/perf'
make[2]: *** [build-linux-tools] Error 2
make[2]: Leaving directory `/data/home/bguthro/dev/orc-newdev.git/linux'
make[1]: *** [install-kernel] Error 2
make[1]: Leaving directory `/data/home/bguthro/dev/orc-newdev.git/orc-kernel'
make: *** [dist-kernels] Error 2


git blame shows that line coming in from the following changeset -
though April is a long time ago in kernel time - so this must have
come in with some other merge in this 3.7 window

commit cd932c593995abee1d1a8a0bfe608f7d103d87ad
Author: Ian Munsie <imunsie@...ibm.com>
Date:   Tue Apr 20 16:58:32 2010 +1000

    perf: Move arch specific code into separate arch directory

    The perf userspace tool included some architecture specific code to map
    registers from the DWARF register number into the names used by the regs
    and stack access API.

    This moves the architecture specific code out into a separate
    arch/x86 directory along with the infrastructure required to use it.

    Signed-off-by: Ian Munsie <imunsie@...ibm.com>
    Acked-by: Masami Hiramatsu <mhiramat@...hat.com>
    Signed-off-by: Paul Mackerras <paulus@...ba.org>


Apologies to Ian, who may reciece this multiple times, as I worked out
some email bounce issues with LKML
--
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/