-
Notifications
You must be signed in to change notification settings - Fork 83
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
master branch - compilation on linux is broken #41
Comments
Thanks for reporting this. |
We are currently building without issues on CentOS for our production servers with this commit in place. @nopsenica, which distro are you using? |
I have checked with ScientificLinux 6 (i.e. CentOS 6) and CentOS 7. |
"git clone" followed by build attempt, the way it is specified by .spec file, fails:
The same thing happens on EL6 and Fedora 26. Problem is removal of files in commit 8a68587. Without that commit, build on linux succeeds. |
Also, I would recommend using
|
Sorry for the confusion! Didn't realize that .spec file had outdated instructions. Let us know if that works for your system; PR #42 updates the .spec file with these instructions. |
Fix issue #41 - Update jmagick.spec to use autoreconf and automake.
Unfortunatelly, build is still broken:
|
Try |
@nopsenica, could you please post the output of On the system I'm using where it builds successfully:
I suspect the version of one or both of those autotools programs is too old. |
Oh, and please include the output of On our system:
|
Package versions are CentOS 7 defaults: autoreconf: 2.69
automake: 1.15
libtoolize: 2.4.2
|
Interesting. Apparently our build system is getting the same error and discarding it. Running ./configure afterwards should work.
and see if it successfully builds? |
Yes, when I do all the build stages manually, it builds successfully despite errors reported by autoreconf/automake. |
I'll look into that tomorrow and see if I can get a PR in that suppresses the errors. |
Sorry, I forgot everything :-) |
If it's any use, here's what I am doing to get a working build with a clean CentOS 7, latest master and IM 7.0.7
(so in my Dockerfile this is part of I ignore the errors and the exit code) configure will then look like it runs OK but if you check the output carefully I have
and so on - and the resulting build does not work To fix that I do
and get a working build - I think it might be possible to fix that in configure.ac note - I've not tried the RPM build with the spec file but can do so |
I am getting the following error while trying to compile on ubuntu:
any ideas? |
/usr/local/bin/MagickWand-config is telling the configure script to look for MagickCore-7.Q16HDRI library .so file and it cannot find it. Can you verify it exists on the linker path and has exported the ConstituteImage function? |
Yes it does exist.
|
Could you please post the contents of config.log in the build directory after the failed configure is run? |
Okay, here is the log: |
Interesting, it looks like your libMagickCore.so depends on libMagickWand! Could you try changing configure.ac line 378 from
to
and see if (after autoreconf) it works? If not please post the new config.log. Thanks! For verbosity, the specific failure is due to the below compiler output during the configure process:
|
It did not work, here is the new log: |
Actually, with It is inaccurate anyway since the .so files live in /usr/local/lib |
Thanks for the correction. But it is still failing with just |
Got a solution from the following comment: https://github.com/jcupitt/libvips/issues/418#issuecomment-207514248 after that I am getting the following error:
|
Glad you were able to find a solution to the linker error! Please revert the change I asked you to make in configure.ac and try running autoreconf --force --install
automake --add-missing
./configure |
I did run
But that was resolved by running Thanks for the help. 😃 |
Happy to hear it works. |
Commit db0e6d7 (8a68587) broke compilation on linux.
The text was updated successfully, but these errors were encountered: