public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Chris Coffey <cmc@babblebit.net>
Cc: devel@driverdev.osuosl.org,
	Christian Gromm <christian.gromm@microchip.com>,
	linux-kernel@vger.kernel.org,
	Michael Fabry <Michael.Fabry@microchip.com>
Subject: Re: [PATCH] staging: most: Fix build errors
Date: Tue, 28 Nov 2017 13:31:42 +0100	[thread overview]
Message-ID: <20171128123142.GA23875@kroah.com> (raw)
In-Reply-To: <20171128121247.yeklq5dagwos3mcd@deb-660>

On Tue, Nov 28, 2017 at 12:12:47PM +0000, Chris Coffey wrote:
> On Tue, Nov 28, 2017 at 08:26:07AM +0100, Greg Kroah-Hartman wrote:
> > On Mon, Nov 27, 2017 at 09:12:39PM +0000, Chris Coffey wrote:
> > > This patch fixes build errors that occur when trying to build the
> > > MOST modules. For example, the cdev module build fails with:
> > > 
> > > make[3]: *** No rule to make target 'drivers/staging/most/aim-cdev/cdev.o', needed by 'drivers/staging/most/aim-cdev/aim_cdev.o'.  Stop.
> > > scripts/Makefile.build:569: recipe for target 'drivers/staging/most/aim-cdev' failed
> > > make[2]: *** [drivers/staging/most/aim-cdev] Error 2
> > > scripts/Makefile.build:569: recipe for target 'drivers/staging/most' failed
> > > make[1]: *** [drivers/staging/most] Error 2
> > > Makefile:1502: recipe for target '_module_drivers/staging' failed
> > > make: *** [_module_drivers/staging] Error 2
> > 
> > How are you seeing this error?  What is the build command line that you
> > provided to do this?  It should just "not build" right now at all.
> > 
> 
> I did a git pull to get the latest staging updates, enabled a bunch of
> staging drivers, and then ran a build on the staging modules with 'make
> modules M=drivers/staging'. Unfortunately now I'm unable to reproduce
> the error (of course).

If you run 'make' it would have fixed up the dependancies and not caused
a build error.  That makes sense how you saw it, but it's not there for
anyone else so all is fine.

> > > Update the Makefile variables and paths with the new directory
> > > structure to fix these errors.
> > > 
> > > Signed-off-by: Chris Coffey <cmc@babblebit.net>
> > > ---
> > >  drivers/staging/most/Makefile | 14 +++++++-------
> > >  1 file changed, 7 insertions(+), 7 deletions(-)
> > 
> > I think a patch was sent yesterday to fix these up, did you see it in
> > the archives?
> 
> I checked the archives before making the patch, and didn't see anything
> MOST-related in there for the past few days. The patch below made the 
> build succeed and generate all of the MOST modules.

Subject: [PATCH 1/3] staging: most: fix Makefile
is the patch sent yesterday that should resolve this.  I'm going to go
apply it right now...

thanks,

greg k-h

      reply	other threads:[~2017-11-28 12:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 21:12 [PATCH] staging: most: Fix build errors Chris Coffey
2017-11-28  7:26 ` Greg Kroah-Hartman
2017-11-28 12:12   ` Chris Coffey
2017-11-28 12:31     ` Greg Kroah-Hartman [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=20171128123142.GA23875@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Michael.Fabry@microchip.com \
    --cc=christian.gromm@microchip.com \
    --cc=cmc@babblebit.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.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