On Mon, 2021-02-08 at 19:36 +0100, Pierre Labastie via lfs-dev wrote:
> On Fri, 2021-02-05 at 17:40 +, Ken Moffat via lfs-dev wrote:
> > On Fri, Feb 05, 2021 at 10:39:08AM -0600, Bruce Dubbs via lfs-dev
> > wrote:
> > > On 2/5/21 6:48 AM, Ken Moffat via lfs-dev wrote:
> > > > While replying to
On Fri, 2021-02-05 at 17:40 +, Ken Moffat via lfs-dev wrote:
> On Fri, Feb 05, 2021 at 10:39:08AM -0600, Bruce Dubbs via lfs-dev
> wrote:
> > On 2/5/21 6:48 AM, Ken Moffat via lfs-dev wrote:
> > > While replying to Frans on -support re his inability to build
> > > glibc-2.33, I glanced at the b
On Fri, Feb 05, 2021 at 10:39:08AM -0600, Bruce Dubbs via lfs-dev wrote:
> On 2/5/21 6:48 AM, Ken Moffat via lfs-dev wrote:
> > While replying to Frans on -support re his inability to build
> > glibc-2.33, I glanced at the binutils bugs
> > https://www.mail-archive.com/bug-binutils@gnu.org/ and sai
On 2/5/21 6:48 AM, Ken Moffat via lfs-dev wrote:
While replying to Frans on -support re his inability to build
glibc-2.33, I glanced at the binutils bugs
https://www.mail-archive.com/bug-binutils@gnu.org/ and said that
2.36 might be buggy. At that time I hadn't read all the links
gurgle found fo
While replying to Frans on -support re his inability to build
glibc-2.33, I glanced at the binutils bugs
https://www.mail-archive.com/bug-binutils@gnu.org/ and said that
2.36 might be buggy. At that time I hadn't read all the links
gurgle found for me. One of them is
https://www.linuxquestions.or
