Line 204 of autogen.sh should look like this:
1.8*) automake_progs=automake-1.8 automake-1.9 automake-1.10
automake-1.11 ;;
Add your version of automake to the end, like this:
1.8*) automake_progs=automake-1.8 automake-1.9 automake-1.10
automake-1.11 automake-1.12 ;;
That should compile
Well, you could open up app/sanity.c and comment out the line that
says gegl:seamless-clone, to disable the check, although then you'll
have a broken seamless clone tool.
It seems like the proper fix would be to try and make the seamless
clone op work on your computer. The error happens during
OK, Thanks for the work around. As I said, I am not sure if seamless clone
is needed anyway.
As for running gimp through gdb, it's not possible not since gimp does not
even start.
Here is what I get:
gdb output
gdb ./gimp-2.9
GNU
Quick correction: put the breakpoint on g_log, not g_warning.
g_warning is actually a #define.
On Sun, Aug 4, 2013 at 12:32 PM, Michael Henning
dra...@darkrefraction.com wrote:
Well, you could open up app/sanity.c and comment out the line that
says gegl:seamless-clone, to disable the check,
Let me clarify. After you start gdb, but before starting GIMP, type:
break g_log
set logging on
run
Then, whenever gdb stops the program (may happen a few times), type:
bt full
continue
Once the dialog box appears, close it and you're done. Then, find
gdb.txt and attach it here or put it on a
On 08/04/2013 09:12 AM, Michael Henning wrote:
Line 204 of autogen.sh should look like this:
1.8*) automake_progs=automake-1.8 automake-1.9 automake-1.10
automake-1.11 ;;
Add your version of automake to the end, like this:
1.8*) automake_progs=automake-1.8 automake-1.9 automake-1.10
Michael,
Sorry to be dense. But gimp stops running after you click OK on the dialog
box and the gdb stack is empty. So, I am not sure what you are expecting in
the logfile? gdb.txt shows exactly what I posted above.
NU gdb 6.3.50-20050815 (Apple version gdb-1515) (Sat Jan 15 08:33:48 UTC
2011)
On 08/04/2013 10:41 AM, Burnie West wrote:
And I already had pygtk/2.0 installed natively.
But for some reason, even though the installation is in fact pygtk2-2.24.0, it
installs in the directory pygtk/2.0 (Fedora 18), as I had noted earlier.
I've very little experience with the configure
It should install into pygtk/2.0; that is normal. The 2.0 indicates
that it is API/ABI compatible with pygtk 2.0. As long as there are no
backwards-incompatible changes, the directory remains 2.0, even for
version 2.4.
Are you on linux? If you are, then the only things you should really
need to
On 08/04/2013 01:11 PM, Michael Henning wrote:
Are you on linux? If you are, then the only things you should really
need to build yourself are babl, gegl, and gimp. Install your distro's
packages for everything else, and you should be good to go. If you
have issues with python, then you may need
Thanks for your help, Michael. But gimp's autogen.sh fails the same
way.
checking for /usr/bin/python2 script directory...
${prefix}/lib/python2.7/site-packages
checking for /usr/bin/python2 extension module directory...
${exec_prefix}/lib64/python2.7/site-packages
checking for headers
Michael,
Additional information: After I commented out seamless clone from sanity
check, Gimp compiled and ran fine.
I tried out LightiningIsMyName's youtube video and it works on the Mac
fine without the need for this check. Of course, it's excruciatingly slow
and takes forever on my speedy Mac
On 08/04/2013 02:49 PM, Owen wrote:
This might sound stupid, but do you have pygtk, ie, what is in
${prefix}/lib/python2.7/site-packages (on my system it's called
dist-packages)
2.10.4 is pretty old so if its there, the version number probably
isn't the problem.
I have /usr/lib64/pygtk/2.0,
On 08/04/2013 03:31 PM, Burnie West wrote:
On 08/04/2013 02:49 PM, Owen wrote:
This might sound stupid, but do you have pygtk, ie, what is in
${prefix}/lib/python2.7/site-packages (on my system it's called
dist-packages)
2.10.4 is pretty old so if its there, the version number probably
isn't
On 08/04/2013 05:19 PM, Burnie West wrote:
On 08/04/2013 03:31 PM, Burnie West wrote:
So I tried links in /usr/lib/python2.7site-packages to the four pygtk.*
entries in /usr/lib64/python2.7/site-packages.
This does not work, however. Gets the same configure failure message.
For what it might
I forgot: for the instructions in my last email to work, you probably
need to compile glib with debugging symbols.
On Sun, Aug 4, 2013 at 6:05 PM, Partha Bagchi parth...@gmail.com wrote:
Michael,
Additional information: After I commented out seamless clone from sanity
check, Gimp compiled and
16 matches
Mail list logo
