On 09/11/2018 12:23 AM, Michael Shell wrote:
On Mon, 10 Sep 2018 11:52:50 -0500
Bruce Dubbs wrote:
I do not want to start documenting failures that may be host system
dependent.
OK, but what about chapter 6? Make check is recommended there (actually
make check is also shown in chapter
On Mon, 10 Sep 2018 11:52:50 -0500
Bruce Dubbs wrote:
> I do not want to start documenting failures that may be host system
> dependent.
OK, but what about chapter 6? Make check is recommended there (actually
make check is also shown in chapter 5.31) and it is going to require such
an
On 09/10/2018 07:14 AM, Michael Shell wrote:
On Sun, 9 Sep 2018 12:59:49 +0200
Christian Friedl wrote:
* It would seem that the testsuite for tar (Chapter 5.31: Tar-1.30)
created one gigantic file, aptly named BIGFILE, that ate up my whole lfs
partition (all of 5.3GB that were left at that
On Mon, Sep 10, 2018 at 08:50:19AM +0200, Christian Friedl wrote:
>
> For investigation, I just ran make check check on a newly wget'ed (wgotten?)
> tar-1.30.tar.xz on my virtual machine in the cloud.
>
> "Test # 154: listing sparse files bigger than 2^33 B" created a file
> named
On Sun, 9 Sep 2018 12:59:49 +0200
Christian Friedl wrote:
> * It would seem that the testsuite for tar (Chapter 5.31: Tar-1.30)
> created one gigantic file, aptly named BIGFILE, that ate up my whole lfs
> partition (all of 5.3GB that were left at that point).
IMHO, we should add a warning to
Hi Bruce,
thanks for your quick reply!
On 2018-09-09 12:06, Bruce Dubbs wrote:
>
> Are you removing the expanded package directories after each package?
>
Oh, yes. I forgot it in about 3 or 4 scripts, but that didn't impact the
build process a lot.
For investigation, I just ran make check
On 09/09/2018 05:59 AM, Christian Friedl wrote:
Ths is my third attempt to create a LFS, finally
heeding the sage advice to put it all into repeatable scripts (thank
goodness for that!).
Just a little incident report:
I included a "make check" everywhere even in chapter 5, just to be on
the
