make -s prints additional noise on stderr. Can you get rid of the warnings from the bootstrap interpreter?

Do you have an example? I don't see any warnings. Unless you mean lines like

Deepfreezing Python/deepfreeze/importlib._bootstrap.c from Lib/importlib/_bootstrap.py

which are explicitly printed by the command in the Makefile (instead of the full command, which is several lines long due to the long and repeated filenames).

The bootstrap interpreter prints two warnings lines when the pybuilddir.txt file does not exist:

$ make clean
$ make -s 
...
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]

There is no cleanup target for the new directory. I think clean-retain-profile is the correct place to rm -rf Python/deepfreeze.

The bootstrap interpreter prints two warnings lines when the pybuilddir.txt file does not exist:

$ make clean
$ make -s 
...
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]

I've seen that too, but only in the CI. Maybe it's Linux only? I am at a loss for how to fix it. Should I just set PYTHONHOME=. in the deepfreeze calls?

There is no cleanup target for the new directory. I think clean-retain-profile is the correct place to rm -rf Python/deepfreeze.

There's a README.txt file that we don't want to delete, so I should probably rm -rf Python/deepfreeze/*.[ch]. Or is it a problem that that keeps the empty directory in an out-of-tree build?

@tiran any idea?

@tiran any idea?

You could try to use the bootstrap interpreter to generate sysconfig and pybuilddir.txt: main...tiran:deepfreeze-bootstrap

In the long run we might be able to replace PYTHON_FOR_REGEN with bootstrap interpreter, too.

@tiran, Does it look good now? All tests pass. I'll merge origin/main again and re-run the buildbots and then I hope to land this. We'll leave several things to future generations (or at least a later PR):

• Windows
• Avoid deep-freezing and rebuilding after every source change
• Replace PYTHON_FOR_REGEN with $(BOOTSTRAP)

🤖 New build scheduled with the buildbot fleet by @gvanrossum for commit 0c9de73 🤖

If you want to schedule another build, you need to add the "🔨 test-with-buildbots" label again.

The AMD64 FreeBSD buildbot is failing (https://buildbot.python.org/all/#/builders/203/builds/314/steps/3/logs/stdio), and AFAICT the cause is that its Make doesn't understand $<. Any suggestions? This part of Makefile.pre.in is generated code, so I could just expand it in the code generator (Tools/scripts/freeze_modules.py), like I had before. Or is there a trick to get this to work on FreeBSD?

I was not aware that bmake has a different syntax for autovars than gmake. I only develop with GNU make. I cannot find a common syntax that works with BSD make and GNU make. You have to go back to the old system.

I'm sorry for the extra work I caused.

🤖 New build scheduled with the buildbot fleet by @gvanrossum for commit 3e88103 🤖

If you want to schedule another build, you need to add the "🔨 test-with-buildbots" label again.

🤖 New build scheduled with the buildbot fleet by @gvanrossum for commit f40d138 🤖

If you want to schedule another build, you need to add the "🔨 test-with-buildbots" label again.