[Python-bugs-list] [ python-Bugs-438786 ] CVS 2.1.1c1 broken on osf1V4
noreply@sourceforge.net
noreply@sourceforge.net
Thu, 19 Jul 2001 12:38:24 -0700
Bugs item #438786, was opened at 2001-07-05 07:54
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=438786&group_id=5470
Category: Python Interpreter Core
Group: Platform-specific
Status: Open
Resolution: None
Priority: 5
Submitted By: Gregory H. Ball (greg_ball)
>Assigned to: Guido van Rossum (gvanrossum)
Summary: CVS 2.1.1c1 broken on osf1V4
Initial Comment:
As of right now, the CVS branch for the 2.1 bugfix
release cannot import the math module on my Digital
Unix platform.
ImportError: Unresolved symbol in
/tmp_mnt/home/gball/usr/src/python/dist/src/build/lib.osf1-V4.0-alpha-2.1/math.so:
__eprintf
uname is
OSF1 surya V4.0 878 alpha
----------------------------------------------------------------------
>Comment By: Martin v. Löwis (loewis)
Date: 2001-07-19 12:38
Message:
Logged In: YES
user_id=21627
This seems to originate fromt the fragment
OSF1) CC=cc
without_gcc=;;
which was introduced in configure.in 1.23, with the comment
on osf/1, never use gcc
Therefore, I'm assigning it to Guido. My proposal is to
close this as "won't fix" - if setting CC doesn't work,
just don't do that.
Alternatively, if nobody can remember why gcc should not
be used on OSF/1, it might be reasonable to back-out this
change.
----------------------------------------------------------------------
Comment By: Gregory H. Ball (greg_ball)
Date: 2001-07-19 12:12
Message:
Logged In: YES
user_id=11365
I just checked out the 2.1.1 branch again and
it still seems to be broken. After a fresh config with $CC
set to gcc in the environment, the Makefile contains
CC= cc
OPT= -O -Olimit 1500
CCSHARED=
so it looks like configure has decided to use cc and
chosen flags for that compiler.
Then, the actual build command lines look like
gcc -I.
-I/tmp_mnt/home/gball/usr/src/python/dist/src/./Include
-I/usr/local/include -IInclude/ -c
/tmp_mnt/home/gball/usr/src/python/dist/src/Modules/fpectlmodule.c
-o build/temp.osf1-V4.0-alpha-2.1/fpectlmodule.o
i.e. just "gcc" instead of "cc -O -Olimit 1500"
so it looks like the environment variable gets pulled in
only at the last moment and replaces $(CC), $(OPT) and
possibly $(CCSHARED), thereby throwing away the work done by
configure.
----------------------------------------------------------------------
Comment By: Thomas Wouters (twouters)
Date: 2001-07-19 02:59
Message:
Logged In: YES
user_id=34209
Gregory, did you get a chance to test the patch attached to
bug #437487, or the 2.1.1 CVS tree ? I'd like to know if
this is fixed in 2.1.1.
----------------------------------------------------------------------
Comment By: Thomas Wouters (twouters)
Date: 2001-07-16 08:56
Message:
Logged In: YES
user_id=34209
Ah, yes, that sounds very plausible. The fix for that
problem, which was checked in on the trunk, will be in
Python 2.1.1-final as well. The Solaris bugreport has a
patch attached to it; could you test it to see if it solves
your 2.1.1c1 problem ?
----------------------------------------------------------------------
Comment By: Gregory H. Ball (greg_ball)
Date: 2001-07-09 08:48
Message:
Logged In: YES
user_id=11365
The problem goes away if I clear $CC instead of having it
set to gcc. There's a similar problem on Solaris reported
recently.
I think the configure script should try to spot this sort of
thing,
but I suppose that's an Autoconf feature request, not a
python bug...
Thanks.
----------------------------------------------------------------------
Comment By: Martin v. Löwis (loewis)
Date: 2001-07-08 14:06
Message:
Logged In: YES
user_id=21627
This sounds like a bug in your compiler installation.
__eprintf is typically defined in libgcc.a; make sure you
use a consistent compiler capable of building binaries for
your system throughout the build process.
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=438786&group_id=5470