Re^4: PAR::Packer - 'dll not found' error on run

Thank you for your help on this matter. I fear that I am in deep waters here.

The error message from your suggested 'debug' insert is as follows:

errno: #9 ('Bad file descriptor') doesn't match expected value (#22)

At one point I had working code that used this module. I must have (unknowingly) bolluxed it with a subsequent install.

EDIT: it appears to be looking for a file called "auto/Net/SSLeay/OP_ALL.al". Im trying to track this down.

EDIT: didn't find any trace of "OP_ALL.al". Strangely enough I did find 'randomize.al'... so something isn't setup properly on my box.

Comment on Re^4: PAR::Packer - 'dll not found' error on run

Replies are listed 'Best First'.
Re^5: PAR::Packer - 'dll not found' error on run by almut (Canon) on Aug 21, 2007 at 20:26 UTC
Just two things to note: the errno 9 ('Bad file descriptor') is probably being carried over from some other previous system error, though this should - in theory - not happen, as the XS code behind the `constant` routine is setting `errno = 0` before doing anything else... Another strange thing is that the `OP_ALL` is clearly one of the constants I was talking about — which means it should definitely not be treated as an autoload routine. So, as it looks, your DLL is implementing some weird inverse logic ;) Are you sure you've got the right one? (One could hypothesize that in case you've got the wrong DLL, and it doesn't know about the constants it's supposed to handle... in combination with the communication via errno generally not working... the constant lookup might eventually turn into some bogus `OP_ALL.al` autoload attempt... But why would such a DLL pass version checks etc. and be loaded at all??) Hmm, maybe you should try to replace that `SSLeay.dll` with a fresh one from a new and clean installation. Other than that, I haven't got the foggiest what's going on on that machine...	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^5: PAR::Packer - 'dll not found' error on run
by almut (Canon) on Aug 21, 2007 at 20:26 UTC

Just two things to note: the errno 9 ('Bad file descriptor') is probably being carried over from some other previous system error, though this should - in theory - not happen, as the XS code behind the constant routine is setting errno = 0 before doing anything else... Another strange thing is that the OP_ALL is clearly one of the constants I was talking about — which means it should definitely not be treated as an autoload routine.

So, as it looks, your DLL is implementing some weird inverse logic ;) Are you sure you've got the right one? (One could hypothesize that in case you've got the wrong DLL, and it doesn't know about the constants it's supposed to handle... in combination with the communication via errno generally not working... the constant lookup might eventually turn into some bogus OP_ALL.al autoload attempt... But why would such a DLL pass version checks etc. and be loaded at all??) Hmm, maybe you should try to replace that SSLeay.dll with a fresh one from a new and clean installation. Other than that, I haven't got the foggiest what's going on on that machine...

[reply]
[d/l]
[select]