[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151201181643.GZ8644@n2100.arm.linux.org.uk>
Date: Tue, 1 Dec 2015 18:16:43 +0000
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Michal Marek <mmarek@...e.cz>, Stephen Boyd <sboyd@...eaurora.org>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
linux-kbuild@...r.kernel.org, Nicolas Pitre <nico@...xnic.net>,
Arnd Bergmann <arnd@...db.de>,
Måns Rullgård <mans@...sr.com>
Subject: Re: [PATCH v2 1/2] scripts: Add a recorduidiv program
On Tue, Dec 01, 2015 at 12:22:12PM -0500, Steven Rostedt wrote:
> On Tue, 1 Dec 2015 17:10:14 +0000
> Russell King - ARM Linux <linux@....linux.org.uk> wrote:
>
> > Another suggestion - maybe recordmcount, which fstat()s the file,
> > should check the st_nlink before modifying the file, and error out
> > with a helpful error message telling people not to use hardlinks,
> > which would stop nasty surprises (and make it a rule that this should
> > be implemented as a general principle for good build behaviour) - iow,
>
> Actually I like this solution the best.
>
> > something like this (untested):
>
> Can you test it to see if it gives you the error, otherwise I need to
> set up a CCACHE_HARDLINK environment :-)
It does indeed:
CC init/do_mounts_initrd.o
file is hard linked: init/do_mounts_initrd.o
/home/rmk/git/linux-rmk/scripts/Makefile.build:258: recipe for target 'init/do_mounts_initrd.o' failed
make[2]: *** [init/do_mounts_initrd.o] Error 1
> I guess another solution is to do a copy instead of modifying in place
> if it detects the multiple hard link?
That would be the "transparent" solution. If you think it's worth
persuing, I'll have a go at fixing recordmcount to do that.
--
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
--
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