From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-10-30
Date: Fri, 31 Oct 2014 11:53:18 +0200 [thread overview]
Message-ID: <20141031095318.GB2453@tarshish> (raw)
In-Reply-To: <20141031073016.162E2100B71@stock.ovh.net>
Hi Thomas, Gustavo,
On Fri, Oct 31, 2014 at 08:30:15AM +0100, Thomas Petazzoni wrote:
> arm | nss-mdns-0.10 | NOK | http://autobuild.buildroot.net/results/7dba3a78013db577ddd17fc7db4b36ecea2bbc0b/
> i686 | nss-mdns-0.10 | NOK | http://autobuild.buildroot.net/results/e390e383f6481c82b936d8a644784803a2536dad/
sed -r -i -e 's/^(hosts:[[:space:]]+).*/\1files mdns4_minimal [NOTFOUND=return] dns mdns4/' /home/buildroot/instance-1/output/target/etc/nsswitch.conf
sed: can't read /home/buildroot/instance-1/output/target/etc/nsswitch.conf: No such file or directory
This is caused by e1eba3d97c5d4 (system/skeleton: make nsswitch install
conditional). nss-mdns expect nsswitch.conf to exist when it builds, while
this commit postpones nsswitch.conf installation to target_finalize. Not sure
what to do with that, though. Move it to an earlier hook?
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2014-10-31 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-10-30 Thomas Petazzoni
2014-10-31 9:53 ` Baruch Siach [this message]
2014-10-31 9:59 ` Gustavo Zacarias
2014-10-31 11:43 ` Max Filippov
2014-10-31 14:04 ` Angelo Compagnucci
2014-10-31 17:23 ` Vicente Olivert Riera
2014-10-31 17:45 ` Bernd Kuhls
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=20141031095318.GB2453@tarshish \
--to=baruch@tkos.co.il \
--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.