Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Daily results for 2019-11-09
Date: Sun, 10 Nov 2019 09:26:10 +0100	[thread overview]
Message-ID: <20191110082610.GV3419@scaer> (raw)
In-Reply-To: <20191110071632.380E787DAA@hemlock.osuosl.org>

All,

On 2019-11-10 07:16 -0000, Thomas Petazzoni spake thusly:
> Results for branch 'master'
>   riscv64    |   systemd-243-78-gef677436aa   | NOK | http://autobuild.buildroot.net/results/65c6741d812efe86398982d667a28199ea06d0f9 |     
> 
> Results for branch 'next'
>  powerpc64   |   systemd-243-78-gef677436aa   | NOK | http://autobuild.buildroot.net/results/f1e5dbe21685195dc43bf9e6e25425f8a4ec940b |     

That's because systemd v243 introduced a call to realpath(1), which is
not available on "old" distros (Ubuntu 14.04 does not have it, like it
does not have 'ln --relative').

This is strating to be slightly annoying, especially since upstreaam is
really unreceptive about supporting such old-ish build environments...

We now have two packages (as I know of) that have workarounds: systemd
and cups-filters.

So I've looked at adding host-coreutils as a dependency for those
packages. All the depednencies of host-coreutils are already (direct or
indirect) dependencies of systemd or cups-filters, so the overhead is
just the time it takes to build host-coreutils, which is about 1min
here, most of which is spent in configure. Since the build time of all
the dependencies is already large, this is not too bad.

I'll send a patch later today...

The alternative would be that we do systematically install wrappers for
ln and realpath (like the one use for cups-filters, but more generic),
that could be provided with host-skeleton for example...

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2019-11-10  8:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-10  7:16 [Buildroot] [autobuild.buildroot.net] Daily results for 2019-11-09 Thomas Petazzoni
2019-11-10  8:26 ` Yann E. MORIN [this message]
2019-11-17 19:11   ` Arnout Vandecappelle

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=20191110082610.GV3419@scaer \
    --to=yann.morin.1998@free.fr \
    --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