This post gives some of the error messages I received, and the actions I took to resolve the problems.
FSUM3008 Specify a file with the correct suffix (.c, .i, .s, .o, .x, .p, .I, or .a), or a corresponding data set name, instead of -o ….
I got this during a Python C extension build. You need
export _C89_CCMODE=1
export _C99_CCMODE=1
export _Ccc_CCMODE=1
export _CC_CCMODE=1
export _CXX_CCMODE=1
export _C89_CCMODE=1
export _CC_EXTRA_ARGS=1
export _CXX_EXTRA_ARGS=1
export _C89_EXTRA_ARGS=1
Before doing any builds.
Python builds
DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives.
Easy fix which no one tells you about (it took me 3 days to find this). Add
import setuptools
to the top of the file.
COLIN:/u/pymqi: >python3 -m build
No module named build.main; ‘build’ is a package and cannot be directly executed
You have a build directory in your project
https://pypi.org/search/?q=build
then install it
python3 setup.py bdist_wheel … error: invalid command ‘bdist_wheel’
I needed “import setuptools” at the top of the setup.py file. I also needed wheel to be installed.
CEE3501S The module libpython3.10.so was not found.
I was trying to do
import ctypes
from ctypes.util import find_library
testlib = ctypes.CDLL(“… “)
This file was in /u/tmp/python/usr/lpp/IBM/cyp/v3r10/pyz/lib/
You need
export LIBPATH=/u/tmp/python/usr/lpp/IBM/cyp/v3r10/pyz/lib/:$LIBPATH
python3 ….
CEE3587S A call was made to a function in the AMODE 31 DLL //ADD2 from an AMODE 64 caller.
I was trying to call a C program from Python – but i was built with 31 bit mode – not 64 bit mode.
You need to compile it with LP64, and bind in 64 bit mode, and use //BIND.SYSLIB DD DISP=SHR,DSN=CEE.SCEEBND2
ImportError: CEE3512S An HFS load of module /u/tmp/py/mq.so failed. The system return code was 0000000130; the reason code was 0BDF0
I had a bind error. When I fixed it – it worked.
The IBM documentation says
A package shared library may get tagged incorrectly when using the xlc utility. Verify that the shared library is untagged by running the following line:
ls -alT
If the file is tagged, with the output being similar to the following line:
t ISO8859-1 T=on
you can remove the tag with the following command:
chtag -r <filename.so>
ColinPaice 