Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-04-03
Date: Fri, 4 Apr 2014 16:15:37 +0200	[thread overview]
Message-ID: <20140404161537.6864a6f8@skate> (raw)
In-Reply-To: <20140404135530.GA26146@pc-eric>

Dear Eric Le Bihan,

On Fri, 4 Apr 2014 15:55:32 +0200, Eric Le Bihan wrote:

> On Fri, Apr 04, 2014 at 08:30:09AM +0200, Thomas Petazzoni wrote:
> 
> >        arm |                    systemd-212 | NOK |
> > http://autobuild.buildroot.net/results/3546c003a8fcbb36ef5ba29c00a96e473b927ecb/
> This failure is due to systemd now using the `--relative` option of
> `ln(1)` from GNU coreutils. This option was added to GNU coreutils
> 8.16, but some GNU/Linux distributions like Debian Wheezy or Ubuntu
> 12.04 ship 8.13. It looks like the Autobuild server runs one of
> these :-) . Our users may be in this situation and may not want to
> upgrade.

Indeed. That's one of the reason why the distributions we use on the
autobuilders are quite "old".

> I'll post a fix, but would Buildroot benefit from installing
> host-coreutils to avoid this kind of problem?

In general, we try to avoid building too many native dependencies. In
this specific case, if it's not really mandatory to build
host-coreutils and can be avoided using a moderately simple patch, we
prefer doing it this way. We don't want to rebuild the whole world of
native tools just to build systemd, if possible :-)

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2014-04-04 14:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-04  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-04-03 Thomas Petazzoni
2014-04-04 13:55 ` Eric Le Bihan
2014-04-04 14:15   ` Thomas Petazzoni [this message]

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=20140404161537.6864a6f8@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox