[OE-core] [PATCH] iw: fix build path

[Pushpal Sidhu]

On Fri, Oct 16, 2015 at 8:34 AM, Pushpal Sidhu <psidhu at gateworks.com> wrote:
> On Thu, Oct 15, 2015 at 7:18 PM, Christopher Larson
> <chris_larson at mentor.com> wrote:
>> On Thu, Oct 15, 2015 at 5:57 PM, Pushpal Sidhu <psidhu at gateworks.com> wrote:
>>>
>>> The source get's checked out into ${PN}-${PV}, not 'build'. Currently,
>>> building
>>> iw is broken because none of the source files are found.
>>
>>
>> First, this message doesn't make sense. You're implying that bitbake thinks
>> B is S, which it does not. Bitbake already knows the correct source tree
>> path. The S = you add here is redundant, ${PN}-${PV} is the default value
>> for S.
>>
>> If iw was failing to build with a separate build directory from source,
>> you'd just need to remove B. That said, it's not, as far as I can tell. I
>> build iw every day as is and it works just fine building with a separate
>> build directory from source, so I suspect you have something wrong going on
>> in your environment.
>
> I agree with you about setting S, I put it in there to be explicit
> (I've seen other package do this for clarity sake). Here are the
> errors I'm seeing (even in a clean build):
>
> DEBUG: Executing shell function do_install
> NOTE: make -j 4 -f
> /usr/src/psidhu/gw-yocto-master/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/iw/4.1-r0/iw-4.1/Makefile
> PREFIX=/usr SBINDIR=/usr/sbin MANDIR=/usr/share/man
> DESTDIR=/usr/src/psidhu/gw-yocto-master/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/iw/4.1-r0/image
> install
>  GEN  version.c
>  CC   version.o
>  CC   iw
> arm-poky-linux-gnueabi-gcc: error: iw.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: genl.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: event.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: info.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: phy.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: interface.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: ibss.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: station.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: survey.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: util.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: ocb.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: mesh.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: mpath.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: mpp.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: scan.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: reg.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: reason.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: status.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: connect.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: link.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: offch.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: ps.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: cqm.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: bitrate.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: wowlan.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: coalesce.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: roc.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: p2p.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: vendor.o: No such file or directory
> arm-poky-linux-gnueabi-gcc: error: sections.o: No such file or directory
> make: *** [iw] Error 1
> ERROR: oe_runmake failed
> ERROR: Function failed: do_install (log file is located at
> /usr/src/psidhu/gw-yocto-master/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/iw/4.1-r0/temp/log.do_install.24334)


Oh wow, I see my entire problem. My build did in fact get dirtied up
(had some legacy meta-layer my repo sync was pulling in). Anyways, I
agree, this isn't a problem at all so this entire post can be
disregarded.

- Pushpal