From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: 'cannot access'-message after building 64bit
Date: Wed, 20 May 2020 09:05:03 +0200 [thread overview]
Message-ID: <ecddf9d1-85b9-6da4-c8be-e31ee361ca0e@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
Hi,
I tried to install and configure the 64bit-Devel the same way as the
32bit-Devel but I always get these final "cannot access"-message (ONLY
after building with 64bit!):
...
git (2.12.2) [ 8 ][ DONE ]
mpc (0.21) [ 0 ][ DONE ]
xen-image [ 0 ][ SKIP ]
ls: cannot access '*.bz2': No such file or directory
Checking Logfiles for new Files
*** Build finished in 2:49:36
...
This seems to depend on the following command(s) in 'make.sh' (Core144,
line 1695 or 1700):
...
mv $LFS/install/images/*.bz2 $BASEDIR >> $LOGFILE 2>&1
...
Perhaps this is only cosmetic - on 64bit the xen-image is passed over
anyway (normal), but why do I see these message? As far as I know it
should be sent to nowhere!?
Thanks for any hints.
Best,
Matthias
next reply other threads:[~2020-05-20 7:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 7:05 Matthias Fischer [this message]
2020-05-20 8:07 ` Michael Tremer
2020-05-20 11:38 ` Matthias Fischer
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=ecddf9d1-85b9-6da4-c8be-e31ee361ca0e@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