From: Ralf Baechle <ralf@linux-mips.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: linux-mips@linux-mips.org,
Jayachandran C <jayachandranc@netlogicmicro.com>,
David VomLehn <dvomlehn@cisco.com>
Subject: Re: [PATCH] mips: fix netlogic defconfigs for coverage builds
Date: Mon, 23 Jan 2012 14:32:52 +0100 [thread overview]
Message-ID: <20120123133252.GA10454@linux-mips.org> (raw)
In-Reply-To: <1327262566-2676-1-git-send-email-paul.gortmaker@windriver.com>
On Sun, Jan 22, 2012 at 03:02:46PM -0500, Paul Gortmaker wrote:
> The toolchain prefix will most likely be site specific and is
> not guaranteed to always be "mips-linux-gnu-", so simply don't
> specify one. A quick "git grep" shows this to be consistent
> amongst other cross compiled targets.
>
> Similarly, the site specific initramfs source location should not
> be used, since that won't exist for most people, and it prevents
> them from doing coverage builds on the defconfigs, such as those
> done in linux-next and run routinely by many others.
I ran into that issue as well. My build script does something like
sed -i -e s@^CONFIG_CROSS_COMPILE=\"[^\"]*\"\$@CONFIG_CROSS_COMPILE=\"\"@
sed -i -e s@^CONFIG_INITRAMFS_SOURCE=\"[^\"]*\"\$@CONFIG_INITRAMFS_SOURCE=\"\"@
sed -i -e s/^CONFIG_DEBUG_INFO=y\$/#\ CONFIG_DEBUG_INFO\ is\ not\ set/
to patch up two two annoying settings and the last one to make the compiler
run a little quicker and increase chances for a hit in ccache.
But for benefit of the rest of the world I've applied tihs patch and will
also patch up powertv_defconfig which now is the last CONFIG_CROSS_COMPILE
user.
Thanks!
Ralf
prev parent reply other threads:[~2012-01-23 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-22 20:02 [PATCH] mips: fix netlogic defconfigs for coverage builds Paul Gortmaker
2012-01-23 13:32 ` Ralf Baechle [this message]
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=20120123133252.GA10454@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=dvomlehn@cisco.com \
--cc=jayachandranc@netlogicmicro.com \
--cc=linux-mips@linux-mips.org \
--cc=paul.gortmaker@windriver.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