Jump to content

Image build for Orange Pi Zero


spinarr
 Share

Recommended Posts

Hello Armbian,

I am trying to build an image based on release 20.08, but kernel does not get compiled.

 

compile.sh docker BOARD=orangepizero BRANCH=current KERNEL_ONLY=no KERNEL_CONFIGURE=no CLEAN_LEVEL="" NO_APT_CACHER=yes BUILD_MINIMAL=no RELEASE=buster

 

Displaying message: * [\e[32ml\e[0m][\e[32mc\e[0m] xxx-sun50i-h6-enable-higher-clock.patch  info
Displaying message: Compressing sources for the linux-source package
Displaying message: Compiling current kernel 5.8.16 info
Displaying message: Compiler version arm-none-linux-gnueabihf-gcc 9.2.1 info
Displaying message: Using kernel config file config/kernel/linux-sunxi-current.config info
Displaying message: ERROR in function compile_kernel compilation.sh:411 err
Displaying message: Kernel was not built @host err
Displaying message: Process terminated  info

 

drivers/net/wireless/rtl8189es/os_dep/linux/ioctl_cfg80211.c:6549:37: error: ‘cfg80211_rtw_mgmt_frame_register’ undeclared here (not in a function)
 6549 |  .update_mgmt_frame_registrations = cfg80211_rtw_mgmt_frame_register,
      |                                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
make[4]: *** [scripts/Makefile.build:281: drivers/net/wireless/rtl8189es/os_dep/linux/ioctl_cfg80211.o] Error 1
make[3]: *** [scripts/Makefile.build:497: drivers/net/wireless/rtl8189es] Error 2
make[2]: *** [scripts/Makefile.build:497: drivers/net/wireless] Error 2
make[1]: *** [scripts/Makefile.build:497: drivers/net] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:1754: drivers] Error 2
make: *** Waiting for unfinished jobs....

 

Am I doing anything wrong? 

 

Many thanks for the clarification.

 

Regards

Rostislav

Link to comment
Share on other sites

Open source development is fun. Join Armbian Linux development team today!

Only master branch is expected to build flawless. Others aren't. The reason is that upstream sources may change so our patchset does not match anymore and cause issues.

If you want to compile this (older) branch you are on your own.

Link to comment
Share on other sites

  • Werner locked and unlocked this topic

Does that mean that release tags v20.0x work until there is some change in upstream sources that brakes that?

So is it good practice to base the image from master at the given moment?

 

Many thanks.

Rostislav

Link to comment
Share on other sites

18 minutes ago, spinarr said:

So is it good practice to base the image from master at the given moment?

Yes.

Ideally we would fork and freeze all sources depending on a specific branch but last but not least due to lack of  (human) ressources we cannot effort to do that.

Therefore are only able to maintain one branch which is master.

Link to comment
Share on other sites

 Share

×
×
  • Create New...