Bug 2258853 - syslog-ng: FTBFS in F40/Rawhide on i686
Summary: syslog-ng: FTBFS in F40/Rawhide on i686
Keywords:
Status: CLOSED COMPLETED
Alias: None
Product: Fedora
Classification: Fedora
Component: syslog-ng
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Peter Czanik
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PortingToModernCHelpNeeded 2142177
TreeView+ depends on / blocked
 
Reported: 2024-01-17 17:13 UTC by Ben Beasley
Modified: 2024-02-06 12:53 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-02-05 17:02:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ben Beasley 2024-01-17 17:13:42 UTC
The syslog-ng package FTBFS on i686. Koschei hasn’t detected this because it doesn’t run scratch builds on that architecture.

Reproducible: Always

Actual Results:  
modules/secure-logging/slog.c: In function 'writeKey':
modules/secure-logging/slog.c:937:63: error: passing argument 4 of 'g_io_channel_write_chars' from incompatible pointer type [-Wincompatible-pointer-types]
  937 |   status = g_io_channel_write_chars(keyfile, key, KEY_LENGTH, &outlen, &error);
      |                                                               ^~~~~~~
      |                                                               |
      |                                                               guint64 * {aka long long unsigned int *}

Expected Results:  
Successful build

Comment 2 Peter Czanik 2024-02-04 19:55:44 UTC
Thanks! Reported to my colleagues upstream last week. There should be a fix in the coming days.

Comment 3 Peter Czanik 2024-02-05 17:02:27 UTC
For now I worked it around with:

ExcludeArch: %{ix86}

I'll remove this line from syslog-ng.spec once a fix is available upstream.

Comment 4 Peter Czanik 2024-02-06 07:58:48 UTC
OK. I got a fix from my colleagues, so ix86 is enabled again, and package submitted to rawhide.

Comment 5 Ben Beasley 2024-02-06 12:53:42 UTC
Nice work! Thanks for following up on these.


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