pyroscope/rtorrent-ps

"Could not compile XMLRPC-C test" on Raspberry Pi.

meeeo opened this issue · 7 comments

meeeo commented

Hello.
I tried to install rtorrent-ps on a Raspberry Pi model B (running DietPi - a variation of Raspbian) .
I followed this installation guide.
At First I encountered the "Could not compile XMLRPC-C test" error, and I noticed that there's a section of code for to resolve that problem in build.sh but I don't know why it didn't work, and after some searchings, I tried to run that build.sh command with "--disable-instrumentation" explicitly, see the screenshot below. But still the same.
What am I supposed to do?
Thanks.

2018-06-27 11 15 53

a) I cannot solve build problems for every platform on this earth (you have to), b) I can try, but then you need to attach or 0bin the rrelevant configure.log, console logs are pretty much useless in those cases (and doubly so as pictures).

And env vars have to come before the command, not ON it. The safest way is to export them beforehand.

meeeo commented

Thank you.
I tried again to put env vars before the command.
2018-06-27 15 48 49
Still the same.
Here's the config.log.
https://drive.google.com/uc?id=1FyzqcFRMOYBx5diRSghJTb-3zt8p-j5a&export=download

That log is useless, since it is the one from the succeeding xmlrpc build. What fails is USING xmlrpc.

meeeo commented

Thank you.
Succeeding build but fails using it? But why it says that "Could not compile XMLRPC-C" error message, I was sure that's the log file generated by the interrupted building on the screenshot, but now I'm confused. Should I clean_all and do it again and collect that log.

rtorrent uses xmlrpc-c. Come to IRC if you want to continue this, it gets tedious.

meeeo commented

Thank you for you patience and sorry for my ignorance.
I just did it again and I noticed that the config.log exited with result 0 means xmlrpc build successfully.
But the building still failed.
2018-06-28 02 51 57

I'll go to IRC room later, thank you again.

Closing as dupe of #76