On 1/31/2020 5:25 AM, Scott Andrews via blfs-support wrote:
On 1/31/20 6:28 AM, Stuart via blfs-support wrote:
On 2020-01-31 10:28, Ken Moffat via blfs-support wrote:
On Fri, Jan 31, 2020 at 09:10:23AM +0000, Stuart via blfs-support
wrote:
On 2020-01-30 23:23, Ken Moffat via blfs-support wrote:
On Thu, Jan 30, 2020 at 10:27:54PM +0000, Stuart via blfs-support
wrote:
On 2020-01-30 16:41, Alan Feuerbacher via blfs-support wrote:
On 1/30/2020 8:57 AM, Ken Moffat via blfs-support wrote:
Ok gimp still has the same issue so I plan today to rebuild all the
python3
modules and gimp using the later build of python3 and see if that
fixes
things.
Should I consider any other component rebuilds ?
Thanks
Stuart
Stuart,
I have no idea what is going wrong here. I still do not see why
gimp would be using python3. If it was my system I might be tempted
to use strace (but that usually has voluminous output and finding
anything interesting is sometimes hit or miss).
On my own systems I build sqlite, python2, and then rebuild python3
before booting.
Good luck.
?en
Ken
SNIP
I am not to the point where I am building gimp as of now, but these
issues are the exact reason that I use a package manager and build in
a clean chroot environment. I can then control which the packages
that get linked togetether.
What sort of package manager do you use?
Alan
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
