[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.1.10.0808191430010.28232@gandalf.stny.rr.com>
Date: Tue, 19 Aug 2008 14:33:27 -0400 (EDT)
From: Steven Rostedt <rostedt@...dmis.org>
To: Ingo Molnar <mingo@...e.hu>
cc: LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH] ftrace: update recordmount.pl arch changes
On Fri, 15 Aug 2008, Ingo Molnar wrote:
>
> * Steven Rostedt <rostedt@...dmis.org> wrote:
>
> > Ingo,
> >
> > I'm trying to keep all the arch changes in recordmcount.pl in one
> > place. I moved your code into that area, by adding the flags to the
> > commands that were passed in.
> >
> > Does this change still work for you when compiling i386 on a x86_64
> > box?
>
> actually, i thought of this as a quick hack to let -tip testing
> continue. Dont we have all the proper information available in kbuild
> and should just pass that to scripts/recordmcount.pl when called - like
> we pass in things like OBJDUMP which might have cross-build overrides,
> etc.
Ingo,
Could you use my updated patch. I know it is still just a work around, but
your update broke my build. I use distcc which passes in "distcc" as gcc.
My distcc is self built and is not the same as the distribution gcc.
Ie, you have:
if ($arch eq "x86_64") {
$ld = "ld -m elf_x86_64";
$objdump = "objdump -M x86-64";
$objcopy = "objcopy -O elf64-x86-64";
$cc = "gcc -m64";
}
Where the $cc = "gcc" is not compatible on my system. I end up with a bad
build that causes ftrace to fail on bootup.
-- Steve
--
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/
Powered by blists - more mailing lists