linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Inaky Perez-Gonzalez <inaky@linux.intel.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, Greg KH <greg@kroah.com>,
	linux-next@vger.kernel.org
Subject: Re: linux-next: usb tree build failure
Date: Mon, 22 Dec 2008 09:26:43 -0800	[thread overview]
Message-ID: <200812220926.43784.inaky@linux.intel.com> (raw)
In-Reply-To: <20081222064542.GA24252@uranus.ravnborg.org>

On Sunday 21 December 2008, Sam Ravnborg wrote:
> On Mon, Dec 22, 2008 at 01:42:21PM +1100, Stephen Rothwell wrote:
> > (Just cc'ing Sam)
> >
> > On Sun, 21 Dec 2008 17:31:10 -0800 Greg KH <greg@kroah.com> wrote:
> > > On Mon, Dec 22, 2008 at 11:33:35AM +1100, Stephen Rothwell wrote:
> > > > Hi Greg,
> > > >
> > > > Today's linux-next build (x86_64 allmodconfig) failed like this:
> > > >
> > > > x86_64-linux-ld: drivers/net/wimax/built-in.o: No such file: No such
> > > > file or directory
> > > >
> > > > I reverted commit 66aa675719ab82a03a66b75210fd40be6541f8fb ("wimax:
> > > > Makefile, Kconfig and docbook linkage for the stack") just to make
> > > > the build work.
> > >
> > > Inaky, any ideas?  This really looks like a build system error that I
> > > ran into with the staging tree in the past.  I had to add a "dummy"
> > > file to the empty directory to get it to build properly.
> > >
> > > I tried to duplicate the problem with a sample patch, but never could
> > > :(
>
> Incidentally I sent some review comments to said patch yesterday
> but missed this one.
>
> We have:
> diff --git a/drivers/net/wimax/Makefile b/drivers/net/wimax/Makefile
> new file mode 100644
> index 0000000..bda9430
> --- /dev/null
> +++ b/drivers/net/wimax/Makefile
> @@ -0,0 +1,2 @@
> +
> +obj-$(CONFIG_WIMAX_I2400M)	+= i2400m/
>
>
>
> But the problem here is that because we do not even pretend to
> build some files in this dir thus kbuild does not create build-in.o
>
> The fix is a bit ugly but simple. Add a dummy statement to
> the drivers/net/wimax/Makefile like this:
>
> # force kbuild to create built-in.o
> obj- := dummy.o

ops -- ok, I will. I guess I have to add this in all the similar ones, right?

Greg, do you want a new patch series or just another patch on top?



-- 
Inaky

  reply	other threads:[~2008-12-22 17:28 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-22  0:33 linux-next: usb tree build failure Stephen Rothwell
2008-12-22  1:31 ` Greg KH
2008-12-22  2:42   ` Stephen Rothwell
2008-12-22  6:45     ` Sam Ravnborg
2008-12-22 17:26       ` Inaky Perez-Gonzalez [this message]
2008-12-22 17:53         ` Sam Ravnborg
2008-12-22 23:37           ` Inaky Perez-Gonzalez
2008-12-23  4:31             ` Greg KH
2008-12-23  4:30           ` Greg KH
2008-12-23  4:31         ` Greg KH
2008-12-23 10:26           ` Inaky Perez-Gonzalez
2008-12-23 17:17             ` Greg KH
2008-12-24  1:07               ` Inaky Perez-Gonzalez
2009-01-05  4:34                 ` Greg KH
2009-01-05  5:55                   ` Stephen Rothwell
2008-12-29  3:55 ` Stephen Rothwell
2009-01-02  7:27   ` Greg KH
2009-01-03  4:33     ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2010-02-02  6:10 Stephen Rothwell
2010-02-02 13:53 ` Greg KH
2010-02-02 22:33   ` Stephen Rothwell
2009-08-19  8:34 Stephen Rothwell
2009-08-19 13:52 ` Greg KH
2009-08-19 23:45   ` Greg KH
2009-08-19 23:58     ` Stephen Rothwell
2009-04-29  7:17 Stephen Rothwell
2009-04-29 14:15 ` Greg KH
2009-04-29 15:00   ` Stephen Rothwell
2009-04-29 15:16     ` Greg KH
2009-04-29 15:18 ` Randy Dunlap
2009-04-29 15:37   ` Greg KH
2009-04-29 15:44     ` Randy Dunlap
2009-04-29 17:44       ` Greg KH
2009-04-29 17:53         ` Randy Dunlap
2009-04-30 16:13           ` Greg KH
2009-04-30 16:27             ` Randy Dunlap
2008-11-03  0:36 Stephen Rothwell
2008-11-05  4:47 ` Greg KH
2008-11-05 18:19   ` Mauro Carvalho Chehab
2008-10-14  4:08 Stephen Rothwell
2008-10-14  5:51 ` Alexey Klimov
2008-10-14 17:41   ` Alexey Klimov
2008-10-14 17:26     ` Mauro Carvalho Chehab
2008-10-14  3:59 Stephen Rothwell
2008-10-14  8:24 ` Dmitry
2008-10-14 15:42   ` Dmitry
2008-10-16 16:05 ` Greg KH
2008-10-16 17:27   ` Dmitry Baryshkov
2008-10-16 21:36   ` Dmitry Baryshkov
2008-10-17  0:26     ` Stephen Rothwell
2008-10-17  0:41       ` Dmitry
2008-10-20 18:45         ` Greg KH
2008-08-13  6:37 Stephen Rothwell
2008-08-13  7:33 ` Stephen Rothwell
2008-08-13 14:23   ` Stephen Rothwell
2008-08-14  6:28     ` Stephen Rothwell
2008-08-14  6:54       ` Stephen Rothwell
2008-08-14 12:25         ` Greg KH
2008-08-15  0:16           ` Stephen Rothwell
2008-07-18  1:31 Stephen Rothwell

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=200812220926.43784.inaky@linux.intel.com \
    --to=inaky@linux.intel.com \
    --cc=greg@kroah.com \
    --cc=linux-next@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).