search

hercules-390 / hyperion

Hercules 390
Other
252 stars 68 forks source link

Unable to load dyncrypto #114

Closed jphartmann closed 8 years ago

jphartmann commented 8 years ago

atom is the out-of-source build directory.

[/usr/data/src/hercules/hyperion] find .. -name 'dyncrypt*'
../atom/crypto/.deps/dyncrypt.Plo
../atom/crypto/dyncrypt.lo
../atom/crypto/dyncrypt.la
../atom/crypto/.libs/dyncrypt.o
../atom/crypto/.libs/dyncrypt.so
../atom/crypto/.libs/dyncrypt.lai
../atom/crypto/.libs/dyncrypt.la

Is this location (crypto/.libs) deliberate or has something gone haywire? I should expect the .so in atom/.libs along with the remainder of the loadable modules.

I suspect that make was done in the crypto directory rather than in atom; that is considered a bad idea by makefile aficionados. Instead, include a makefile from crypto that adds the source modules with the source directory. 

HHC01603I modpath /usr/data/src/hercules/atom/crypto/.libs                                                                                                                        
HHC01603I ldmod dyncrypt                                                                                                                                                          
HHC01526I HDL: loading module dyncrypt...                                                                                                                                         
HHC00150I Crypto module loaded (c) Copyright 2003-2015 by Bernard van der Helm                                                                                                    
HHC00151I Activated facility: Message Security Assist                                                                                                                             
HHC00151I Activated facility: Message Security Assist Extension 1, 2, 3 and 4                                                                                                     
HHC01527I HDL: module dyncrypt loaded

I can do this circumvention in the configuration file:

# This seems to be a bug in crypto build:
modpath crypto/.libs
ldmod dyncrypt
# And now where device managers live
modpath .libs

However that will fail if I specify -p .libs on the hercules command.

jphartmann commented 8 years ago

Presumably the crypto directory will install the library in the right place, so this is an issue only when testing in the build directory.