About the PR 11181

README.md

first issue

• opencv/opencv#11181
• @Nadav-Eyesight posted a issue that OpenCV has a bug that NEON can't be disabled
• Me and @alalek denied that compiler/environment has something wrong
• Now moved the discussion to answers.opencv.org

post on answers.opencv.org

• https://question/187958/help-compiling-to-linux-arm64/
• The QA forum was not enough for asking back and forward
• I needed more information so rather than on forum, Nadav-Eyesight posted a new log on gist

discussion on the gist

• https://gist.github.com/Nadav-Ruskin/53b5726db802ca5538200d38e3a2bf3a
• At that time Nadav-Ruskin's account was named Nadav-Eyesight
• Now, I pointed that the compiler is malfunctioned
• Nadav didn't reply explicitly, but seems to agreed and started to check the compiler

discussion on docross

• dockcross/dockcross#206
• Nadav-Ruskin now posted an issue on dockcross, and the reply was

It is best to move from the Embedian toolchains to Crosstool-ng toolchains,

back to forum

• https://answers.opencv.org/question/187958/help-compiling-to-linux-arm64/?answer=190953#post-id-190953
• Explanation is all there

remaining issue

• original issue ( opencv/opencv#11181 ) is remained open. Can't we close it ?

I think we can close this issue.
The answer is posted on forum

Dockcross was using a deprecated tool named embedian

So it wasn't bug of OpenCV at all.

Nadav-Ruskin did the right thing. Nadav-Ruskin reported to dockcross and figured out that this issue is not from opencv, but the tool that dockross was relying.
If anyone arrives this issue facing same situation, do NOT post the same issue, but change your compiler.

Now, I don't see any reason that this 2+ years old issue remains open