2.1 extension errors on Solaris/gcc

[Martin von Loewis]

"Andrew Dalke" <dalke at dalkescientific.com> writes:

> Original attempt was to compile Python with gcc 2.95 using
> the archive from ftp.sunfreeware.com .  That caused a problem.
> 
>  solana> /usr/local/bin/python
>  Python 2.1.1 (#1, Aug 25 2001, 04:37:28)
>  [GCC 3.0.1] on sunos5
>  Type "copyright", "credits" or "license" for more information.
>  >>> import cStringIO
>  Traceback (most recent call last):
>    File "<stdin>", line 1, in ?
>  ImportError: ld.so.1: /usr/local/bin/python: fatal: libgcc_s.so.1:
>  open failed: No such file or directory
>  >>>
> 
> and there was no libgcc_s.so anywhere on the machine.

I very much doubt that you got gcc 2.95. libgcc_s is only introduced
by gcc 3. Is there any chance configure was picking up a gcc 3 driver
(the "gcc" binary) already?

>  gcc -shared build/temp.solaris-2.7-sun4u-2.1/dayswig_python.o \
>    build/temp.solaris-2.7-sun4u-2.1/daydepict_python.o \
>    -L/daylight/v472/lib -ldt_thor -ldt_merlin -ldt_progob -ldt_depict \
>    -ldt_monomer -ldt_datatype -ldt_finger -ldt_smarts -ldt_ipcx \
>    -ldt_smiles -lm -o build/lib.solaris-2.7-sun4u-2.1/dayswig_python.so
>  ld: warning: global symbol `_DYNAMIC' has non-global binding:
>          (file /usr/local/lib/gcc-lib/sparc-sun-\
>            solaris2.7/3.0.1/../../../libgcc_s.so value=LOCL);
>  ld: warning: global symbol `_PROCEDURE_LINKAGE_TABLE_' has non-global \
>         binding: (file /usr/local/lib/gcc-lib/sparc-sun-\
>                    solaris2.7/3.0.1/../../../libgcc_s.so value=LOCL);
>  ld: warning: global symbol `_GLOBAL_OFFSET_TABLE_' has non-global binding:
>         (file /usr/local/lib/gcc-lib/sparc-sun-\
>                  solaris2.7/3.0.1/../../../libgcc_s.so value=LOCL);
>  Bus Error (core dumped)
> 
> Now what?

Tell us what binutils are you using. What is as, what is ld? If GNU
binutils, what versions? 

You can find out what tools are used by invoking gcc with -v; make
sure you add that to a linker line.

It may be that the precompiled gcc on Sunfreeware was build for use
with GNU binutils, so you may need to install those as well.

In any case, I recommend to get a working compiler first before
starting to build Python. It may be that you have to get a really old
gcc version first, than rebuild a more recent version if the prebuilt
binaries are unusable.

Regards,
Martin