[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAE2F3rDw9fUut1QgTbxcEDhKXP7QjgdvBvJ4fgdD9MQ4mx4YLA@mail.gmail.com>
Date: Mon, 26 Sep 2016 11:51:34 -0700
From: Daniel Mentz <danielmentz@...gle.com>
To: Alexey Brodkin <Alexey.Brodkin@...opsys.com>
Cc: "Vineet.Gupta1@...opsys.com" <Vineet.Gupta1@...opsys.com>,
"linux-snps-arc@...ts.infradead.org"
<linux-snps-arc@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: modules still have .debug_* (was Re: [PATCH 0/3] ARC unwinder
switch to .eh_frame)
On Mon, Sep 26, 2016 at 5:38 AM, Alexey Brodkin
<Alexey.Brodkin@...opsys.com> wrote:
> On Fri, 2016-09-23 at 18:04 -0700, Daniel Mentz wrote:
>> On Fri, Sep 23, 2016 at 3:38 AM, Alexey Brodkin
>> <Alexey.Brodkin@...opsys.com> wrote:
>> >
>> > On Thu, 2016-09-22 at 15:37 -0700, Daniel Mentz wrote:
>> > >
>> > > Sorry, that was a misunderstanding. Buildroot routinely runs the strip
>> > > command on .ko files before installing them on the target. I was only
>> > > looking at the .ko files *after* running the strip command. No, the
>> > > interim patch was not in my tree.
>> >
>> > Well are you sure buildroot really touches modules in Linux kernel build folder?
>> > Buildroot just runs a simple "make" command in "output/build/linux-x.y".
>>
>> Sorry, that was phrased badly. Buildroot does not touch the modules in
>> the Linux kernel build folder. Modules are stripped in the target
>> directory as you described.
>
> So every is as expected now for you or there're still thing you don't like?
Yes, everything works as expected now. Thank you for Synposys' support
with this issue.
Powered by blists - more mailing lists