On Tue, Feb 04, 2020 at 10:28:10AM -0600, Bruce Dubbs via blfs-support wrote:
> On 2/3/20 11:36 PM, Alan Feuerbacher via blfs-support wrote:
> > Here's a bit more on the problem of Python-3.8.1 failing to install
> > all of the pip and pyvenv binaries to /usr/bin:
> >
> > Beginning in late December 2019 I built LFS development version
> > systemd successfully. The hard drive on which I built it is still
> > running, so I compared the Python-related contents (from
> > Python-3.7.5) of its /usr/bin with the contents of /usr/bin from
> > the Python-3.8.1 I've been dealing with. Here are some results:
> >
> > For the previous LFS Python-3.7.5 build:
> > #################
> > [root@localhost bin]# pwd
> > /usr/bin
> >
> > [root@localhost bin]# ll pip* pyenv* 2to3
> > ls: cannot access 'pyenv*': No such file or directory
> > ls: cannot access '2to3': No such file or directory
> > -rwxr-xr-x. 1 root root 507 Jan 2 13:56 pip
> > lrwxrwxrwx. 1 root root 9 Jan 2 13:56 pip-3 -> ./pip-3.7
> > -rwxr-xr-x. 1 root root 507 Jan 2 13:56 pip3
> > lrwxrwxrwx. 1 root root 8 Jan 2 13:56 pip-3.7 -> ./pip3.7
> > -rwxr-xr-x. 1 root root 507 Jan 2 13:56 pip3.7
> > -rwxr-xr-x. 1 root root 21080 Nov 28 08:35 pipewire
> > #################
> >
> > For the current LFS Python-3.8.1 build:
> > #################
> > (lfs chroot) root:/usr/bin$ pwd
> > /usr/bin
> >
> > (lfs chroot) root:/usr/bin$ ll pip* pyenv* 2to3
> > ls: cannot access 'pyenv*': No such file or directory
> > lrwxrwxrwx 1 root root 8 Feb 3 20:45 2to3 -> 2to3-3.8
> > lrwxrwxrwx 1 root root 6 Feb 3 20:46 pip3 -> pip3.8
> > #################
> >
> > I hope this helps in diagnosing the root problem.
>
> You are right pyvenv is no longer present. I've removed that from the book.
>
> -- Bruce
I'm just about to try to boot my latest build. One of the things I
do between LFS and first boot is rebuild Python3, so showing the
current output from ls -l will not be relevant to the problem.
But my log from the chroot build shows the following were all
installed (obviously it doesn't show which are symlinks) :
/usr/bin/2to3
/usr/bin/2to3-3.8
/usr/bin/easy_install-3.8
/usr/bin/idle3
/usr/bin/idle3.8
/usr/bin/pip3
/usr/bin/pip3.8
/usr/bin/pydoc3
/usr/bin/pydoc3.8
/usr/bin/python3
/usr/bin/python3-config
/usr/bin/python3.8
/usr/bin/python3.8-config
So for me at least /usr/bin/pip3.8 did get installed in LFS.
Also the bundled version of setuptools (in site-packages) which ISTR
is why we need pip.
But I would have thought that '--with-ensurepip=yes' would add ALL
of those, or NONE if omitted, so I don't understand how a dangling
symlink is likely.
Unfortunately, in best python "hide the details to avoid scaring
people" style my log from the build doesn't mention pip3.8 at all.
All I can see in that which is useful is
checking for GCC >= 4.7 __atomic builtins... yes
checking for ensurepip... upgrade
checking if the dirent structure of a d_type field... yes
Sorry, you can maybe see why I dislike python. Well, actually the
main reason is the importance of whitespace, but that only really
affects patching it.
ĸen
--
We had folksingers in the lower bar for six months back home where
I worked. In the end we had to get a man in with a ferret.
-- Polly, in "Interesting Times"
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
