On Fri, Jun 19, 2020 at 01:14:01PM -0500, Bruce Dubbs via lfs-dev wrote:
> On 6/19/20 11:58 AM, Pierre Labastie via lfs-dev wrote:
> > On Fri, 2020-06-19 at 16:26 +0100, Ken Moffat via lfs-dev wrote:
> > > I've now been through my test logs for the new build (on my i7
> > > haswell).
> > >
> > >
On Fri, Jun 19, 2020 at 06:58:42PM +0200, Pierre Labastie via lfs-dev wrote:
> On Fri, 2020-06-19 at 16:26 +0100, Ken Moffat via lfs-dev wrote:
> > I've now been through my test logs for the new build (on my i7
> > haswell).
> >
> > Here are a few comments (in order of testing)
> >
> >
On 6/19/20 11:58 AM, Pierre Labastie via lfs-dev wrote:
On Fri, 2020-06-19 at 16:26 +0100, Ken Moffat via lfs-dev wrote:
I've now been through my test logs for the new build (on my i7
haswell).
Here are a few comments (in order of testing)
bison-3.6.3
---
Here, I strongly disagree
On 2020-06-19 18:58 +0200, Pierre Labastie via lfs-dev wrote:
> On Fri, 2020-06-19 at 16:26 +0100, Ken Moffat via lfs-dev wrote:
> > I've now been through my test logs for the new build (on my i7
> > haswell).
> >
> > Here are a few comments (in order of testing)
> >
> > glibc-2.31.0
> >
On Fri, 2020-06-19 at 16:26 +0100, Ken Moffat via lfs-dev wrote:
> I've now been through my test logs for the new build (on my i7
> haswell).
>
> Here are a few comments (in order of testing)
>
> glibc-2.31.0
>
>
> We say "misc/tst-ttyname is known to fail in the LFS chroot
>
I've now been through my test logs for the new build (on my i7
haswell).
Here are a few comments (in order of testing)
glibc-2.31.0
We say "misc/tst-ttyname is known to fail in the LFS chroot
environment." But for me it was skipped (I'm running a 5.7.2
kernel, with 5.7.2 headers