[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090103205437.GA5499@uranus.ravnborg.org>
Date: Sat, 3 Jan 2009 21:54:37 +0100
From: Sam Ravnborg <sam@...nborg.org>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: David Woodhouse <dwmw2@...radead.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [Regression] Build failure in current mainline - firmware related
On Sat, Jan 03, 2009 at 09:49:48PM +0100, Sam Ravnborg wrote:
> On Sat, Jan 03, 2009 at 12:47:14PM +0100, Rafael J. Wysocki wrote:
> > Hi,
> >
> > I get the following error from 'make modules_install' on my test boxes:
> >
> > HOSTCC firmware/ihex2fw
> > /home/rafael/src/linux-2.6/firmware/ihex2fw.c:268: fatal error: opening dependency file firmware/.ihex2fw.d: Read-only file system
> > compilation terminated.
> > make[3]: *** [firmware/ihex2fw] Error 1
> > make[2]: *** [_modinst_post] Error 2
> > make[1]: *** [sub-make] Error 2
> > make: *** [all] Error 2
> >
> > where the configuration is that the kernel is compiled on a build box
> > with 'make O=<destdir> -j5' and then <destdir> is mounted over NFS read-only by
> > each test box (full path to this directory is the same on the build box and on
> > the test boxes). Then, I cd into <destdir>, run 'make modules_install' and get
> > the error above.
> >
> > 2.6.28 didn't have this problem.
>
>
> Strange...
> 1) The string "opening dependency file" does not occur in my freshly pulled kernel
> 2) Line 268 is last line of ihex2fw.c
>
> Could you try to do a "make modules_install V=1" to see the exact arguments supplied ti ihex2fw.c
>
> I gave up on all the firmware stuff long time ago and has
> never properly reviewed the implementation so I really
> have no clue what is actually happening.
>
> Walking through the 179 lines Makefile has not yet benn on my
> "fun to do" list - and it most likely take a while before it hits it.
Took a quick peek. The Makefile uses "order only" in three spots.
This alone demand make version 3.80 IIRC and Documetnation/Changes
says 3.79.1...
The "order only" is so rare that Paul Smith once said that
coming up with a good example of usage was not easy.
For the headers_* stuff I recall when I reworked it I could
kill the usage of "order only" there but now it crept
back - sigh!
Sam
--
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