[Gegl-developer] pygegl make fails

2009-02-19 Thread Scott Gorlin
Hi,

I'm trying to build the python bindings without much success. babl and
gegl are successfully installed from svn, but I get the error below when
making pygegl. I'm running Ubuntu 8.10 w/ python 2.5 on a dell latitude
d620. Any suggestions?

Thanks,
Scott


nlinfit:~/scripts svn co http://svn.gnome.org/svn/gegl/trunk/bindings/pygegl 
pygegl
Apygegl/configure.ac
Apygegl/COPYING.LESSER
Apygegl/samples
Apygegl/samples/op-reference.py
Apygegl/samples/subgraph.py
Apygegl/samples/render-test.py
Apygegl/samples/.gitignore
Apygegl/samples/xml-parsing.py
Apygegl/samples/Makefile.am
Apygegl/.gitignore
Apygegl/AUTHORS
Apygegl/acinclude.m4
Apygegl/ChangeLog
Apygegl/COPYING
Apygegl/Makefile.am
Apygegl/autogen.sh
Apygegl/NEWS
Apygegl/README
Apygegl/Gegl
Apygegl/Gegl/fifthleg.py
Apygegl/Gegl/geglrectangle.override
Apygegl/Gegl/.gitignore
Apygegl/Gegl/geglmodule.c
Apygegl/Gegl/__init__.py
Apygegl/Gegl/Makefile.am
Apygegl/Gegl/gegl.override
Apygegl/Gegl/gegl.defs
 U   pygegl
Checked out revision 2920.
nlinfit:~/scripts cd ./pygegl/
nlinfit:~/scripts/pygegl ./autogen.sh 

I am testing that you have the tools required to build the
pygegl project from SVN. This test is not foolproof,
so if anything goes wrong, see the file HACKING for more information...

checking for libtool = 1.4 ... Major version might be too new (2.2.4)
checking for autoconf = 2.54 ... yes (version 2.61)
checking for automake = 1.8.3 ... yes (version 1.10.1)

I am going to run ./configure with the following arguments:

  --enable-maintainer-mode  

If you wish to pass additional arguments, please specify them 
on the ./autogen.sh command line or set the AUTOGEN_CONFIGURE_ARGS 
environment variable.

libtoolize: putting auxiliary files in `.'.
libtoolize: linking file `./ltmain.sh'
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:74: installing `./config.guess'
configure.ac:74: installing `./config.sub'
configure.ac:31: installing `./install-sh'
configure.ac:31: installing `./missing'
Gegl/Makefile.am: installing `./depcomp'
Gegl/Makefile.am:6: installing `./py-compile'
Makefile.am: installing `./INSTALL'

Running ./configure...

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands +=... yes
checking for /usr/bin/ld option to reload object files... -r
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked 

Re: [Gegl-developer] pygegl make fails

2009-02-19 Thread Hubert Figuiere
On 02/19/2009 11:03 AM, Scott Gorlin wrote:
 I'm trying to build the python bindings without much success. babl and
 gegl are successfully installed from svn, but I get the error below when
 making pygegl. I'm running Ubuntu 8.10 w/ python 2.5 on a dell latitude
 d620. Any suggestions?


Are you sure the python bindings are up to date with the API changes in 
trunk?


Hub
___
Gegl-developer mailing list
Gegl-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gegl-developer


[Gegl-developer] Documenting gegl

2009-02-19 Thread Henrik Akesson
Hi all,

I'm learning gegl internals for doing some work on parallelizing it (I've
posted before on that subject). When I do it I normally write some
documentation of my own (when it's missing), such as:

http://computerresearcher.blogspot.com/search/label/Gegl

Note that it's fragmented and still under construction.

Instead of writing it on my blog I could contribute it.

1. Are you interested in that?

If yes:

2. What is the appropriate format. Asciidoc? Note that there are/will be
images, documentation for specific c files and general documentation.

3. It would need to be reviewed. I'm after all learning this stuff... How
can it be done practically. I suppose that a separate svn branch for me with
someone of you merging could be a solution.

/Henrik
___
Gegl-developer mailing list
Gegl-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gegl-developer


[Gegl-developer] Documenting gegl

2009-02-19 Thread Nicolas Robidoux

Hello Henrik:

I don't know if this was mentioned before, but the open source VIPS

http://www.vips.ecs.soton.ac.uk/index.php?title=VIPS

although quite different to GEGL, is also somewhat similar.

VIPS handles CMPs well.

Maybe some of VIPS' under the hood parallel machinery would carry
over?

Nicolas Robidoux
Laurentian University/Universite Laurentienne
___
Gegl-developer mailing list
Gegl-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gegl-developer