All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13201] New: SYSTEMD build failed with GCC 7.x
Date: Fri, 11 Sep 2020 14:02:21 +0000	[thread overview]
Message-ID: <bug-13201-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=13201

            Bug ID: 13201
           Summary: SYSTEMD build failed with GCC 7.x
           Product: buildroot
           Version: 2020.08
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: oaivanov at elvees.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

systemd 246 bring back 'nonnull' warning (see
https://github.com/systemd/systemd/pull/15704).
GCC 7.x produces false positive nonnull warnings and fails to compile systemd.
GCC 9.x are OK.

../src/journal/sd-journal.c: In function ?sd_journal_open_files_fd?:
../src/journal/sd-journal.c:1293:28: error: argument 2 null where non-null
expected [-Werror=nonnull]
                         fd = openat(j->toplevel_fd, skip_slash(path),
O_RDONLY|O_CLOEXEC|O_NONBLOCK);
                        
~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

../src/journal/sd-journal.c:1295:28: error: argument 1 null where non-null
expected [-Werror=nonnull]
                         fd = open(path, O_RDONLY|O_CLOEXEC|O_NONBLOCK);
                         ~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-09-11 14:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-11 14:02 bugzilla at busybox.net [this message]
2024-06-15 14:55 ` [Buildroot] [Bug 13201] SYSTEMD build failed with GCC 7.x bugzilla

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=bug-13201-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.