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 8086] New: Cannot select systemd as init with Linaro 2014.09 toolchain selected
Date: Wed,  6 May 2015 12:35:05 +0000 (UTC)	[thread overview]
Message-ID: <bug-8086-163@https.bugs.busybox.net/> (raw)

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

           Summary: Cannot select systemd as init with Linaro 2014.09
                    toolchain selected
           Product: buildroot
           Version: unspecified
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: l_giuliani at hotmail.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


On last development version 2015.05 rc1 of Buildroot,  
when external toolchain Linaro 2014.09 is selected, Systemd cannot be choosed
as init system.

From ./toolchain/toolchain-external/Config.in for
BR2_TOOLCHAIN_EXTERNAL_LINARO_ARM and  BR2_TOOLCHAIN_EXTERNAL_LINARO_ARMEB
BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_1 is selected 

But in ./system/Config.in for  BR2_INIT_SYSTEMD you need at least
BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_10

From Linaro website Linaro 2014.09 is build against 3.17 linux kernel :
https://wiki.linaro.org/Cycles/1409/Release

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2015-05-06 12:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06 12:35 bugzilla at busybox.net [this message]
2015-05-06 21:02 ` [Buildroot] [Bug 8086] Cannot select systemd as init with Linaro 2014.09 toolchain selected 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-8086-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.