- Sun Apr 25, 2021 10:17 pm
eriksl wrote:Is it all in the overlay tarball? Or just a part?
BTW I now did the fork of the phillipov fork and a rebase to the current state of the original crosstool-ng repo, which went surprisingly well. A few commit had conflicts, primarily because the files they operate on files that are no longer present or have different content. I resolved the conflicts as good as I was able to, two commits were functionally empty now and I removed them.
First test build for some reason selected the wrong arch (alpha instead of xtensa) but otherwise almost completely built to completion (broke at binutils as the selected arch doesn't exist (alpha4ve-lx106..). It looks like I've fixed that issue now, going on again now. If this is going to work, I think it's a great base to keep our fork current with upstream and also, it's fairly easy for the upstream guys (if they want to), to merge "our" patches, which would be ideal of course.
What puzzles me is that crosstool-NG seems to have xtensa support natively, but apparently not lx106?
There are three parts to the crosstool custom build - there is the overlays, the sample config and the local patches for any tools. And you're correct - there's a generic xtensa overlay that's been developed but there's none specific to Espressif's lx-106 so they need to be copied into the tree in the right place before you build.
The sample config files are used to provide default values when you initially select the architecture, but you would override them to select the later gcc and utils.
The local patches are for architecture specific issues in things like gcc and newlib and need to be matched to the version - this is the stuff that I revved for later versions and adjusted