Re: [lfs-dev] Python 3.7.2 build errors using Glibc 2.29

2019-02-12 Thread hykwok1--- via lfs-dev
>On 02/10/2019 10:07 AM, Xi Ruoyao via lfs-dev wrote:
>> On 2019-02-10 09:54 -0600, Bruce Dubbs via lfs-dev wrote:
>>> On 02/10/2019 06:41 AM, Pierre Labastie via lfs-dev wrote:
 On 10/02/2019 08:45, Brandon Murry via lfs-dev wrote:
> Hi, I hope this is the right place to put this.
> I've been attempting to build Linux From Scratch from the development book
> using Systemd. One of the big new changes is an early build of Python 
> 3.7.2
> for the newest version of Glibc 2.29. I've tried this about 6 times 
> trying all
> different setups within the host environment. Compiling Python 3.7.2 
> during
> chapter 5 produces a ton of "error: unknown type name" for standard C 
> libraries.
> Python fails to build the majority of it's modules. When Glibc is rebuilt
> during chapter 6, it fails due to missing Python modules. Haven't seen any
> hints about this from LFS or on the net, so curious to see if I'm the 
> only one
> having this issue.
> Thanks,
> Brandon
>

 All I can tell is that I've built LFS SVN twice (in a 64 bit and in a 32 
 bit
 VM) since glibc-2.29 has been put in, and I haven't seen those errors.

 Like Thomas, I suggest you check the 2.2 host system requirements page. 
 Note
 that version-check.sh does not necessarily tell if something goes wrong: 
 the
 output has to be compared with the versions given above in the page.
>>>
>>> We saw that problem in testing.  Python in Chapter 5 needs glibc 2.26 or
>>> later on the host system.  We did change that in the host system
>>> requirements.
>> 
>> But this is very strange.  Chapter 5 Python should link to Glibc-2.29 built 
>> in
>> temporary toolchain, instead of Glibc of the host.
>It has to do with headers.  It's possible that with the right CFLAGS 
>setting we can get Python in Chapter 5 to build with the headers in 
>/tools.  The problem we saw was with Debian stable.  If someone wants to 
>investigate, then we can update the book to support older versions of glibc.
>   -- Bruce

I also encountered same problem that I could not build Python 3 in the chapter 
5.30 so that I counld not build the GLibc in the chapter 6.9.

My host system is Ubuntu 18.04.02. The glibc version of the host system is 2.27 
and the gcc version is 7.3.0. So I am sure the host requirement is OK for the 
latest LFS.

Actually, I found that I could build the Python compiler successfully but I 
could not build the Python system modules.
I checked the gcc version was 8.2.0 so the host compiler was not used. I also 
used the "ldd" command to check the generated Python compiler and it linked to 
the "/tools" system libraries.

Finally, I re-ordered the build order as follow to fix "my" problem:

Chapter 5.29 --> Chapter 5.31 to Chapter 5.36 (I did build the Python in the 
Chapter 5 section)
Chapter 6.7 --> Chapter 6.8 --> Chapter 5.30 --> Chapter 6.9 (I built the 
Python before Glibc in the chapter 6 section)

The reason is: I want to build the Python modules in the "chroot" environment 
to ensure that no host's header file will be used.
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: [lfs-dev] Python 3.7.2 build errors using Glibc 2.29

2019-02-10 Thread Bruce Dubbs via lfs-dev

On 02/10/2019 10:07 AM, Xi Ruoyao via lfs-dev wrote:

On 2019-02-10 09:54 -0600, Bruce Dubbs via lfs-dev wrote:

On 02/10/2019 06:41 AM, Pierre Labastie via lfs-dev wrote:

On 10/02/2019 08:45, Brandon Murry via lfs-dev wrote:

