extra text for gtk-config not found
heya, i know this is kind of a pedantic bitch, but i run into it every time i install a new system w/red hat and then install gimp from source. after building and installing a new gtk, unless you specify usr/lib as your install path, you will have to add /usr/local/bin to /etc/ld.so.config and run ldconfig or configure will fail. i've done it half dozen or more times, and it still give me pause - and i remember what a PITA it was before i figured out what was going on. will someone add possibly a check or some extra text to that end in ./configure, so that the people upgrading to 2.0 on existing RH systems won't be so in the dark? thanks, -- Blue Lang Unix Systems Admin QSP, Inc., 3200 Atlantic Ave, Ste 100, Raleigh, NC, 27604 Home: 919 835 1540 Work: 919 875 6994 Fax: 919 872 4015
Re: Why host plug-ins at SourceForge? (Was: I want to develop IPTC-data support for The Gimp.)
On 26 Feb, Kelly Lynn Martin wrote: > It will also force us to develop tools for the separate compilation of > plugins and develop a plugin interface that is versionable The first one is definitely a need but "a plugin interface that is versionable"? We do have versioned libraries ensuring that plugins always use the right libgimp version and a wireprotocol which checks whether a plugin is using the same protocol version as the GIMP. -- Servus, Daniel
Re: Crash in Gimp 1.1.7 on Solaris 8.
[EMAIL PROTECTED] wrote:
> On 23 Feb, Ludovic Poitou wrote:
>
> > SunOS bondi 5.8 Generic sun4u sparc SUNW,Ultra-5_10
> > UltraSPARC-IIi
>
> > But I haven't compiled with the 64 bit flag on !
>
> > A simple program like this :
> > main(){
> > printf("%d\n", sizeof(unsigned char *));
> > }
>
> Do the plugins work for you? We've got dozens of problems with
> GIMP on 64bit architectures not using gcc for compilation.
>
I tried several plugins and they all work.
Ludovic.
>
> --
>
> Servus,
>Daniel
--
Ludovic Poitou
Sun Microsystems Inc.
iPlanet E-Commerce Solutions - Directory Group - Grenoble - France
