On 1/31/20 7:30 PM, Ken Moffat via blfs-support wrote:
On Fri, Jan 31, 2020 at 06:48:56PM -0500, Scott Andrews via blfs-support wrote:
On 1/31/20 6:26 PM, Bruce Dubbs via blfs-support wrote:
On 1/31/20 5:01 PM, Scott Andrews via blfs-support wrote:
In part "a" python3 would not get pulled in by "some package" it is
already there. Why would python3 need rebuilt?
As it says in BLFS:
"Python 3 was installed in LFS. The only reason to rebuild it here is if
optional modules are needed."
The modules we know about are in Berkeley DB, SQLite, and Tk. I am not
aware that any packages in BLFS actually need these modules.
-- Bruce
I have built sqlite and I don't rebuild python3 and I build Berkeley DB as
it is needed by rpm, Both function without problems with out rebuilding
python3 for me. rpm exercises Berkeley DB as does sqlite by yum.
I am missing some thing here?
The rebuild of python3 (and for some of us, rebuilding python2 after
adding extra possible dependencies) is so that something else can
use the added python modules.
ĸen
sqlite builds the required/extra python modules. Other packages can use
them as long as I have sqlite installed. Again with no need to rebuild
pythion.
I am still failing to understand why python needs rebuilt, The modules
are built during the sqlite/or other package that has python modules.
build. I have never had to rebuild it in all the years I have been do
this using the RPi platform to create network servers. It has never
failed with me never rebuilding python3 or 2. I simply install sqlite
which has the new modules and then build the package. It works
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
