>> Personally, I don't find adding that handful of lines to my build
>> scripts at all cumbersome. But, yes, if one is typing it all on the
>> console line... Well, that's why I haven't done that since LFS-4.1!
>
>I take it you don't use jhalfs. How do you build your scripts?
>
>Alan
I don't.
On 5/7/2017 1:28 AM, Paul Rogers wrote:
For automake, the process of removing the bad tests is cumbersome, but
we do say: Four tests are known to fail.
Personally, I don't find adding that handful of lines to my build
scripts at all cumbersome. But, yes, if one is typing it all on the
> Date: Sun, 07 May 2017 22:09:26 +0100
> From: lf...@cruziero.com (akhiezer)
>
[...]
> Cc'd to lfs-dev re 'freecode', further below.
s/free/fresh/
>
[...]
> http://freecode.com/users/esr
( - ~ignore that link).
>
[...]
>
akh
--
--
(
To: clfs-supp...@lists.clfs.org
Cc: lfs-dev@lists.linuxfromscratch.org
)
Cc'd to lfs-dev re 'freecode', further below.
Page 'the-end/whatnow' contains defunct 'freshmeat' link:
https://github.com/bradfa/clfs-embedded/blob/2017.04-fixes/BOOK/the-end/whatnow.xml
> It would be useful to know which pages you consider a problem. I've
> recently fixed glibc, vim, and am in the process of fixing the one in
> flex via an updated patch.
I also accepted a failure in my tar-1.28 fallback, sparse3 IIRC. AIUI
it tries to allocate a huge file, but I'm building in
