Re: [pygsl-discuss] Build problem for 0.9.0 on Debian AMD64

[<jo...@fh...>]

On 18.04.2007, at 18:12, mta...@ec... wrote:

> I have been unable to compile version 0.9.0 of the library.  My system
> details:

> numpy v1.0.1

[...]


> janus:pygsl-0.9.0/#python ./setup.py install
> Using 'Numeric' as array object

Please realize that you are building against Numeric, not numpy.
Use with
   --array-object=3Dnumpy to override.

In that case it should also work out of the box...

> tmodule.c:51:
> src/init/block_helpers.c: In function 'PyGSL_PyArray_Check':
> src/init/block_helpers.c:243: error: 'PyArray_BYTE' undeclared =20
> (first use
> in this function)
> src/init/block_helpers.c:243: error: (Each undeclared identifier is
> reported only once
> src/init/block_helpers.c:243: error: for each function it appears in.)
> src/init/block_helpers.c:243: error: 'PyArray_STRING' undeclared =20
> (first
> use in this function)
> error: command 'gcc' failed with exit status 1

Here's a patch to work around this issue:

--- src/init/block_helpers.c-orig       2007-04-17 18:32:03.000000000 =20=

+0200
+++ src/init/block_helpers.c    2007-04-17 20:27:02.000000000 +0200
@@ -240,7 +240,7 @@
       PyGSL_add_traceback(NULL, filename, __FUNCTION__, line);
       DEBUG_MESS(4, "common array types: Double %d, CDouble %d", =20
PyArray_DOUBLE, PyArray_CDOUBLE);
       DEBUG_MESS(4, "integer: Long %d, Int %d, Short %d", =20
PyArray_LONG, PyArray_INT, PyArray_SHORT);
-     DEBUG_MESS(8, "Char type %d  Byte type %d String type %d", =20
PyArray_CHAR, PyArray_BYTE, PyArray_STRING);
+     /* DEBUG_MESS(8, "Char type %d  Byte type %d String type %d", =20
PyArray_CHAR, PyArray_BYTE, PyArray_STRING); */
       return error_flag;
  }


Greetings,
Jochen
--=20
Einigkeit und Recht und Freiheit                http://www.Jochen-=20
Kuepper.de
     Libert=E9, =C9galit=E9, Fraternit=E9                GnuPG key: =
CC1B0B4D
         Sex, drugs and rock-n-roll