Linux Kernel failed to build: ERROR: no certificate subject alternative name matches

55 views
Skip to first unread message

not you

unread,
Aug 30, 2018, 4:48:09 AM8/30/18
to BeagleBoard
I am following this guide to install Linaro on my Ubuntu 18.04 machine:
https://www.digikey.com/eewiki/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-ARMCrossCompiler:GCC

Thanks to Robert's help, I got Linaro 7.3.1 successfully installed.  I am now stuck at building the Linux Kernel.  I checked out the long term / real-time branch using:

git checkout origin/am33x-rt-v4.9 -b tmp

And proceed to building it:

./build_kernel.sh

It failed to build, giving out these status report:

+ Detected build host [Ubuntu 18.04.1 LTS]
+ host: [x86_64]
+ git HEAD commit: [3a7726562a52a27d7712b5eb4cbe4a2f31890ac6]
Installing:
-----------------------------
--2018-08-30 15:32:01--  https://releases.linaro.org/components/toolchain/binaries/6.4-2018.05/arm-linux-gnueabihf/gcc-linaro-6.4.1-2018.05-x86_64_arm-linux-gnueabihf.tar.xz
Resolving releases.linaro.org (releases.linaro.org)... 13.228.101.204
Connecting to releases.linaro.org (releases.linaro.org)|13.228.101.204|:443... connected.
ERROR: no certificate subject alternative name matches
    requested host name ‘releases.linaro.org’.
To connect to releases.linaro.org insecurely, use `--no-check-certificate'.
--2018-08-30 15:32:01--  https://releases.linaro.org/archive/components/toolchain/binaries/6.4-2018.05/arm-linux-gnueabihf/gcc-linaro-6.4.1-2018.05-x86_64_arm-linux-gnueabihf.tar.xz
Resolving releases.linaro.org (releases.linaro.org)... 13.228.101.204
Connecting to releases.linaro.org (releases.linaro.org)|13.228.101.204|:443... connected.
ERROR: no certificate subject alternative name matches
    requested host name ‘releases.linaro.org’.
To connect to releases.linaro.org insecurely, use `--no-check-certificate'.

So I got a few questions:
1. It installs Linaro 6.4.1 tho I already have 7.3.1.  Why does this happen?
2. What should I do to get it built?

Robert Nelson

unread,
Aug 30, 2018, 10:04:37 AM8/30/18
to Beagle Board, not you
How does it know you have 7.3.1 installed?

> 2. What should I do to get it built?

Read system.sh

Regards,

--
Robert Nelson
https://rcn-ee.com/

not you

unread,
Aug 30, 2018, 10:39:29 AM8/30/18
to BeagleBoard


On Thursday, August 30, 2018 at 9:04:37 PM UTC+7, RobertCNelson wrote:
> 1. It installs Linaro 6.4.1 tho I already have 7.3.1.  Why does this happen?

How does it know you have 7.3.1 installed? 

I did the first part and get Linaro 7.3.1 instead.  Testing with ${CC}gcc succeeded, so I suppose that is the case.   Am I doing it wrong?

Robert Nelson

unread,
Aug 30, 2018, 10:52:17 AM8/30/18
to Beagle Board, not you
>> > 1. It installs Linaro 6.4.1 tho I already have 7.3.1. Why does this happen?
>>
>> How does it know you have 7.3.1 installed?
>
> I did the first part and get Linaro 7.3.1 instead. Testing with ${CC}gcc succeeded, so I suppose that is the case. Am I doing it wrong?

That was for building u-boot... Currently the kernel build script does
not parse the environment variable CC.. I suppose it "could" with some
patches written, but today NOPE..

So if you want to bypass the pre-choosen compiler you need to open
"system.sh" and see the examples, then correctly add your's..

#ARM GCC CROSS Compiler:
#if CC is not set, a known working linaro based gcc compiler will be
downloaded and utilized.
#CC=<enter full path>/bin/arm-none-eabi-
#CC=<enter full path>/bin/arm-linux-gnueabi-
#CC=<enter full path>/bin/arm-linux-gnueabihf-

It has some error detection, so if you don't properly set the
path/etc, it will just default to the build-in version..

not you

unread,
Aug 30, 2018, 11:42:24 PM8/30/18
to BeagleBoard
I edited system.sh to have the full link to Linaro 7.3.1.  When building the kernel, there is a blue screen coming up.  What should I do with it?
Reply all
Reply to author
Forward
0 new messages