Re: [Gimp-developer] What is the status of the 16-bit GIMP ?

2002-01-19 Thread Marcin Skubiszewski

On Fri, Jan 18, 2002 at 10:31:21AM -0800, Jonathan Cohen wrote:

[...]

 There are a couple of extra steps because of the weirdness, but it can be
 built:
 
 aclocal;
 automake -a;
 autoconf;
 ./configure --disable-shared --disable-debug --bindir=blah
 --datadir=blah --prefix=directory above include directory
 --exec-prefix=directory above bin which contains gnu tools;
 ltconfig --disable-shared ltmain.sh; # have to do this separately for some
 reason
 gmake all;


Sorry, this does not work for me. Could you please help me further ?

When I do what you say, ./configure exits prematurely (it exits when
it tries to execute ltconfig). As a result, the Makefiles are not built.

When I comment out the invocation of ltconfig in ./configure, ./configure executes 
completely and I do get
makefiles, but then one of them, namely

gimp/plug-ins/rll/Makefile

has wrong content: it does not specify the compiler to use.

I tried to go further (suppress the compilation of plugins), but all I
get is more and more errors.

Here is a detailed log of how I try to follow your instructions:


FIRST ATTEMPT:


bash-2.04$ cvs -d :pserver:[EMAIL PROTECTED]:/cvs/gnome checkout -r HO 
LLYWOOD gimp
[here comes a long list of checked-out files] 
bash-2.04$ aclocal
bash-2.04$ automake -a
bash-2.04$ autoconf
configure.in:31: warning: AC_CANONICAL_HOST invoked multiple times
bash-2.04$ ./configure --disable-shared --disable-debug --bindir=/l/src/gimp16d /bin 
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for ranlib... ranlib
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix... 
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
ltconfig: you must specify a host type if you use `--no-verify'
Try `ltconfig --help' for more information.
configure: error: libtool configure failed
bash-2.04$ ./ltconfig --disable-shared ltmain.sh
checking host system type... i686-pc-linux-gnu
checking for ranlib... ranlib
checking for gcc... gcc
checking whether we are using GNU C... yes
checking for object suffix... o
checking for executable suffix... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.lo... yes
checking if gcc supports -fno-rtti -fno-exceptions ... yes
checking if gcc static flag -static works... -static
checking whether ln -s works... yes
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the linker (/usr/bin/ld) supports shared libraries... yes
checking for BSD-compatible nm... /usr/bin/nm -B
checking command to parse /usr/bin/nm -B output... ok
checking how to hardcode library paths into programs... immediate
checking for /usr/bin/ld option to reload object files... -r
checking dynamic linker characteristics... Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking for objdir... .libs
creating libtool
bash-2.04$ make all
make: *** No rule to make target `all'.  Stop.


SECOND ATTEMPT:

Now I edit the call to ltconfig out of ./configure, then I do the following:

bash-2.04$ ./configure --disable-shared --disable-debug --bindir=/l/src/gimp16d /bin 
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for ranlib... ranlib
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix... 
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking 

[Gimp-developer] What is the status of the 16-bit GIMP ?

2002-01-18 Thread Marcin Skubiszewski

Last time I checked, I was unable to autoconf;./configure the version
in the CVS.

Thank you in advance.

Marcin.
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer



Re: [Gimp-developer] What is the status of the 16-bit GIMP ?

2002-01-18 Thread Sven Neumann

Hi,

Marcin Skubiszewski [EMAIL PROTECTED] writes:

 Last time I checked, I was unable to autoconf;./configure the version
 in the CVS.

as fas as I know the Hollywood GIMP branch is unmaintained. Our plan
is to add 16bit depth per color channel and other colorspaces with
GIMP-2.0. Development on this stuff takes place in the GEGL module
while GIMP itself is still on the road to GIMP-1.4. This is explained
more detailed in http://developer.gimp.org/gimp-future.


Salut, Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer



Re: [Gimp-developer] What is the status of the 16-bit GIMP ?

2002-01-18 Thread Jonathan Cohen

Not true.  I'm a software developer at Rhythm and Hues.  We're 
actively maintaining and developing the 16bit GIMP for use in our
studio.  There is something a little funky with the autoconf/automake
setup that we never fully debugged, and the code is a little unstable
right now.

There are a couple of extra steps because of the weirdness, but it can be
built:

aclocal;
automake -a;
autoconf;
./configure --disable-shared --disable-debug --bindir=blah
--datadir=blah --prefix=directory above include directory
--exec-prefix=directory above bin which contains gnu tools;
ltconfig --disable-shared ltmain.sh; # have to do this separately for some
reason
gmake all;

New features include things like improved UI, frame manager for editing
and painting on multiple frames from an animation clip, and save/restore
layout.

-Jon

On 18 Jan 2002, Sven Neumann wrote:

 Hi,
 
 Marcin Skubiszewski [EMAIL PROTECTED] writes:
 
  Last time I checked, I was unable to autoconf;./configure the version
  in the CVS.
 
 as fas as I know the Hollywood GIMP branch is unmaintained. Our plan
 is to add 16bit depth per color channel and other colorspaces with
 GIMP-2.0. Development on this stuff takes place in the GEGL module
 while GIMP itself is still on the road to GIMP-1.4. This is explained
 more detailed in http://developer.gimp.org/gimp-future.
 
 
 Salut, Sven
 ___
 Gimp-developer mailing list
 [EMAIL PROTECTED]
 http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
 

___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer