Re: 'cannot access'-message after building 64bit

[Matthias Fischer <matthias.fischer@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]

Hi,

On 20.05.2020 10:07, Michael Tremer wrote:
> Hi,
> 
> This always shows up, because we do not have any images compressed as bzip2 any more on most architectures.
> 
> You can just ignore it, or add a 2>/dev/null to the command, so that the message won’t 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
> 
>> On 20 May 2020, at 08:05, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>> 
>> 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
>