MarvellEmbeddedProcessors / openwrt-dd

GNU General Public License v2.0
12 stars 17 forks source link

Unable to compile openwrt-dd 17.02 release #3

Closed fishy-chips closed 7 years ago

fishy-chips commented 7 years ago

Hi, I followed the directions from the expressobin wiki to pull down the kernel, openwrt 17.02 release, update the packages via the feeds, and perform menuconfig.

When I attempt to compile, I receive a compilation error indicating that it cannot find the Makefile located here: /home/buddy/Projects/espresso/openwrt/openwrt-dd/staging_dir/host/bin/sed: can't read /home/buddy/Projects/espresso/openwrt/openwrt-dd/build_dir/toolchain-aarch64_cortex-a53+neon-vfpv4_gcc-5.3.0_musl-1.1.16/linux-4.4.8/Makefile: No such file or directory Makefile:100: recipe for target '/home/buddy/Projects/espresso/openwrt/openwrt-dd/build_dir/toolchain-aarch64_cortex-a53+neon-vfpv4_gcc-5.3.0_musl-1.1.16/linux-4.4.8/.prepared' failed

What step did I miss? Are others successful in compiling 17.02?

When I look at the reason why, it appears that linux-4.4.8 has a cyclic link with itself:drwxr-xr-x 3 buddy buddy 4096 Jun 1 14:29 . drwxr-xr-x 4 buddy buddy 4096 Jun 1 11:59 .. lrwxrwxrwx 1 buddy buddy 11 Jun 1 14:29 linux-4.4.8 -> linux-4.4.8 drwxr-xr-x 25 buddy buddy 4096 Jun 1 11:41 openwrt-kernel

any assistance appreciated. Thanks!

full output here: buddy@buddy-VirtualBox ~/Projects/espresso/openwrt/openwrt-dd $ make -j1 V=s fatal: No names found, cannot describe anything. fatal: No names found, cannot describe anything. fatal: No names found, cannot describe anything. make[1]: Entering directory '/home/buddy/Projects/espresso/openwrt/openwrt-dd' make[2]: Entering directory '/home/buddy/Projects/espresso/openwrt/openwrt-dd'

fishy-chips commented 7 years ago

This is foolish.

I walked away after trying to figure out what went wrong. Came back and started from scratch again and noticed that I had the wrong path in the kernel path under menuconfig.

Once I fixed that, all is well. Thanks for the support!

Cathgao commented 5 years ago

This is foolish.

I walked away after trying to figure out what went wrong. Came back and started from scratch again and noticed that I had the wrong path in the kernel path under menuconfig.

Once I fixed that, all is well. Thanks for the support!

How could you solved the problem of "staging_dir/host/bin/sed:not found"?