Gimp build from source libtool error makefile edit
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Gimp build from source libtool error makefile edit
Hello,
So I've been trying to get GIMP 2.7 installed on my Slackware64 13.0, but I'm having some issues. After some extensive finagling and dependence findings, I got it to configure correctly, however, the make fails with libtool trying to find libgdk_pixbuf-2.0.la:
libtool: link: cannot find the library `..//usr/lib64/pkgconfig/gdk-pixbuf/libgdk_pixbuf-2.0.la' or unhandled argument `..//usr/lib64/pkgconfig/gdk-pixbuf/libgdk_pixbuf-2.0.la'
libgdk_pixbuf-2.0.la is in /usr/lib64/pkgconfig/, but for whatever reason, editing the makefile doesn't change this. (Yes I have the right permissions to edit it). What gives? First of all, why is it searching for /usr in the top build directory, and second, why doesn't an edit of the makefile work?
Distribution: pclos2010.12, Slack1337 DebSqueeze, +50+ other Linux OS, for test only.
Posts: 9,302
Rep:
I have no solution for the expected issues,
but you may want to read this : http://www.gimp.org/release-notes/gimp-2.7.html
GIMP 2.7 Release Notes
QUOTE : " This is an unstable development version of the GNU Image
Manipulation Program. Please realize that this is just a snapshot of
the development tree. We are working hard towards GIMP 2.8, the next
stable release. GIMP 2.7 is in no way a final product. A lot of new
features are incomplete and some things may even be completely broken.
If you need to get work done, please use the stable version, GIMP 2.6."
.....
Distribution: pclos2010.12, Slack1337 DebSqueeze, +50+ other Linux OS, for test only.
Posts: 9,302
Rep:
Gimp 2.6.8 .. Slackware 13 - 64
The following is done on a clean install, no dependencies added.
First thing to do : I will check the patching for 2.6.8 :
Debian Sid : none. Fedora 14 : yes
wget http://download.fedora.redhat.com/pu...6.fc14.src.rpm
sh unPack_rpm.sh gimp-2.6.8-6.fc14.src.rpm
Code:
bash-3.1# src2pkg -e="--sysconfdir=/etc" gimp-2.6.8.tar.bz2
Found source archive: gimp-2.6.8.tar.bz2
Creating working directories:
PKG_DIR=/tmp/gimp-2.6.8-x86_64-1
SRC_DIR=/tmp/gimp-2.6.8-src-1
Unpacking source archive - Done
Correcting source permissions - Done
Checking for patches - Found
Applying: gimp-2.6.2-xdg-open.patch
Applying: gimp-2.6.6-minimize-dialogs.patch
Applying: gimp-2.6.7-jpeg-units.patch
Applying: gimp-2.6.8-4-automake.patch.bz2
Applying: gimp-2.6.8-gold.patch
Applying: gimp-2.6.8-gtk219.patch
Notice - '.am', '.ac' or '.in' config files were patched
Regenerating config files - Using: autoreconf -if Done!
Found configure script - Done
Configuring sources using:
LDFLAGS="-Wl,-L/lib64,-L/usr/lib64" CFLAGS="-O2 -fPIC -m64" ./configure --prefix=/usr --libdir=/usr/lib64
Configuration has been - Successful!
Compiling sources - Using: 'make'
Compiling has been - Successful!
Checking for Makefile rule: 'install' Okay
Creating content in JAIL root - Using: 'make install'
Compiling has been - Successful!
Checking for Makefile rule: 'install' Okay
Creating content in JAIL root - Using: 'make install'
Safe content creation - Successful!
.
.
Creating package: gimp-2.6.8-x86_64-1.tgz - Done
Package Creation - Successful! Package Location:
/tmp/gimp-2.6.8-x86_64-1.tgz
Distribution: pclos2010.12, Slack1337 DebSqueeze, +50+ other Linux OS, for test only.
Posts: 9,302
Rep:
Actually it's no wrong idea to use rpm2targz with an
SRC RPM source code package.
'rpm2targz' does the rpm unpacking, and you get a
<package>.tar.gz with the source code, the patches,
and a spec file you can check for configure options.
The advantage of the unPack_rpm.sh script :
You don't forget to create a new directory.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.