From: Johannes Berg <johannes@sipsolutions.net>
To: "Maxin B. John" <maxin.john@gmail.com>
Cc: linux-wireless@vger.kernel.org, "Maxin B. John" <maxin.john@intel.com>
Subject: Re: [PATCH] iw: support and enable separate build dir
Date: Tue, 21 Jun 2016 11:41:27 +0200 [thread overview]
Message-ID: <1466502087.3170.17.camel@sipsolutions.net> (raw)
In-Reply-To: <CAMhs6Yw-ScHvfjsxKGG-teXAYtebsrOEmRzt9-VBepoeNkpjWg@mail.gmail.com> (sfid-20160610_125900_263648_E37B4F59)
On Fri, 2016-06-10 at 13:58 +0300, Maxin B. John wrote:
> Hi Johannes,
>
> On Thu, Jun 9, 2016 at 11:25 AM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > On Wed, 2016-06-01 at 11:40 +0300, maxin.john@gmail.com wrote:
> > > From: "Maxin B. John" <maxin.john@intel.com>
> > >
> > > Support separation of SRCDIR and OBJDIR
> > >
> > Doesn't seem to work:
> >
> > $ mkdir /tmp/obj
> > $ make clean
> > $ make OBJDIR=/tmp/obj
> > [...]
> > GEN version.c
> > CC version.o
> > cc: error: version.c: No such file or directory
> > cc: fatal error: no input files
> > compilation terminated.
> > Makefile:104: recipe for target 'version.o' failed
> > make: *** [version.o] Error 1
> > $ ls *.o
> > event.o genl.o ibss.o info.o interface.o iw.o mesh.o mpath.o
> > mpp.o ocb.o phy.o reg.o scan.o station.o survey.o util.o
> >
> > (object files are in the wrong place too)
>
> I was following the below listed steps to verify this patch:
>
> # mkdir build
> # cd build
> # make -f <path>/iw/Makefile
>
Oh. Any chance you could make both work, since the "make O=..." is
something kernel people are used to/familiar with?
johannes
next prev parent reply other threads:[~2016-06-21 11:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 8:40 [PATCH] iw: support and enable separate build dir maxin.john
2016-06-09 8:25 ` Johannes Berg
2016-06-10 10:58 ` Maxin B. John
2016-06-21 9:41 ` Johannes Berg [this message]
2016-06-21 12:08 ` Maxin B. John
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=1466502087.3170.17.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=maxin.john@gmail.com \
--cc=maxin.john@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.