Re: kernel/drivers/net/wireless/wl/Makefile not found

1,480 views
Skip to first unread message

Ron M

unread,
Jul 18, 2012, 12:55:15 PM7/18/12
to andro...@googlegroups.com
1. Don't use generic_x86 it's deprecated.
2. I am not sure about the specific target - but there are reasonable
chances that "touch Makefile" in this directory will get you through.
That is a workaround for when you try to make mrproper the kernel, you
would fail on the same error.

The better solution would be modifying some makefile somewhere for SUB_DIRS etc.

-Ron

On Wed, Jul 18, 2012 at 2:03 PM, Pieter <psim...@intec.ugent.be> wrote:
> Hi all,
>
> I am trying to build Android-x86 ICS from source. I am using a Ubuntu 10.04
> LTS 64-bit, with the Sun JDK, as suggested in all tutorials.
>
> I issued the following build command:
> **** make -j2 iso_img TARGET_PRODUCT=generic_x86
>
> After some hours running fine, the compilation however fails at the wireless
> driver, with the following error:
>
> LD [M] drivers/net/wireless/rtlwifi/rtl8192se/rtl8192se.o
> LD [M] drivers/net/wireless/rtlwifi/rtlwifi.o
> /home/pieter/android-x86/kernel/scripts/Makefile.build:44:
> /home/pieter/android-x86/kernel/drivers/net/wireless/wl/Makefile: No such
> file or directory
> make[6]: *** No rule to make target
> `/home/pieter/android-x86/kernel/drivers/net/wireless/wl/Makefile'. Stop.
> make[5]: *** [drivers/net/wireless/wl] Error 2
> make[4]: *** [drivers/net/wireless] Error 2
> make[3]: *** [drivers/net] Error 2
> make[2]: *** [drivers] Error 2
> make[1]: *** [sub-make] Error 2
> make[1]: Leaving directory `/home/pieter/android-x86/kernel'
> make: *** [out/target/product/generic_x86/kernel] Error 2
> make: *** Waiting for unfinished jobs....
>
>
> Checking the drivers/net/wireless/wl/ directory, there is indeed no
> Makefile, but only these files:
> - Kconfig
> - Makefile.patch
> - wl_iw.h.patch.
>
> How can I make sure this Makefile is available?
>
> Thank you very much,
> Pieter
>
> --
> You received this message because you are subscribed to the Google Groups
> "Android-x86" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/android-x86/-/V-EFvvM-8HsJ.
> To post to this group, send email to andro...@googlegroups.com.
> To unsubscribe from this group, send email to
> android-x86...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/android-x86?hl=en.

Chih-Wei Huang

unread,
Jul 18, 2012, 11:49:31 PM7/18/12
to andro...@googlegroups.com
The broadcom wifi driver source will be downloaded
from internet directly. Probably you don't have
a valid internet connection on making.

If you don't need the driver, you can remove
CONFIG_WL=m in the kernel config.

2012/7/18 Pieter <psim...@intec.ugent.be>:
--
Chih-Wei
Android-x86 project
http://www.android-x86.org

Pieter

unread,
Jul 19, 2012, 2:22:54 AM7/19/12
to andro...@googlegroups.com
Hi Ron and Chih-Wei,

thank you both for your kind replies.

For archiving purposes:
* Indeed, there was no Internet connection at the time of making.
* Meanwhile, I succeeded compiling by removing in the kernel config the Broadcom drivers (even without Internet connection).

Given Ron's suggestion, I will try the EEE-PC image instead to start from for my platform.

Best regards,
Pieter

Chih-Wei Huang

unread,
Aug 30, 2012, 12:54:50 AM8/30/12
to andro...@googlegroups.com
2012/8/30 Fatty <bis...@gmail.com>:
>
> There are another bug is present.
> WL_ENABLED is checked using $(KERNEL_DOTCONFIG_FILE) from out directory
> instead $(KERNEL_CONFIG_FILE).
>
> This lead to error 'grep: .../out/target/product/.../obj/kernel/.config: No
> such file or directory' on first build executing and can be solved by
> re-executing make w/o changes.

Thank you for pointing this bug.
The patch is applied.

Regards,

Honghe Wu

unread,
Sep 17, 2013, 4:47:33 AM9/17/13
to andro...@googlegroups.com
In view of the generic_x86-eng lunch is deprecated on Android-x86 4.0,  it is better to remove the generic_x86 option of page and compile option of lunch command in Android-x86 source compile. 
I am the lucky guy to choose the generic_x86 TARGET_PRODUCT on compiling the source code = =!
Reply all
Reply to author
Forward
0 new messages