p2pool for core 0.16 question
-
If you are on a windows server, it could be placed into the directory, where the windows dll are located. normally it should work, if the dll is in the same directory, where the p2pool binaries are, but honnestly I’ve no real clue, where windows searches for dll files.
-
I don’t have anything like a neoscrypt.dll file… I’ve got a neoscrypt.pyd and a neoscrypt.egg could one of these work?
IF so, where would the p2pool code be looking for the dlls?
-
When you did the
C:\Python27\python.exe setup.py build --compile=mingw32 installdid you get any output? it should compile the neoscrypt module, so there should be some output of your c-compiler on the console/cmd window.
Can you paste that output?
Normally the command also should create a directory ‘build’ under the neoscrypt directory, which temporary holds the files.
if you don’t have that directory try
C:\Python27\python.exe setup.py build --compile=mingw32and check for the directory and it’s content.
-
When I run the setup.py for neoscrypt this is the output in the console;
C:\Python27\Lib\site-packages\p2pool-neoscrypt-master\neoscrypt>python C:\Python27\Lib\site-packages\p2pool-neoscrypt-master\neoscrypt\setup.py build --compile=mingw32 install
running build
running build_ext
running install
running install_lib
running install_egg_info
Removing C:\Python27\Lib\site-packages\neoscrypt-1.0-py2.7.egg-info
Writing C:\Python27\Lib\site-packages\neoscrypt-1.0-py2.7.egg-infoC:\Python27\Lib\site-packages\p2pool-neoscrypt-master\neoscrypt>pause
Press any key to continue . . .Which appears like it works correctly as the build directory is created.
-
@j1732 said in p2pool for core 0.16 question:
running install_lib
…
Writing C:\Python27\Lib\site-packages\neoscrypt-1.0-py2.7.egg-infoI think, these are the important steps.
install_lib installs the library
Writing C:\Python27\Lib\site-packages\neoscrypt-1.0-py2.7.egg-info writes the information about the library like author, email address, license and platform.I’m at the end of my knowledge. :(
The only thing I can think of is, that the file extension of the created file is not dll.
can you do anther setup.py, but without the final ‘install’ parameter?
Then you can check the content of the build directory and see what the exact file name(s) of the creates file(s) is.
I’m working on linux and have no experience with p2pool on windows.
I found some hints with google ‘setup p2pool on windows’, but i’m not sure if that will help you, sorry -
Running just the build creates the neoscrypt.pyd file. It seems like the issue is that the python scripts run when starting the pool just don’t know where to find it.
It’s odd because I’ve run this setup guide on another windows machine and not had a single issue.
-
may be you can google, where python looks for the pyd files on windows?
-
yeah, I tried that with not much luck… the only thing I could find was a path issue, and I’ve added every directory I could think of to the path just to see if it helped. It didn’t.
-
m@j1732 said in p2pool for core 0.16 question:
yeah, I tried that with not much luck… the only thing I could find was a path issue, and I’ve added every directory I could think of to the path just to see if it helped. It didn’t.
I hope you aded the path, where the pyd file was installed. ;)
Also, did I get it right, that you got it working on another pc with the same OS?
Then as a last try you could copy the whole p2pool directory form that pc to the one with problems and see if it works, but I’m guessing now.
I have no idea anymore how to isolate and fix the problem :(
-
ha! Yeah, I added the directory for the .pyd to the path variable :D
I tried copying over the whole folder and it was no good. I’m going to try a new install on a completely different machine and see what happens… this whole thing is just weird.
-
-
any news here? did you get it working?
-
Almost. I created a linux box and got everything to run and compile right. The only issue now is when I try and use an newly generated receipt address from my wallet it won’t work. Runs fine if I use the address you show in the example at the beginning.
Any thoughts?
-
Feathercoin v0.16 generates bech32 adresses, which are not recognized by the current p2pool versions.
-
@j1732 said in p2pool for core 0.16 question:
Almost. I created a linux box and got everything to run and compile right. The only issue now is when I try and use an newly generated receipt address from my wallet it won’t work. Runs fine if I use the address you show in the example at the beginning.
Any thoughts?
So i think feathercoin core 0.16 and onwards will default to segwit / bech32 addresses.
To generate a legacy address that’s you can use the feathecoin-cli
the command would be something like
feathercoin-cli getnewaddress "AddressLabel" "address_type"so for you, you could do something like
feathercoin-cli getnewaddress "PoolWallet" "legacy"
