How does the kernel differ from just a fresh kernel from kernel.org? Devicetree settings etc.
What I'm looking for is , grab kernelsource from kernel.org select correct devicetree and arch,
compile with cross compiler (mipsel-linux-musl) and create some sort of image to be programmed to the union
Got it! I just had to get my directories and paths right. I was rushing a bit, and things were not lined up exactly correctly. I think it builds for the entire project because the recursive make found my package on its own, but I wasn't specifying it exactly right when I tried to build it individually.
If it seems that your build system configuration isn't matching the firmware that we build, it might be because when ./scripts/feeds is run, it overwrites the .config file. To remedy this, you can just run git checkout .config (assuming you're using our github repo or docker image).
As for packages failing to build, we've seen this happen as well but only when running our Docker image on a windows machine. If the Docker image is running on Linux or Mac, there's no issues. (Haven't had the cycles to figure out why it doesn't play nice with Windows)
@Douglas-Kryder all great information, thank you. Your guess of a new wifi driver release seems realistic. If it doesn't arrive by July (which would be nearly 1 year late) then it probably won't ever come. I'll start testing the official lede builds with Onion packages and report back my findings.
0.1.9 b149 is pretty old. I am one behind at b156, but it has been stable with some bugs worked out. Maybe download and install it, as a number of other packages have been upgraded since the release of b149. Or even to b157. Just a thought.
@Zogg-Baubas Well, it seems my likelihood of doing that is going down fast. I guess I can reformat the drive to ext4? I only went with HFS because I'd been using the drive on a separate machine and it was already formatted (and loaded with a few hundred gig of files). But if that's what I gotta do, I guess that's what I gotta do.
@Armstead-Smith if the individual app is a package in a feed (can be a third party feed like Onion's, or your own), you can build it separately with
This will produce a *.opkg package in bin/packages/mipsel_24kc/FEEDNAME. This can then be copied to the omega2 and installed with opkg.
Setting up your own feed with your own packages is not entirely trivial, but not really difficult either (with some time invested in reading up). I think it's worth doing, to get a nicely organized build.
If all you need is cross-compiling a binary without packaging, you could probably directly use the tools from the toolchain LEDE has build for you in build_dir/toolchain-mipsel_24kc_gcc-5.4.0_musl-1.1.16. You'd need a bunch of environment settings to direct compiler and linker to the correct headers and libraries - but I don't have practical experience with that.
Also, regarding the kernel issues, the Omega's firmware follows the head of the OpenWRT CC repo, we add customizations on top of it. After the campaign, we'll make it a priority to fix that nagging kernel version issue.
Looks like your connection to Community was lost, please wait while we try to reconnect.