Hi, I hope this is the right place to put this.
I've been attempting to build Linux From Scratch from the development book
using Systemd. One of the big new changes is an early build of Python 3.7.2
for the newest version of Glibc 2.29. I've tried this about 6 times trying all
different setups within the host environment. Compiling Python 3.7.2 during
chapter 5 produces a ton of "error: unknown type name" for standard C libraries.
Python fails to build the majority of it's modules. When Glibc is rebuilt
during chapter 6, it fails due to missing Python modules. Haven't seen any
hints about this from LFS or on the net, so curious to see if I'm the only one
having this issue.
Thanks,
Brandon



All I can tell is that I've built LFS SVN twice (in a 64 bit and in a 32 bit
VM) since glibc-2.29 has been put in, and I haven't seen those errors.

Like Thomas, I suggest you check the 2.2 host system requirements page. Note
that version-check.sh does not necessarily tell if something goes wrong: the
output has to be compared with the versions given above in the page.


We saw that problem in testing.  Python in Chapter 5 needs glibc 2.26 or
later on the host system.  We did change that in the host system
requirements.


But this is very strange.  Chapter 5 Python should link to Glibc-2.29 built in
temporary toolchain, instead of Glibc of the host.


It has to do with headers.  It's possible that with the right CFLAGS 
setting we can get Python in Chapter 5 to build with the headers in 
/tools.  The problem we saw was with Debian stable.  If someone wants to 
investigate, then we can update the book to support older versions of glibc.


  -- Bruce

--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: [lfs-dev] Python 3.7.2 build errors using Glibc 2.29

2019-02-10 Thread Xi Ruoyao via lfs-dev
On 2019-02-10 09:54 -0600, Bruce Dubbs via lfs-dev wrote:
> On 02/10/2019 06:41 AM, Pierre Labastie via lfs-dev wrote:
> > On 10/02/2019 08:45, Brandon Murry via lfs-dev wrote:
> > > Hi, I hope this is the right place to put this.
> > > I've been attempting to build Linux From Scratch from the development book
> > > using Systemd. One of the big new changes is an early build of Python 
> > > 3.7.2
> > > for the newest version of Glibc 2.29. I've tried this about 6 times 
> > > trying all
> > > different setups within the host environment. Compiling Python 3.7.2 
> > > during
> > > chapter 5 produces a ton of "error: unknown type name" for standard C 
> > > libraries.
> > > Python fails to build the majority of it's modules. When Glibc is rebuilt
> > > during chapter 6, it fails due to missing Python modules. Haven't seen any
> > > hints about this from LFS or on the net, so curious to see if I'm the 
> > > only one
> > > having this issue.
> > > Thanks,
> > > Brandon
> > > 
> > 
> > All I can tell is that I've built LFS SVN twice (in a 64 bit and in a 32 bit
> > VM) since glibc-2.29 has been put in, and I haven't seen those errors.
> > 
> > Like Thomas, I suggest you check the 2.2 host system requirements page. Note
> > that version-check.sh does not necessarily tell if something goes wrong: the
> > output has to be compared with the versions given above in the page.
> 
> We saw that problem in testing.  Python in Chapter 5 needs glibc 2.26 or 
> later on the host system.  We did change that in the host system 
> requirements.

But this is very strange.  Chapter 5 Python should link to Glibc-2.29 built in
temporary toolchain, instead of Glibc of the host.
-- 
Xi Ruoyao 
School of Aerospace Science and Technology, Xidian University

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: [lfs-dev] Python 3.7.2 build errors using Glibc 2.29

2019-02-10 Thread Bruce Dubbs via lfs-dev

On 02/10/2019 06:41 AM, Pierre Labastie via lfs-dev wrote:

On 10/02/2019 08:45, Brandon Murry via lfs-dev wrote:

Hi, I hope this is the right place to put this.
I've been attempting to build Linux From Scratch from the development book
using Systemd. One of the big new changes is an early build of Python 3.7.2
for the newest version of Glibc 2.29. I've tried this about 6 times trying all
different setups within the host environment. Compiling Python 3.7.2 during
chapter 5 produces a ton of "error: unknown type name" for standard C libraries.
Python fails to build the majority of it's modules. When Glibc is rebuilt
during chapter 6, it fails due to missing Python modules. Haven't seen any
hints about this from LFS or on the net, so curious to see if I'm the only one
having this issue.
Thanks,
Brandon



