OpenWrt Forum Archive

Topic: Cross-compilation: Nothing to be done for `package/compile'

The content of this topic has been archived on 17 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi all,
I am trying to make an executable file for OpenWrt using
OpenWrt-SDK-ar71xx-generic_gcc-5.3.0_musl-1.1.16.Linux-x86_64.tar.bz2
— i.e. cross-compilation.

So I put the code into package directory and the output appears in build_dir directory as expected.

I have two almost identical computers.
On the first computer it works perfectly.
But on the second it doesn't work — nothing appears in build_dir directory!

The system says:

make[2]: Nothing to be done for `package/compile'.

The computers are almost identical: Win7 with VirtualBox with Ubuntu12 64bit.
I cannot find any difference. Basically the folder for the cross-compilation is the same!

Here is what happens:

osboxes@osboxes:~/Downloads/trunk$ make V=99
awk: include/scan.awk: line 21: function asort never defined
awk: include/scan.awk: line 21: function asort never defined
awk: include/scan.awk: line 21: function asort never defined
awk: include/scan.awk: line 21: function asort never defined
#
# configuration written to .config
#
make[1]: Entering directory `/home/osboxes/Downloads/trunk'
make[2]: Entering directory `/home/osboxes/Downloads/trunk'
make[2]: Nothing to be done for `package/compile'.
make[2]: Leaving directory `/home/osboxes/Downloads/trunk'
make[2]: Entering directory `/home/osboxes/Downloads/trunk'
Generating package index...
Signing key has not been configured
make[2]: Leaving directory `/home/osboxes/Downloads/trunk'
make[1]: Leaving directory `/home/osboxes/Downloads/trunk'
osboxes@osboxes:~/Downloads/trunk$ 

What can be the reason of that strange error?

Why aren't you putting your code in ~/OpenWrt-SDK-ar71xx-generic_gcc-5.3.0_musl-1.1.16.Linux-x86_64/feeds/packages/utils?

Then go to general directory and run:
1) ./scripts/feeds update -i
2) ./scripts/feeds/install <your package>
3) make/<your package>/compile

The discussion might have continued from here.