-
-
Notifications
You must be signed in to change notification settings - Fork 617
Downgrade Kernel version to 3.18, build failed with "BR2_EXTERNAL='...' does not exist" #39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi Reveriel, The current Buildroot allows BR2_EXTERNAL to be a colon : separated list of paths: https://buildroot.org/downloads/manual/manual.html#outside-br-custom So I'm guessing that the Buildroot you checked out to did not support that? Which version was that for the record? In general, downgrading the kernel is a pain, since you have to mess with the Buildroot version, and then potentially you also have to make this repo play well with that version of Buildroot. I've updated the https://github.com/cirosantilli/linux-kernel-module-cheat/tree/7bbc3c4c8bb556267aeeb820461c7cf99c6b9d79#downgrade-the-linux-kernel section to clarify that now. For the most part however, I expect the required changes to this repo to be trivial: just do a Another thing you can try is to run an older kernel on our current Buildroot. It might work for the most part, but I wouldn't do any serious work based on it. If this is important to you and if you understand what is going on, send me a pull request with a linux-3.18 branch of this repo and I'll let you own it. |
The buildroot version is
The default version is 3.18.1 not 3.18 beacause 3.18 failed to compile at the 3.18.1 buildroot's manual said:
It seems we need to add a There are some problems when building the 3.18.1 buildroot.
Your lkmc helps me a lot, and I'm willing to contribute. But I'm quite new to kernel development, and am not clear what buildroot does. As for those external packages, right now I just ignored them. Thanks for your explanation. |
OK, glad you managed to find out what happened. If something else goes wrong, let me know. There is no obligation to contribute, as long as it helped you, I'm happy. Buildroot packages are a way to add your software to the Buildroot image, and All our Buildroot packages are under buildroot_packages/ to the build. But there is nothing important there anymore, as I moved the important stuff to custom build commands like ./build-modules and ./build-userland which integrate with |
in short
Try to use 3.18 linux kernel, failed at
./build-buildroot
,BR2_EXTERNAL
has strange value. Setting it to empty avoids it.Is there something that are not cleaned?
details
I need to test the ver3.18 kernel.
So I checked out ver3.18 in
submodule/linux
and checked out the corresponding buildroot commit as the readme said.
then I run
./build
, and failed in./build-buildroot
And the related code is
commit 863867ed3d9079e7b820b144724d81fc1becec31
submodule/buildroot/Makefile:140
this code tries to cd
$(BR2_EXTERNAL)
andpwd
, but the value ofBR2_EXTERNAL
is such a long string that contains many path separated by:
, I don't know where is the definition ofBR2_EXTERNAL
isSo I add
and the build continues..
The text was updated successfully, but these errors were encountered: