This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: Tools/freeze "make" gets missing file error with unix shared builds
Type: Stage: needs patch
Components: Demos and Tools Versions: Python 3.4, Python 3.5
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: lemburg, loewis, meador.inge, ned.deily
Priority: normal Keywords:

Created on 2015-02-07 10:48 by ned.deily, last changed 2022-04-11 14:58 by admin.

Messages (1)
msg235518 - (view) Author: Ned Deily (ned.deily) * (Python committer) Date: 2015-02-07 10:48
While investigating another freeze-related issue, I found that Tools/freeze seems to not work when used with an installed shared unix build.  The symptom is that the linkage step in the freeze-produced Makefile fails with:

gcc -pthread  -Xlinker -export-dynamic config.o frozen.o M___future__.o [...] M_zipfile.o /py/3x/unix/root/lib/python3.4/config-3.4dm/   -lpthread -ldl  -lutil -lm  -o hello
gcc: error: /py/3x/unix/root/f/../lib/python3.4/config-3.4dm/ No such file or directory
Makefile:505: recipe for target 'hello' failed
make: *** [hello] Error 1

The problem is that the freeze linkage step is looking for the python library with a shared library extension (in this case, '.so') in the config-3.xmm directory but the library is installed as a static archive ('.a') there:


I'm unfamiliar with freeze and its history but it looks like the problem was introduced by the changes for Issue11824, in particular this:

-    libs = [os.path.join(binlib, 'libpython$(VERSION).a')]
+    libs = [os.path.join(binlib, '$(LDLIBRARY)')]

The Python Makefile target "libainstall" installs the Python library in the config* dir:
	@if test -d $(LIBRARY); then :; else \
		if test "$(PYTHONFRAMEWORKDIR)" = no-framework; then \
			if test "$(SHLIB_SUFFIX)" = .dll; then \
			else \
			fi; \
		else \
			echo Skip install of $(LIBRARY) - use make frameworkinstall; \
		fi; \

So, if I understand the cases correctly, for non-".dll" cases, the library is installed in the config* directory as file name $LIBRARY.  But the changed code in the freeze-generated Makefile looks for the library as $LDLIBRARY.  For static Python builds, $LIBRARY and $LDLIBRARY are (always?) the same, but for shared builds, they are (usually) not, for example:

    LDLIBRARY = ""
    LIBRARY = "libpython3.4dm.a"

I'm not sure what the complete solution should be but clearly what is there now is not right for shared unix builds.
Date User Action Args
2022-04-11 14:58:12adminsetgithub: 67594
2015-02-07 10:48:02ned.deilycreate