From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: 'cannot access'-message after building 64bit Date: Wed, 20 May 2020 09:07:09 +0100 Message-ID: <8FE22679-B29A-49D7-B27D-D30D55532EA5@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2811621241548519108==" List-Id: --===============2811621241548519108== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, This always shows up, because we do not have any images compressed as bzip2 a= ny more on most architectures. You can just ignore it, or add a 2>/dev/null to the command, so that the mess= age won=E2=80=99t be shown. -Michael > On 20 May 2020, at 08:05, Matthias Fischer = wrote: >=20 > Hi, >=20 > 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!): >=20 > ... > 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 > ... >=20 > This seems to depend on the following command(s) in 'make.sh' (Core144, > line 1695 or 1700): >=20 > ... > mv $LFS/install/images/*.bz2 $BASEDIR >> $LOGFILE 2>&1 > ... >=20 > 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!? >=20 > Thanks for any hints. >=20 > Best, > Matthias --===============2811621241548519108==--