On 17/04/2017 18:06, Ken Moffat wrote:
On Mon, Apr 17, 2017 at 02:47:24PM +0200, Pierre Labastie wrote:
make install && chmod -v 755 /usr/lib/libpython2.7.so.1.0 If "make install"
fails, the above instruction does not return an error code, so the script
does not stop (all the scripts created by jhalfs have "set -e" at the
beginning), and the failure may get unnoticed (specially when those
instructions have been working for ages). Now, the failure with urandom. I
too have the "defined but not used" warning about dev_urandom_xxx functions,
when compiling Python. The failure itself occurs much later, during
installation. Actually, it fails when calling system functions, and that may
be dependent on the host system, since it occurs while in chroot. I have to
build a kernel in order to run them from a booted system. Pierre
The follow-up re 'set -e' was enlightening. All I can say is that
my own scripts per-package generally use that (in a few packages I
turn it off for a short time, e.g. to run tests where my own logic
is too complex to add a simple '|| true'), and I've been building
Python2 in chroot for at least 5 years.
I will admit that nowadays I only usually build scons for my server,
but I think I built it on a desktop a few months ago when I was
investigating some possibly dependencies.
I looked at my log, but the install seems to be the main item
(nearly 5000 lines). Good luck with your .config.
As I anticipated, os.urandom() works on a booted machine...
And building scons too.
Note that I think it does not use /dev/urandom, but "getentropy()".
I am not sure when I last built LFS with debian 8 as a host.
I'd say around October last year, and at the time, it worked.
A lot of things have changed since then (glibc, directory tree,...).
Pierre
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
