From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Fischer To: development@lists.ipfire.org Subject: Re: 'cannot access'-message after building 64bit Date: Wed, 20 May 2020 13:38:33 +0200 Message-ID: <4cee5464-65df-8a19-c147-f20c20b9de5f@ipfire.org> In-Reply-To: <8FE22679-B29A-49D7-B27D-D30D55532EA5@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8805418401850118998==" List-Id: --===============8805418401850118998== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, On 20.05.2020 10:07, Michael Tremer wrote: > Hi, >=20 > This always shows up, because we do not have any images compressed as bzip2= any more on most architectures. >=20 > You can just ignore it, or add a 2>/dev/null to the command, so that the me= ssage won=E2=80=99t be shown. Thanks - I figured something like this. But why doesn't this message appear in the nightly x86_64 'build_log'? Best, Matthas > -Michael >=20 >> 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 >=20 --===============8805418401850118998==--