From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Current 'next' won't build
Date: Sun, 23 Dec 2018 10:59:42 +0100 [thread overview]
Message-ID: <b1336091-316b-1d16-4ade-75a0e68196b7@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 740 bytes --]
Hi,
First - all the best for chrismas and the new year. May the code be with
you! :-)
But..
Everytime I try, I'm getting the same error:
...
#Change KVER to Kernelversion
sed -e "s/KVER/4.14.86/g" -i /tmp/ROOTFILES
#Remove doubled files with tar/untar/tar to save space
tar -c --exclude='proc/*' --exclude='tmp/ROOTFILES' --exclude='#*'
--exclude='dev/pts/*' \
<->--exclude-from=/usr/src/config/rootfiles/core/127/exclude \
<->-C / --files-from=/tmp/ROOTFILES -f /ipfire.tar
tar: boot/boot.cmd: Cannot stat: No such file or directory
tar: boot/boot.scr: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
make: *** [core-updates:67: core/127] Error 2
...
Can anyone confirm?
Best,
Matthias
next reply other threads:[~2018-12-23 9:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-23 9:59 Matthias Fischer [this message]
2018-12-25 8:22 ` Michael Tremer
-- strict thread matches above, loose matches on Subject: below --
2019-06-08 10:20 Matthias Fischer
2019-06-08 10:21 ` Michael Tremer
2019-06-08 10:33 ` Matthias Fischer
2019-06-08 10:35 ` Michael Tremer
2019-06-08 11:38 ` Matthias Fischer
2018-04-29 11:53 Matthias Fischer
2018-04-29 12:08 ` Peter Müller
2017-10-18 2:39 Matthias Fischer
2017-10-18 2:39 ` Michael Tremer
2017-10-18 13:56 ` Matthias Fischer
2017-10-18 14:22 ` Matthias Fischer
2017-10-18 14:50 ` Michael Tremer
2017-10-18 15:54 ` Matthias Fischer
2017-10-18 17:03 ` Matthias Fischer
2017-10-18 17:42 ` Michael Tremer
2017-10-19 14:00 ` Matthias Fischer
2017-10-19 19:10 ` Matthias Fischer
2017-10-23 14:22 ` Michael Tremer
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=b1336091-316b-1d16-4ade-75a0e68196b7@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
/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