From: Nicholas Piggin <npiggin@gmail.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Michal Marek <michal.lkml@markovi.net>
Subject: Re: [PATCH 2/2] kbuild: rename built-in.o to built-in.a
Date: Sun, 11 Feb 2018 21:15:08 +1000 [thread overview]
Message-ID: <20180211211508.4261ebf2@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <CAK7LNAT=9d9W8kTjzSTRATLvvHVUqQN-7h_owvon_a=oLy0T_A@mail.gmail.com>
On Sun, 11 Feb 2018 13:38:04 +0900
Masahiro Yamada <yamada.masahiro@socionext.com> wrote:
> 2018-02-10 23:25 GMT+09:00 Nicholas Piggin <npiggin@gmail.com>:
> > Incremental linking is gone, so rename built-in.o to built-in.a, which
> > is the usual extension for archive files.
> >
> > This patch does two things, first is a simple search/replace:
> >
> > git grep -l 'built-in\.o' | xargs sed -i 's/built-in\.o/built-in\.a/g'
> >
> > The second is to invert nesting of nested text manipulations to avoid
> > filtering built-in.a out from libs-y2:
> >
> > -libs-y2 := $(filter-out %.a, $(patsubst %/, %/built-in.a, $(libs-y)))
> > +libs-y2 := $(patsubst %/, %/built-in.a, $(filter-out %.a, $(libs-y)))
> >
> > Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
>
>
> I think this is the right thing to do, but I have no idea
> why 'less kernel/built-in.a' shows strange output.
> Do you have a clue?
>
>
> Without this patch,
> 'emacs kernel/built-in.o'
> 'cat kernel/built-in.o'
> 'less kernel/built-in.o'
>
> showed me the same content.
>
> $ less kernel/built-in.o | head -n 10
> !<thin>
> // 2964 `
> fork.o/
> exec_domain.o/
> panic.o/
> cpu.o/
> exit.o/
> softirq.o/
> resource.o/
> sysctl.o/
>
>
>
>
> After applying this patch,
> 'less kernel/built-in.a' is strange.
>
>
> $ less kernel/built-in.a | head -n 10
> rw-r--r-- 0/0 60216 Jan 1 09:00 1970 kernel/fork.o
> rw-r--r-- 0/0 3648 Jan 1 09:00 1970 kernel/exec_domain.o
> rw-r--r-- 0/0 20552 Jan 1 09:00 1970 kernel/panic.o
> rw-r--r-- 0/0 87752 Jan 1 09:00 1970 kernel/cpu.o
> rw-r--r-- 0/0 34136 Jan 1 09:00 1970 kernel/exit.o
> rw-r--r-- 0/0 41448 Jan 1 09:00 1970 kernel/softirq.o
> rw-r--r-- 0/0 40904 Jan 1 09:00 1970 kernel/resource.o
> rw-r--r-- 0/0 60968 Jan 1 09:00 1970 kernel/sysctl.o
> rw-r--r-- 0/0 4472 Jan 1 09:00 1970 kernel/sysctl_binary.o
> rw-r--r-- 0/0 12472 Jan 1 09:00 1970 kernel/capability.o
>
>
> However, 'cat kernel/built-in.a' works as I expect.
>
> $ cat kernel/built-in.a | head -n 10
> !<thin>
> // 2964 `
> fork.o/
> exec_domain.o/
> panic.o/
> cpu.o/
> exit.o/
> softirq.o/
> resource.o/
> sysctl.o/
>
>
>
> Is my 'less' insane?
> Or, is this intentional behavior of 'less'?
Interesting, my less does not do that. Instead of the raw contents
of the file, yours is providing output of `ar tv`, which is
reconstructing more of the archive metadata. I guess it is keyed
on the filename extension.
Do you have an alias for it, or maybe the distro patches the tool?
It seems a bit rude for your less tool to reformat data for you.
Thanks,
Nick
next prev parent reply other threads:[~2018-02-11 11:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 14:25 [PATCH 0/2] remove the last of incremental linking Nicholas Piggin
2018-02-10 14:25 ` [PATCH 1/2] kbuild: remove incremental linking option Nicholas Piggin
2018-02-11 6:04 ` Masahiro Yamada
2018-02-18 14:26 ` Sam Ravnborg
2018-02-18 16:53 ` Nicholas Piggin
2018-02-10 14:25 ` [PATCH 2/2] kbuild: rename built-in.o to built-in.a Nicholas Piggin
2018-02-11 4:38 ` Masahiro Yamada
2018-02-11 11:15 ` Nicholas Piggin [this message]
2018-02-12 0:57 ` Masahiro Yamada
2018-02-12 1:26 ` Nicolas Pitre
2018-02-12 3:00 ` Masahiro Yamada
2018-02-12 3:08 ` Masahiro Yamada
2018-02-18 17:10 ` Sam Ravnborg
2018-02-19 7:04 ` Nicholas Piggin
2018-02-18 23:42 ` [PATCH 0/2] remove the last of incremental linking Masahiro Yamada
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180211211508.4261ebf2@roar.ozlabs.ibm.com \
--to=npiggin@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=yamada.masahiro@socionext.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox