Vikas wrote:

> <snipped historical stuff...>

>
> I even ran autoconf on the directory and it did generate the configure
> script but the script did not run. There were errors at startup itself.
> I do not remeber them right now.
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com

Hi,

Typically, I run

autogen.sh   --prefix=/usr/people/garry/WorkSpace/dist \
             --with-gtk-prefix=/usr/people/garry/WorkSpace/dist \
             --enable-ansi \
             --enable-debug \
             --disable-static \
             --disable-perl

autogen.sh is designed to run autoconf, automake, libtool, gettext.
then kick off configure, passing the parameter list to that script,
as noted by Marc and described in gimp/HACKING (was that available
to you to read?). None of the options I use above is mandatory; the
first two assist me in keeping a development gimp environment that
is distinct from a production gimp, the next three assist in
debugging, the last concerning a regrettable difficulty specific
to SGI/Irix (See bug report: http://bugs.gnome.org/db/193/19335),
and which is approaching resolution.

I suggest you experiment with autogen.sh, as described in gimp/HACKING.
If you care to, send me the output by private e-mail if you do not
have any success.

Be good, be well

Garry Osgood

Reply via email to