Build erraneously picks up 32-bit libltdl
Swiss army knife of image processing
Brought to you by:
bfriesen
Menu
▾
▴
1 Attachments
#272 Build erraneously picks up 32-bit libltdl
closed-works-for-me
None
5
2017-03-04
2014-06-25
No
When compiling on Suse (SLES 11.1) with both 32-bit and 64-bit versions of libtool installed, compilation fails.
During the configure stage, wrong lib directories are introduced to LDFLAGS when the LDFLAGS for freetype and xml2 are added.
The attached patch solves the problem for me (but might break stuff for other people).
It may be that if GraphicsMagick configure provides an option to use pkg-config files, that this problem would be avoided on a system where pkg-config is perfectly installed. Otherwise it requires temporary modification of the user executable search path (PATH) since GraphicsMagick is obtaining options from package-specific config scripts.
What does 'freetype-config --libs' report for the system which has freetype libraries in lib64? This ouput could be used directly except that since we have many libraries to link with, we don't like it that -L and -l options are mixed in the same output. If -l arguments are filtered, then the output would be useful for LDFLAGS.
This seems like a problem with the configuration information provided by FreeType, or a selection of the wrong freetype-config script, and not a problem in GraphicsMagick. The freetype-config script is supposed to produce the correct paths for the build.
What likely has bit you is that this script is found by searching PATH. I know that it is inconvenient to need to make sure that PATH is set to find the correct freetype-config script.
Do
which freetype-configto see where the version currently being used is being pulled from.