Jump to content

Tucson Tom

Members
  • Posts

    4
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Tucson Tom got a reaction from Werner in Getting Source Code   
    I would have been back sooner, but being new on the forum, it seemed to not let me post more than once in 24 hours.  Or something.
     
    But I was busy with this most of yesterday in an interesting way.  I gave up (for now anyway) doing this on my Fedora Desktop.  What I did was to download Armbian for my Orange Pi PC 2, put it on an SD card and run it on the Orange Pi.  Then I used armbian-config to download kernel sources, which worked just fine, placing them in /usr/src.  Then I could remove the SD card, mount it on my desktop and copy the sources for my convenience.
     
    Then I put the SD card back into the Orange Pi, fired it up, did a cd to /usr/src/linux-source-5.4.43-sunxi64 and typed "make".   It plowed away for 10 hours or more (it finished during the night when I was asleep).  It hung once in the afternoon requiring a reboot and restarting make.  The advantage of this for me, is the build leaves object files (*.o) in the source tree letting me know at a glance just what source files were involved in the build.  This has proven invaluable for me in the past when rummaging around in the linux sources.  Now I can pull that SD card again and copy these files to my desktop for study.
     
    It would be nice to do as Werner says and be able to grab the sources and patch them on my desktop.  I have the idea of studying the Armbian build system and reproducing parts of it in Python to liberate it from being debian dependent -- but using the actual target system was the easy way.
     
    So thanks for the advice.  I still haven't looked at why the R_WDOG patch failed, but I figure that is something that someone else will run into and sort out.
     
    Thanks again.
     
       Tom
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines