Bug 30239 - I can´t build gnutls from source
Summary: I can´t build gnutls from source
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-04-03 14:22 CEST by Nikolay Malykh
Modified: 2022-04-05 12:41 CEST (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Nikolay Malykh 2022-04-03 14:22:29 CEST
Description of problem: I can´t build gnutls from source


Version-Release number of selected component (if applicable): gnutls 3.7.2, 3.7.3, 3.7.4


How reproducible:
Try to build from sources.

Steps to Reproduce:
1. ./configure
2. make
...
make[4]: Entering directory '/home/nmalykh/SRC/gnutls-3.7.2/lib'
  CC       record.lo
  CC       cert-session.lo
during IPA pass: analyzer
In file included from str.h:29,
                 from gnutls_int.h:299,
                 from cert-session.c:28:
cert-session.c: In function '_gnutls_ocsp_verify_mandatory_stapling.part.0'
errors.h:137:7: internal compiler error: Segmentation fault
  137 |       _gnutls_log( l, __VA_ARGS__); } while(0)
      |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
errors.h:140:33: note: in expansion of macro 'LEVEL'
  140 | #define _gnutls_assert_log(...) LEVEL(3, __VA_ARGS__)
      |                                 ^~~~~
errors.h:33:25: note: in expansion of macro '_gnutls_assert_log'
   33 | #define gnutls_assert() _gnutls_assert_log( "ASSERT: %s[%s]:%d\n", __FILE__,__func__,__LINE__);
      |                         ^~~~~~~~~~~~~~~~~~
cert-session.c:420:17: note: in expansion of macro 'gnutls_assert'
  420 |                 gnutls_assert();
      |                 ^~~~~~~~~~~~~
0x197d124 diagnostic_impl(rich_location*, diagnostic_metadata const*, int, char const*, __va_list_tag (*) [1], diagnostic_t)
        ???:0
0x197dd76 internal_error(char const*, ...)
        ???:0
0xbf2a6f crash_signal(int)
        ???:0
0x7e1adf cgraph_node::get_edge(gimple*)
        ???:0
0xf0d2bb ana::decl_region::calc_tracked_p(tree_node*)
        ???:0
0xf2362e ana::region_model_manager::get_region_for_global(tree_node*)
        ???:0
0xf115c9 ana::region_model::get_rvalue_1(ana::path_var, ana::region_model_context*) const
        ???:0
0xf11680 ana::region_model::get_rvalue(tree_node*, ana::region_model_context*) const
        ???:0
0xf148d6 ana::region_model::handle_unrecognized_call(gcall const*, ana::region_model_context*)
        ???:0
0xef619f ana::exploded_node::on_stmt(ana::exploded_graph&, ana::supernode const*, gimple const*, ana::program_state*, ana::uncertainty_t*, ana::path_context*)
        ???:0
0xef8d00 ana::exploded_graph::process_node(ana::exploded_node*)
        ???:0
0xef9ad2 ana::exploded_graph::process_worklist()
        ???:0
0xefbfc7 ana::impl_run_checkers(ana::logger*)
        ???:0
0xefce5e ana::run_checkers()
        ???:0
0xeed498 (anonymous namespace)::pass_analyzer::execute(function*)
        ???:0
Comment 1 Thomas Backlund 2022-04-03 14:36:40 CEST
looks like an issue that should be fixed in upcoming gcc-12.0.1-0.20220403.1.mga9 that will be pushed tonight/tomorrow morning and should be available tommorrow
Comment 2 Nikolay Malykh 2022-04-05 12:41:07 CEST
after updating gss to version 12 everything is fine.

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.