1 1
jmartin

Image build broken: nanopim4 / nanopineo4

Recommended Posts

Hi guys,

 

New over here. I have been building custom images without issues for some time for Nano Pi M4. From last week it seems it is not longer building them. In case my build env was corrupted, image build process was tested on a clean VM build env with Ubuntu 18.04, without any customization, following instructions in https://docs.armbian.com/Developer-Guide_Build-Preparation/). I am just trying to buildi kernel image at the moment.

 

In any case, I am seeing some of the rockchip kernel patches are not being applied for some reason, and a compiler error is produced when building the kernel (specifically: looback block dev module). Anybody else is experiencing this?

 

By the way,  is there any way to keep a "frozen" build environment with kernel and image components not being updated for sequential builds in time? I couldn't find any information searching out there on this aspect, and definitely is a nice to have feature.

 

Thank you in advance.

 

Share this post


Link to post
Share on other sites
1 hour ago, jmartin said:

is there any way to keep a "frozen" build environment


Why? You don't want updates and fixes?

Share this post


Link to post
Share on other sites

Updates and fixes are desirable most of the time (specially as final user). However, in my experience when building custom images and adding custom changes, not controlling if/when the latest patch is applied can be undesirable, e.g. when validating your own changes. So, I'd say this type of feature would help determinism and reliability for users customizing images.

 

Finally, when a new version of the system does not work as intended, is cool being able to build a previous version and continue working on some other features/modifications.

 

Thanks anyway, I am aware of the effort put in Armbian, being as is very useful for people like me.

 

Share this post


Link to post
Share on other sites

We have an option to freeze upstream sources - pin to certain tag or release (like this), but not to exact commit. This is the only source that can make problems and where we can't use tag or release. Some RFC or workaround would be needed but ... we have no staff who would wait for your problems, no budget for R&D and support is 99.5% our cost. I have a full time job, a family ...

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
1 1