All I can tell is that I've built LFS SVN twice (in a 64 bit and in a 32 bit
VM) since glibc-2.29 has been put in, and I haven't seen those errors.

Like Thomas, I suggest you check the 2.2 host system requirements page. Note
that version-check.sh does not necessarily tell if something goes wrong: the
output has to be compared with the versions given above in the page.


We saw that problem in testing.  Python in Chapter 5 needs glibc 2.26 or 
later on the host system.  We did change that in the host system 
requirements.


  -- Bruce

--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: [lfs-dev] Python 3.7.2 build errors using Glibc 2.29

2019-02-10 Thread Pierre Labastie via lfs-dev
On 10/02/2019 08:45, Brandon Murry via lfs-dev wrote:
> Hi, I hope this is the right place to put this.
> I've been attempting to build Linux From Scratch from the development book
> using Systemd. One of the big new changes is an early build of Python 3.7.2
> for the newest version of Glibc 2.29. I've tried this about 6 times trying all
> different setups within the host environment. Compiling Python 3.7.2 during
> chapter 5 produces a ton of "error: unknown type name" for standard C 
> libraries.
> Python fails to build the majority of it's modules. When Glibc is rebuilt
> during chapter 6, it fails due to missing Python modules. Haven't seen any
> hints about this from LFS or on the net, so curious to see if I'm the only one
> having this issue.
> Thanks,
> Brandon
> 

All I can tell is that I've built LFS SVN twice (in a 64 bit and in a 32 bit
VM) since glibc-2.29 has been put in, and I haven't seen those errors.

Like Thomas, I suggest you check the 2.2 host system requirements page. Note
that version-check.sh does not necessarily tell if something goes wrong: the
output has to be compared with the versions given above in the page.

Pierre
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: [lfs-dev] Python 3.7.2 build errors using Glibc 2.29

2019-02-10 Thread Thomas Trepl via lfs-dev
Am Samstag, den 09.02.2019, 23:45 -0800 schrieb Brandon Murry via lfs-
dev:
> Hi, I hope this is the right place to put this.
> I've been attempting to build Linux From Scratch from the development book 
> using Systemd. One of the big new changes is an early build of Python 3.7.2 
> for the newest version of Glibc 2.29. I've tried this about 6 times trying 
> all different setups within the host environment. Compiling Python 3.7.2 
> during chapter 5 produces a ton of "error: unknown type name" for standard C 
> libraries.
> Python fails to build the majority of it's modules. When Glibc is rebuilt 
> during chapter 6, it fails due to missing Python modules. Haven't seen any 
> hints about this from LFS or on the net, so curious to see if I'm the only 
> one having this issue.
> Thanks,
> Brandon

Whats your host system?  (Distro, architecture etc.)
Did you run the check script of chapter 2.2 ?
Can you provide a snippet of the log where the errors are shown?

--
Thomas

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

[lfs-dev] Python 3.7.2 build errors using Glibc 2.29

2019-02-09 Thread Brandon Murry via lfs-dev
Hi, I hope this is the right place to put this.
I've been attempting to build Linux From Scratch from the development book
using Systemd. One of the big new changes is an early build of Python 3.7.2
for the newest version of Glibc 2.29. I've tried this about 6 times trying
all different setups within the host environment. Compiling Python 3.7.2
during chapter 5 produces a ton of "error: unknown type name" for standard
C libraries.
Python fails to build the majority of it's modules. When Glibc is rebuilt
during chapter 6, it fails due to missing Python modules. Haven't seen any
hints about this from LFS or on the net, so curious to see if I'm the only
one having this issue.
Thanks,
Brandon
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page