public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Regression] Build failure in current mainline - firmware related
Date: Sat, 3 Jan 2009 22:43:28 +0100	[thread overview]
Message-ID: <200901032243.28684.rjw@sisk.pl> (raw)
In-Reply-To: <20090103205437.GA5499@uranus.ravnborg.org>

On Saturday 03 January 2009, Sam Ravnborg wrote:
> 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!

Well, in the meantime I ran 'make modules_install V=1' and this is the
last thing printed (the previous ones are not really interesting):

make -f /home/rafael/src/linux-2.6/scripts/Makefile.fwinst obj=firmware __fw_modinst
  gcc -Wp,-MD,firmware/.ihex2fw.d -Ifirmware -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o firmware/ihex2fw /home/rafael/src/linux-2.6/firmware/ihex2fw.c
/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

It fails because of the attempt to compile ihex2fw .

Thanks,
Rafael

  reply	other threads:[~2009-01-03 21:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-03 11:47 [Regression] Build failure in current mainline - firmware related Rafael J. Wysocki
2009-01-03 20:49 ` Sam Ravnborg
2009-01-03 20:54   ` Sam Ravnborg
2009-01-03 21:43     ` Rafael J. Wysocki [this message]
2009-01-03 22:14       ` Sam Ravnborg
2009-01-04 21:44       ` Sam Ravnborg
2009-01-04 22:43         ` Rafael J. Wysocki
2009-01-10 14:36         ` David Woodhouse
2009-01-10 14:58           ` David Woodhouse
2009-01-11 14:42           ` Mauro Carvalho Chehab
2009-01-11 15:01             ` David Woodhouse
2009-01-11 19:07           ` Rafael J. Wysocki
2009-01-08  7:59 ` Sam Ravnborg
2009-01-08 20:17   ` Rafael J. Wysocki

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=200901032243.28684.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /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