On 1/31/20 5:30 PM, Ken Moffat via blfs-support wrote:
snip
At the moment, we do not know _why_ Stuart has had this problem, only that python3 is involved. Unless anyone is eventually able to say either a) python3 is pulled in by <some-package> and python3 needs to be (re)built after <some-other-package> has been installed or b) there is an odd build or buildscript fubar <with details> that results in this problem then saying that building with all of the LFS packages in your chroot _will_ solve the problem is an assertion. But since nobody else has hit the problem at this point (maybe because there are many possible build orders in BLFS) it's going to be hard to track down the problem. Of course, if your approach when you get to gimp enables you to answer option (a) above then I'll be all ears. ĸen
I did not say this will "fix" his issue, my post was about how I build things. I never have to rebuild python3 after any package is installed. Ever package uses python as it was build in Chapter 6.
In part "a" python3 would not get pulled in by "some package" it is already there. Why would python3 need rebuilt?
Now for "b" His issue may indeed be with an unwanted dependency. When you do not build your packages in a clean environment there is no way to get a repeatable build and with out a package manager there is no way to "backup" and correct an issue with a previous package. One can not simply rebuild it as the environment you now have can not be made as it was when you built the package the first. Hence you must "start over".
It also could be a foobar. As I previous stated, the environment is polluted by constantly adding package, all be it haphazardly. No one can reproduce the environment that gimp was built in as no one can be sure of the state the build is in. This is indeed why I build packages in a clean and reproducible environment.
-- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
