SEGFAULT from importing _minpack.so (was Re: [SciPy-user] install

Gerard Vermeulen gvermeul at polycnrs-gre.fr
Fri May 24 15:00:39 EDT 2002


On Friday 24 May 2002 20:20, you wrote:
> > This makes total sense, now.  I solved the problem by not compiling with
> > -fPIC while the better? solution is to link against g2c-pic.  The problem
> > comes down to the separation of the "PIC" support code in Mandrake 8.2.
> >
> > I have no idea why they did this.
>
> So, what do you suggest? As I understand, there are three options for
> Mandrake:
> 1) let their users modify python's Makefile --- a pain for some users, I
> guess;
> 2) let build_flib.py use "g2c-pic" instead of "g2c" --- works only for
> "out of box" cases and assuming that Mandrake is consistent with using
> "g2c-pic" among its all (recent and future) releases. Need a way to
> determine if linux system is from Mandrake;
> 3) do nothing  --- preferred for users who build their own compiler.
>
Well, if you opt for (2), this feature is new in Mandrake-8.2 (8.1 is OK).

A way to check the version of a Red Hat/Mandrake distribution is to use:

[packer at venus packer]$ cat /etc/mandrake-release
Mandrake Linux release 8.2 (Bluebird) for i586
[packer at venus packer]$ cat /etc/redhat-release
Mandrake Linux release 8.2 (Bluebird) for i586
[packer at venus packer]$

Other idea is to use:
[packer at venus packer]$ g77 -print-search-dirs
to get a list of directories and to look for libg2c-pic.a, mine is here:

[packer at venus packer]$ ls /usr/lib/gcc-lib/i586-mandrake-linux-gnu/2.96/
cc1*       cpp0*        crtend.o   include/      libgcc.a       specs
cc1plus*   crtbegin.o   crtendS.o  libg2c.a      libstdc++.a@   SYSCALLS.c.X
collect2*  crtbeginS.o  f771*      libg2c-pic.a  libstdc++.so@  tradcpp0*
[packer at venus packer]$

We can only hope, that if other distributions have/copy this idea, they give
this library the same name.

Gerard

PS: adding a FAQ or KNOWN-PROBLEMS is fine with me, if you opt for (3).
I can try to send a bug report to Mandrake, so that they will undo this
innovation in the future.



More information about the SciPy-User mailing list