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 10716] New: systemd build failure when BR2_TARGET_GENERIC_HOSTNAME is set
Date: Mon, 29 Jan 2018 07:44:58 +0000	[thread overview]
Message-ID: <bug-10716-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 10716
           Summary: systemd build failure when BR2_TARGET_GENERIC_HOSTNAME
                    is set
           Product: buildroot
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: chemobejk at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

Commit aebabb2780da4c5f85fec00b56f4690feb646073 added an old-style
configuration to the systemd build, which is rejected by the new meson build
system.

I'm currently testing this fix to package/systemd/systemd.mk:

    ifneq ($(SYSTEMD_FALLBACK_HOSTNAME),)
    SYSTEMD_CONF_OPTS += -Dfallback-hostname=$(SYSTEMD_FALLBACK_HOSTNAME)
    endif

I'll submit a patch once I have verified the build result.

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

             reply	other threads:[~2018-01-29  7:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29  7:44 bugzilla at busybox.net [this message]
2018-01-29  8:02 ` [Buildroot] [Bug 10716] systemd build failure when BR2_TARGET_GENERIC_HOSTNAME is set bugzilla at busybox.net
2018-01-29  9:48 ` bugzilla at busybox.net
2018-01-29 13:37 ` bugzilla at busybox.net

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-10716-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.