Re: script-fu prog for tutorial

[Mike Markowski]

Hi all,

One more quick note on the script-fu function that follows
a tutorial (more info at URL below).  I have been urged to
link to the file from a web page rather than just point to the
file itself.  So, please use

http://udel.edu/~mm/gimp/

to get to my rather measly gimp page...

Thanks!
Mike

How to compile python plugin?

[Mike Markowski]

Hi all,

I just compiled gimp-1.1.23 and thought I'd experiment with the 
python plugin.  I used the "--enable-python" option with configure, 
but the plugin doesn't seem to have been created.  Could someone
clue me into what more is required?  (Python 1.5.2 is in my path.)  

Thanks, 
Mike

1.1.21 libgimp/gimp.c, line 202

[Mike Markowski]

Hey all,

The source code line referenced in this email subject line
is
  gimp_signal_private (SIGHUP,  gimp_plugin_signalhandler,
SA_RESETHAND | SA_NOMASK);

In Solaris 8, while signal.h defines SA_RESETHAND there is no
sign of SA_NOMASK.

Can someone on a linux box tell me what SA_NOMASK is for so that I can
make the needed fix and get libgimp to compile?  (Is it just zero?)

Thanks!
Mike

Re: gimp/perl problem on solaris

[Mike Markowski]

On Wed, Apr 05, 2000 at 06:26:57AM +0200, Marc Lehmann [EMAIL PROTECTED] wrote:
 On Mon, Apr 03, 2000 at 02:11:41PM -0400, Mike Markowski [EMAIL PROTECTED] wrote:
  PS I notice a handfull of plugins whose makefiles aren't created properly:
  plug-ins/perl/Gimp/Makefile
  plug-ins/perl/Net/Makefile
  plug-ins/perl/UI/Makefile
  plug-ins/perl/po/Makefile
  plug-ins/perl/Makefile
 They always require hand editing to change 'cc' to 'gcc' even though
 configure picks up 'gcc' correctly.
 
 That's actually according to design. Your perl was compiled using
 "cc".

That makes sense ( I've now recompiled perl with gcc).  In that case,
there's still one glitch with the generated makefiles quoted above.  While
configure correctly picked up 'cc' as the perl compiler, it passed the
compiler flags for 'gcc' - which is what required me to track down and fix
the makefiles.  However, the best solution is for me to simply stick with
a single compiler!  So the preceding is just an FYI and can likely be
ignored.

  Anyway, don't know if this is really the right list to mention that.
 
 It is!

Ok, great.  Then I have a final configure question.  Because I'm on a
shared machine and can't install things in standard places, code is under
my home directory in a typical bin, lib, include type of tree.  While
LD_LIBRARY_PATH lets me handle where to look for libs, is there a cmd line
arg to 'configure' telling it to tack on a '-I$HOME/include' to compilation
commands?  From 'configure --help', it doesn't look like there is such an
option.

Ok.  No more config questions from me.

Thanks!
Mike