You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, depending on your gcc you may need to edit /usr/src/kernel/arch/x86/Makefile
Line 78 change "stackp-y := -fstack-protector-strong" to stackp-y := -fstack-protector-all
If that doesn't work you can build your own newer gcc see #939
The makefile edit option seems to be allowing the build to proceed. I will
let you know if I have further issues. Thanks for the suggestions.
Got Win7 and the globalcache.com windows-only utility "ilearn,exe" working in my crouton/virtualbox now. This is a wonderful project thanks for all the obvious hard work that goes into it. I can work all the needed toolchain pieces for my openremote.org driven home automation stuff from my chromebook now!!!! Major kudos to everybody on this project. Please close this now non-issue.
So, depending on your gcc you may need to edit /usr/src/kernel/arch/x86/Makefile
Line 78 change "stackp-y := -fstack-protector-strong" to stackp-y := -fstack-protector-all
If that doesn't work you can build your own newer gcc see #939 #939
—
Reply to this email directly or view it on GitHub #951 (comment).
I am getting the following error message:
.
.
.
cc1: error: unrecognized command line option ‘-fstack-protector-strong’
make[3]: *** [kernel/bounds.s] Error 1
make[2]: *** [prepare0] Error 2
make[2]: Leaving directory
/home/tim/kernel' make[1]: *** [debian/stamp/conf/kernel-conf] Error 2 make[1]: Leaving directory
/home/tim/kernel'make: *** [debian/stamp/conf/minimal_debian] Error 2
Failed to create a ./debian directory: at /usr/bin/make-kpkg line 984.
This happens at this step:
$ make-kpkg --rootcmd fakeroot kernel_image kernel_headers
I have a HP Pavillion Chromebook 14. The uname give this info...
$ uname -a
Linux localhost 3.4.0 #1 SMP Thu Jul 24 15:16:06 PDT 2014 x86_64 x86_64 x86_64 GNU/Linux
Thanks for any help .... Tim C.
The text was updated successfully, but these errors were encountered: