The thread closed automatically but I want to comment on it:
I wish to confirm that after executing @linuxdev instructions I still get the “extra” hardware folder (inside tmp2, next to temp3 folder)
The thread closed automatically but I want to comment on it:
I wish to confirm that after executing @linuxdev instructions I still get the “extra” hardware folder (inside tmp2, next to temp3 folder)
That was a long thread! FYI, the final instructions for reproducing this are in this last comment:
https://forums.developer.nvidia.com/t/kernel-make-execution-creates-hardware-folder-on-my-desktop-cont/269605/12
For people just starting this, it uses the source code of the R35.3.1 kernel, found here:
https://developer.nvidia.com/embedded/jetson-linux-r3531
The short story behind this thread is that a proper kernel build is producing content in a directory where it should not be producing it. Namely, a parent directory to the build directory. This last reply I made in the other thread (URL above) shows how to reproduce the problem via cross compile. It appears there could be a bug in the _ddot_
macro content causing a descent into one parent directory too many.