https://community.hpe.com/t5/operating-system-hp-ux/shl-load-returns-error-22/m-p/2734354#M721872 Hi<BR /><BR /><BR />I can guess that you need the latest linker patch and then use the LD_PRELOAD functionality to avoide this<BR /><BR />You can use the LD_PRELOAD environment variable to load a shared library that contains thread-local storage to avoid the following error when loading the library dynamically: <BR /><BR /> /usr/lib/dld.sl: Can't shl_load() a library containing Thread Local Storage: /usr/lib/libpthread.1<BR /><BR />Also error 22<BR /><BR />The load order and symbol resolution order may be different in a PA32 program than in the same PA64 program because the dynamic loader uses depth-first search order in PA32 mode and breadth-first search order in PA64 mode. <BR />The dynamic loader uses the LD_PRELOAD environment variable even if you use the +noenvvar in the link line. This insures that LD_PRELOAD is enabled even in a +compat link. The LD_PRELOAD variable is always enabled except for setuid and setgid programs. <BR /><BR />Note: Using LD_PRELOAD can cause a core dump when used with applications which mix shared and archived libraries, especially when both the shared library and the application are built with aC++ or use libc. <BR /><BR />You can specify multiple libraries as part of the LD_PRELOAD environment variable. Separate the libraries by spaces or colons as in LD_LIBRARY_PATH. (Multi-byte support is not provided as part of parsing the LD_PRELOAD library list). You can specify LD_PRELOAD libraries with absolute paths or relative paths. The LD_PRELOAD libraries can also consist of just the library names, in which case the dynamic loader uses the directory path list in the environment variables LD_LIBRARY_PATH and/or SHLIB_PATH or the embedded path list (if enabled) to search for the libraries. <BR /><BR />The dynamic loader does not issue an error or warning message if it cannot find a library specified by LD_PRELOAD. However, if it does not find a dependent of the LD_PRELOAD libraries, the dynamic loader issues the same error message as if the LD_PRELOAD library is specified in the link line. <BR /><BR /><BR /><BR />See man dld.sl when patch is loaded<BR /><BR /><BR /> Steve steel<BR /> Thu, 30 May 2002 10:34:57 GMT Steve Steel 2002-05-30T10:34:57Z https://community.hpe.com/t5/operating-system-hp-ux/shl-load-returns-error-22/m-p/2734353#M721871 Thu, 30 May 2002 10:26:26 GMT https://community.hpe.com/t5/operating-system-hp-ux/shl-load-returns-error-22/m-p/2734353#M721871 ArieMo 2002-05-30T10:26:26Z https://community.hpe.com/t5/operating-system-hp-ux/shl-load-returns-error-22/m-p/2734354#M721872 Hi<BR /><BR /><BR />I can guess that you need the latest linker patch and then use the LD_PRELOAD functionality to avoide this<BR /><BR />You can use the LD_PRELOAD environment variable to load a shared library that contains thread-local storage to avoid the following error when loading the library dynamically: <BR /><BR /> /usr/lib/dld.sl: Can't shl_load() a library containing Thread Local Storage: /usr/lib/libpthread.1<BR /><BR />Also error 22<BR /><BR />The load order and symbol resolution order may be different in a PA32 program than in the same PA64 program because the dynamic loader uses depth-first search order in PA32 mode and breadth-first search order in PA64 mode. <BR />The dynamic loader uses the LD_PRELOAD environment variable even if you use the +noenvvar in the link line. This insures that LD_PRELOAD is enabled even in a +compat link. The LD_PRELOAD variable is always enabled except for setuid and setgid programs. <BR /><BR />Note: Using LD_PRELOAD can cause a core dump when used with applications which mix shared and archived libraries, especially when both the shared library and the application are built with aC++ or use libc. <BR /><BR />You can specify multiple libraries as part of the LD_PRELOAD environment variable. Separate the libraries by spaces or colons as in LD_LIBRARY_PATH. (Multi-byte support is not provided as part of parsing the LD_PRELOAD library list). You can specify LD_PRELOAD libraries with absolute paths or relative paths. The LD_PRELOAD libraries can also consist of just the library names, in which case the dynamic loader uses the directory path list in the environment variables LD_LIBRARY_PATH and/or SHLIB_PATH or the embedded path list (if enabled) to search for the libraries. <BR /><BR />The dynamic loader does not issue an error or warning message if it cannot find a library specified by LD_PRELOAD. However, if it does not find a dependent of the LD_PRELOAD libraries, the dynamic loader issues the same error message as if the LD_PRELOAD library is specified in the link line. <BR /><BR /><BR /><BR />See man dld.sl when patch is loaded<BR /><BR /><BR /> Steve steel<BR /> Thu, 30 May 2002 10:34:57 GMT https://community.hpe.com/t5/operating-system-hp-ux/shl-load-returns-error-22/m-p/2734354#M721872 Steve Steel 2002-05-30T10:34:57Z