From: Sam Ravnborg <sam@ravnborg.org> To: Arnaud Lacombe <lacombar@gmail.com> Cc: linux arch <linux-arch@vger.kernel.org>, linux-kbuild <linux-kbuild@vger.kernel.org>, lkml <linux-kernel@vger.kernel.org>, Michal Marek <mmarek@suse.cz> Subject: Re: [RFC] move link of vmlinux to a script Date: Mon, 23 Apr 2012 07:10:41 +0200 [thread overview] Message-ID: <20120423051041.GA6709@merkur.ravnborg.org> (raw) In-Reply-To: <CACqU3MU7MS7MjpyiSx-tUJ6c3rSexUB5=vTGy6gPv_OJevuOqw@mail.gmail.com> Hi Arnaud. Thanks for the comments. > > +# Link of vmlinux > > +# $1 - optional extra .o files > > +# $2 output file > > +vmlinux_link() > > +{ > > + local lds=${srctree}/arch/${SRCARCH}/kernel/vmlinux.lds > > +echo srcarch=${SRCARCH} CF=${CFLAGS_vmlinux} > debugging leftover ? yes - will be deleted. > > + > > + local aflags="${KBUILD_AFLAGS} ${AFLAGS_KERNEL} ${NOSTDINC_FLAGS} ${LINUXINCLUDE} ${KBUILD_CPPFLAGS} ${modkern_aflags}" > might be worse splitting that line. I may be able to drop several of the variables, otherwise yes. > > +mksysmap() > > +{ > > + $NM -n $1 | \ > > + grep -v '\( [aNUw] \)\|\(__crc_\)\|\( \$[adt]\)' > $2 > > +} > > + > you don't seem to consistently use #{FOO} vs. $FOO. For arguments I use $FOO for the rest ${FOO} I will fix this up to be consistent. > > +# Update version > > +info GEN .version > > +if [ ! -r .version ]; then > why '-r' specifically ? '-e' might be just enough. I was so before - this part is a copy from the kernel. And there is already enough changes.. > > +# final build of init/ > > +${MAKE} -f ${srctree}/scripts/Makefile.build obj=init > > + > are spaces allowed in `srctree' ? if so, this will break here. Good catch. Sticking "" around should do the trick? I will try to do so. I should also try if it works with spaces - I think not. > > +kallsymso="" > > +kallsyms_vmlinux="" > > + > > +if [ "${CONFIG_KALLSYMS}" != "" ]; then > > + > [ -n "${CONFIG_KALLSYMS}" ] would work too, as well as the other > places where you use the [ "${FOO}" != "" ] syntax. Much more readable - will change. Sam -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Sam Ravnborg <sam@ravnborg.org> To: Arnaud Lacombe <lacombar@gmail.com> Cc: linux arch <linux-arch@vger.kernel.org>, linux-kbuild <linux-kbuild@vger.kernel.org>, lkml <linux-kernel@vger.kernel.org>, Michal Marek <mmarek@suse.cz> Subject: Re: [RFC] move link of vmlinux to a script Date: Mon, 23 Apr 2012 07:10:41 +0200 [thread overview] Message-ID: <20120423051041.GA6709@merkur.ravnborg.org> (raw) Message-ID: <20120423051041.k_nD-BJYg-wU8J6XAcIWXboaD2WeMKx7EGNcTpMy4Pw@z> (raw) In-Reply-To: <CACqU3MU7MS7MjpyiSx-tUJ6c3rSexUB5=vTGy6gPv_OJevuOqw@mail.gmail.com> Hi Arnaud. Thanks for the comments. > > +# Link of vmlinux > > +# $1 - optional extra .o files > > +# $2 output file > > +vmlinux_link() > > +{ > > + local lds=${srctree}/arch/${SRCARCH}/kernel/vmlinux.lds > > +echo srcarch=${SRCARCH} CF=${CFLAGS_vmlinux} > debugging leftover ? yes - will be deleted. > > + > > + local aflags="${KBUILD_AFLAGS} ${AFLAGS_KERNEL} ${NOSTDINC_FLAGS} ${LINUXINCLUDE} ${KBUILD_CPPFLAGS} ${modkern_aflags}" > might be worse splitting that line. I may be able to drop several of the variables, otherwise yes. > > +mksysmap() > > +{ > > + $NM -n $1 | \ > > + grep -v '\( [aNUw] \)\|\(__crc_\)\|\( \$[adt]\)' > $2 > > +} > > + > you don't seem to consistently use #{FOO} vs. $FOO. For arguments I use $FOO for the rest ${FOO} I will fix this up to be consistent. > > +# Update version > > +info GEN .version > > +if [ ! -r .version ]; then > why '-r' specifically ? '-e' might be just enough. I was so before - this part is a copy from the kernel. And there is already enough changes.. > > +# final build of init/ > > +${MAKE} -f ${srctree}/scripts/Makefile.build obj=init > > + > are spaces allowed in `srctree' ? if so, this will break here. Good catch. Sticking "" around should do the trick? I will try to do so. I should also try if it works with spaces - I think not. > > +kallsymso="" > > +kallsyms_vmlinux="" > > + > > +if [ "${CONFIG_KALLSYMS}" != "" ]; then > > + > [ -n "${CONFIG_KALLSYMS}" ] would work too, as well as the other > places where you use the [ "${FOO}" != "" ] syntax. Much more readable - will change. Sam
next prev parent reply other threads:[~2012-04-23 5:10 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-22 21:22 [RFC] move link of vmlinux to a script Sam Ravnborg 2012-04-22 21:22 ` Sam Ravnborg 2012-04-23 2:23 ` Arnaud Lacombe 2012-04-23 5:10 ` Sam Ravnborg [this message] 2012-04-23 5:10 ` Sam Ravnborg 2012-04-30 9:04 ` David Howells 2012-05-05 8:30 ` Sam Ravnborg
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=20120423051041.GA6709@merkur.ravnborg.org \ --to=sam@ravnborg.org \ --cc=lacombar@gmail.com \ --cc=linux-arch@vger.kernel.org \ --cc=linux-kbuild@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mmarek@suse.cz \ /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: linkBe 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; as well as URLs for NNTP newsgroup(s).