On Sun, Apr 16, 2017 at 07:43:00PM +0200, Pierre Labastie wrote: > > > On 15/04/2017 19:49, Pierre Labastie wrote: > > > > On 15/04/2017 17:37, Roger Koehler wrote: > > > I just completed a new build of LFS SVN using jhalfs, including > > > blfs_root, but it bombed out when building scons: > > > > > > running install_lib > > > error: [Errno 38] Function not implemented > > > > > > I tried it manually following BLFS with same error. > > > I could reproduce it on a laptop with a core2duo, and debian 8 as a host. > Actually, after building LFS, mount virtual devices using the instructions > on the page "Preparing Virtual Kernel Filesystems", chroot using the > instructions on the page "Cleaning up". Then build Python 2.7.13, then run: > --------------------- > $ python > [...] > >>> import os > >>> os.urandom(1) > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > OSError: [Errno 38] Function not implemented
I only have 64-bit systems now, but your above example seems to work fine for me (it returned 'q'). > --------------------- > Note that _there is_ a file /dev/urandom, and that: > --------------- > $ hexdump /dev/urandom > --------------- > returns random output... > > Actually, looking at logs from building Python, I see that this error occurs > while building Python... > But it is not caught because of the "&&"... > I do not have the logs of working installations. > Pierre > Doing an install of scons to /tmp/SCONS appears to work for me. So, I'd offer you my log, but it is 442KB and I don't think the list will like that. gzip -9 brings it down to 38K, but that is awkward to read and quote. Is there any particular part of it which will be of interest ? Aside: I don't normally read the log, but it looks stupid: checking for g++... no configure: WARNING: By default, distutils will build C++ extension modules with "g++". If this is not intended, then set CXX on the configure command line. So, it claims it didn't find g++ but warns it will use it anyway. Stupid snake! I suppose that might be very much a homage to Python, Monty. The only obvious references to any sort of random are gcc warnings for -Wunused-function in Python/random.c, I assume the problem you saw was well before that ? Also, how does '&&' not catch it ? And before anyone replies: "I didn't expect the Spanish Inquisition for disparaging Python". ĸen -- `I shall take my mountains', said Lu-Tze. `The climate will be good for them.' -- Small Gods -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
