Ted Gould wrote: I agree.. I (or someone who knows better how to do this) need to write a couple of little tests in comfigure.ac to actually check if the libs and includes are available. Just wanting them is not enough. ;-)

Probably a quick compile of a C call to get their version info.

Bob

Whoa, whoa, whoa.

The reason that it is failing on the GIMP gradient here is because he doesn't have the Perl libraries, and the GIMP gradient is the first object to link in with external libraries.

I found that I got build errors for both missing the Perl and Python development packages -- I think that the configure script needs to detect these omissions earlier.

--Ted

On Tue, 2004-12-21 at 13:50 -0800, Bryce Harrington wrote:

...

No, it's not perl but that dang gimpgrad thingee again, that everyone has trouble with...

There's been some discussion about 'gimpgrad' problems since the release. Maybe Ted can give some more advice.

Perhaps since there have been so many problems, we should pull the gimpgrad code out and into the experimental module, and just provide it as an optional patch, until the issues with the dynamic linking of extensions can get sorted out better?

Bryce

On Tue, 21 Dec 2004, Ben Crowell wrote:

...

Thanks, Bob, for the hint about --with-python=no. I'm now experiencing a different error, shown below, which seems to be related to Perl. I'm trying now with both python and perl disabled. I actually have a modicum of Perl expertise, so if you can tell me what it is about my Perl install that's causing this failure, I might be able to add something to the configure script to autodetect it and give an informative error message.

==============================================================

/bin/sh ../libtool --mode=link g++ -Wall -W -Wpointer-arith -Wcast-align -WsignWswitch -Wno-unused-parameter -g -O2 -o extension/plugin/libgimpgrad.la -rpatns extension/plugin/gimpgrad.lo -lgc -lpthread -ldl -Wl,-E -L/usr/local/lib /r/DynaLoader.a -L/usr/lib/perl/5.8/CORE -lperl -ldl -lm -lpthread -lc -lcrypt

*** Warning: Linking the shared library extension/plugin/libgimpgrad.la against *** static library /usr/lib/perl/5.8/auto/DynaLoader/DynaLoader.a is not portabl g++ -shared -nostdlib /usr/lib/gcc-lib/i486-linux/3.3.4/../../../crti.o /usr/libginS.o extension/plugin/.libs/gimpgrad.o /usr/lib/libgc.so -L/usr/local/lib /u/DynaLoader.a -L/usr/lib/perl/5.8/CORE -lperl -ldl -lpthread -lcrypt -L/usr/lib//lib/gcc-lib/i486-linux/3.3.4/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc-libr/lib/gcc-lib/i486-linux/3.3.4/../../../crtn.o -Wl,-E -Wl,-soname -Wl,libgimpgrbs/libgimpgrad.so.0.0.0 /usr/bin/ld: cannot find -lperl collect2: ld returned 1 exit status make[2]: *** [extension/plugin/libgimpgrad.la] Error 1 make[2]: Leaving directory `/home/bcrowell/Documents/sw/inkscape/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/bcrowell/Documents/sw/inkscape' make: *** [all] Error 2

---

SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

---

SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Bless you!

This is wonderful.

Kees Cook wrote:

On Tue, Dec 21, 2004 at 08:28:59PM -0600, Bob Jamison wrote:

...

I agree.. I (or someone who knows better how to do this) need to write a couple of little tests in comfigure.ac to actually check if the libs and includes are available. Just wanting them is not enough. ;-)

I've committed a change for this. Someone who knows the required versions should probably improve it further. I have it just checking for success/failure of the library checking routines.

On Wed, Dec 22, 2004 at 07:26:39AM -0800, Kees Cook wrote:

Thanks, but I think something may still be a bit busted. I installed the python-dev stuff this morning, and now it doesn't compile. ;) So... my change works for those _without_ python.

Okay! I got it all sane for me now. It's terrific! I loaded the Scripts dialog and selected "Execute Python", poof, About box.

This is cool stuff! :)