-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Aligning an already installed version of librdkafka with Alien::Librdkafka fails #17
Comments
Looks like it is compiling the toy XS okay, but failing when it tries to load it. This can happen if the .so file is not in the system search path. |
Hello Graham, thanks for looking into this. Maybe one step back. Based on the Description section of your github page, an already existing librdkafka is used by Alien::Librdkafka instead of downloading and compiling it. Based on the output above, is this the case? From this output from above, the installation via perl -MCPAN -e 'shell' seems to be looking at the right place.
And the library is there
Is there a way to manually execute the step(s) that is/are failing to dig into this further? |
You can get more detail by running prove in verbose mode:
I think thought that this is a configuration problem with the system. I understand the .so file is in On Linux and some other platforms you can use |
Hey Graham, it works... The system I am using is SLES15SP3. I reverted my VM to the original state and installed librdkafka-v1.8.0.
I then installed Alien::Librdkafka, which again failed. Then I ran
I then configured LD_LIBRARY_PATH=/usr/local/lib.
I went ahead and reran perl -MCPAN -e 'shell' with LD_LIBRARY_PATH and installed Alien::Librdkafka, which worked fine as well. My perl application then started without LD_LIBRARY_PATH being set. Thanks a lot for your help! |
Hello!
I successfully compiled the latest version (1.8.2) of librdkafka. But getting this into the perl context fails. What I did:
Would be nice if someone could comment on this...
The text was updated successfully, but these errors were encountered: