* Arnaldo Carvalho de Melo <a...@redhat.com> wrote:
> Em Tue, Mar 10, 2015 at 11:03:31AM +0100, Ingo Molnar escreveu:
> > So I got this error today:
> >
> > ┌─Warning:───────────────────────────┐
> > │The vmlinux file can't be used. │
> > │Kernel samples will not be resolved.│
> > │ │
> > │ │
> > │Press any key... │
> > └────────────────────────────────────┘
> >
> > ... and sadly perf is being passive-aggressive again: being negative
> > but refusing to say why! :-)
>
> > Is there a way to figure out why it did not like the vmlinux?
>
> I'll check and improve the message.
>
> But you must've noticed that perf is going to a therapist, aka
> improving error messages... ;-)
Absolutely! ;-)
Also, on the positive side, today I was able to build and run perf on
ancient user-space: a Fedora Core 6 installation, with very few hacks
(see the attached hacks).
The HAVE_NEW_FLAX hack results in a non-working -e option.
Thanks,
Ingo
Index: tip/tools/perf/util/parse-events.c
===================================================================
--- tip.orig/tools/perf/util/parse-events.c
+++ tip/tools/perf/util/parse-events.c
@@ -968,6 +968,13 @@ perf_pmu__parse_check(const char *name)
return r ? r->type : PMU_EVENT_SYMBOL_ERR;
}
+#ifndef HAVE_NEW_FLEX
+static int parse_events_lex_init_extra(int start_token __maybe_unused, void
**scanner __maybe_unused)
+{
+ return -1;
+}
+#endif
+
static int parse_events__scanner(const char *str, void *data, int start_token)
{
YY_BUFFER_STATE buffer;
Index: tip/tools/perf/util/symbol-elf.c
===================================================================
--- tip.orig/tools/perf/util/symbol-elf.c
+++ tip/tools/perf/util/symbol-elf.c
@@ -53,6 +53,13 @@ static int elf_getphdrnum(Elf *elf, size
}
#endif
+#ifndef HAVE_ELF_GETPHDRNUM
+static int elf_getphdrnum (Elf *__elf __maybe_unused, size_t *__dst
__maybe_unused)
+{
+ return 1;
+}
+#endif
+
#ifndef NT_GNU_BUILD_ID
#define NT_GNU_BUILD_ID 3
#endif
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
