From: unspecd <unspecd@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: kicad: update to 6.0.0
Date: Fri, 07 Jan 2022 19:52:49 +0100 [thread overview]
Message-ID: <20220107185249.LUiAWMAZtuQITqHeUQghUHOPZtQUf40lzKw0NsTNpag@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34917@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 3795 bytes --]
New comment by unspecd on void-packages repository
https://github.com/void-linux/void-packages/pull/34917#issuecomment-1007652897
Comment:
1. It works for me (on x86_64-musl), but one test failed:
```
=> kicad-6.0.0_1: running do_check ...
[0/1] Running tests...
Test project /builddir/kicad-6.0.0/build
Start 1: qa_python
1/8 Test #1: qa_python ........................ Passed 63.83 sec
Start 2: qa_common
2/8 Test #2: qa_common ........................ Passed 2.34 sec
Start 3: qa_gerbview
3/8 Test #3: qa_gerbview ...................... Passed 21.09 sec
Start 4: qa_eeschema
4/8 Test #4: qa_eeschema ......................***Failed 15.42 sec
Running 62 test cases...
../qa/eeschema/test_ee_item.cpp(124): error: in "EeItem/Rotate": check aItem->GetBoundingBox().GetTop() == aOriginalItem->GetBoundingBox().GetTop() has failed [-529945 != -529188]
Failure occurred in a following context:
Class: SCH_SHEET
Position: -1000000 -500000, Reference: -1000000 -500000
../qa/eeschema/test_ee_item.cpp(128): error: in "EeItem/Rotate": check aItem->GetBoundingBox().GetBottom() == aOriginalItem->GetBoundingBox().GetBottom() has failed [-433225 != -433982]
Failure occurred in a following context:
Class: SCH_SHEET
Position: -1000000 -500000, Reference: -1000000 -500000
../qa/eeschema/test_ee_item.cpp(124): error: in "EeItem/Rotate": check aItem->GetBoundingBox().GetTop() == aOriginalItem->GetBoundingBox().GetTop() has failed [-529945 != -529188]
Failure occurred in a following context:
Class: SCH_SHEET
Position: -1000000 -500000, Reference: -1000000 0
../qa/eeschema/test_ee_item.cpp(128): error: in "EeItem/Rotate": check aItem->GetBoundingBox().GetBottom() == aOriginalItem->GetBoundingBox().GetBottom() has failed [-433225 != -433982]
Failure occurred in a following context:
Class: SCH_SHEET
Position: -1000000 -500000, Reference: -1000000 0
[etc...]
*** 162 failures are detected in the test module "Common Eeschema module tests"
Start 5: qa_sexpr
5/8 Test #5: qa_sexpr ......................... Passed 0.13 sec
Start 6: qa_kimath
6/8 Test #6: qa_kimath ........................ Passed 0.92 sec
Start 7: qa_pcbnew
7/8 Test #7: qa_pcbnew ........................ Passed 125.88 sec
Start 8: qa_kicad2step
8/8 Test #8: qa_kicad2step .................... Passed 4.92 sec
88% tests passed, 1 tests failed out of 8
Total Test time (real) = 234.73 sec
The following tests FAILED:
4 - qa_eeschema (Failed)
Errors while running CTest
FAILED: CMakeFiles/test.util
cd /builddir/kicad-6.0.0/build && /usr/bin/ctest --force-new-ctest-process
ninja: build stopped: subcommand failed.
```
2. You could remove unused configure_args:
- KICAD_USE_OCE [[1](https://gitlab.com/kicad/code/kicad/-/commit/e57bde65821d7afcafeceb3b1a7f25e424d83121), [2](https://gitlab.com/kicad/code/kicad/-/commit/1c5c052301b607a0cf8b8ed6681f1db1622a865b)]
- [KICAD_BUILD_VERSION](https://gitlab.com/kicad/code/kicad/-/commit/fd54d394bd12d2cb277fc289b6b4879f986c2416)
- [BUILD_GITHUB_PLUGIN](https://gitlab.com/kicad/code/kicad/-/commit/9ed6cdd94391bf07b4d509b0b79f8873ec1ec4fd)
3. Not sure, but instead of deleting `disable-warnings.patch`, you could update it:
```diff
--- a/CMakeModules/Warnings.cmake
+++ b/CMakeModules/Warnings.cmake
@@ -38,13 +38,6 @@
set( WARN_FLAGS_CXX "-Wall" )
- # Warn about missing override specifiers
- CHECK_CXX_COMPILER_FLAG( "-Wsuggest-override" COMPILER_SUPPORTS_WSUGGEST_OVERRIDE )
-
- if( COMPILER_SUPPORTS_WSUGGEST_OVERRIDE )
- set( WARN_FLAGS_CXX "${WARN_FLAGS_CXX} -Wsuggest-override" )
- message( STATUS "Enabling warning -Wsuggest-override" )
- endif()
```
next prev parent reply other threads:[~2022-01-07 18:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 2:47 [PR PATCH] " PoroCYon
2022-01-07 18:52 ` unspecd [this message]
2022-01-07 23:07 ` [PR PATCH] [Updated] " PoroCYon
2022-01-07 23:10 ` PoroCYon
2022-01-16 8:43 ` lemmi
2022-01-16 8:44 ` lemmi
2022-01-16 16:37 ` [PR PATCH] [Updated] " PoroCYon
2022-01-16 16:38 ` PoroCYon
2022-01-16 17:48 ` kicad: update to 6.0.1 PoroCYon
2022-01-16 18:35 ` [PR REVIEW] " ericonr
2022-01-16 18:35 ` ericonr
2022-01-16 18:35 ` ericonr
2022-01-16 23:33 ` PoroCYon
2022-01-16 23:39 ` PoroCYon
2022-01-17 0:55 ` [PR PATCH] [Updated] " PoroCYon
2022-01-17 0:57 ` PoroCYon
2022-01-17 4:47 ` [PR REVIEW] " ericonr
2022-01-17 17:17 ` [PR PATCH] [Updated] " PoroCYon
2022-01-23 22:23 ` PoroCYon
2022-01-26 17:26 ` foopub
2022-01-26 17:34 ` foopub
2022-01-27 0:32 ` PoroCYon
2022-01-27 1:05 ` PoroCYon
2022-01-27 13:53 ` [PR PATCH] [Updated] " PoroCYon
2022-01-28 6:27 ` [PR PATCH] [Closed]: " ericonr
2022-01-28 8:00 ` ericonr
2022-01-29 1:12 ` foopub
2022-01-29 1:12 ` foopub
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220107185249.LUiAWMAZtuQITqHeUQghUHOPZtQUf40lzKw0NsTNpag@z \
--to=unspecd@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).