[Python-bugs-list] [ python-Bugs-467265 ] Compile errors on SuSe Linux on IBM/s390

[noreply@sourceforge.net]

Bugs item #467265, was opened at 2001-10-02 11:51
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=467265&group_id=5470

Category: Build
Group: Python 2.2
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Bernard Niset (bniset)
Assigned to: Tim Peters (tim_one)
Summary: Compile errors on SuSe Linux on IBM/s390

Initial Comment:
I requested a test account at IBM on one of their 
IBM/s390 machine. I tried to compile Python-2.2a4.tgz 
and got the following errors... I submit this as a bug 
because the version 2.1.1 compile and run fine on this 
machine.
Cheers,
Bernard Niset,
bn@smartobjects.be

gcc -c -g -O3 -Wall -Wstrict-prototypes -I. -
I./Include -DHAVE_CONFIG_H  -o Objects/fileobject.o 
Objects/fileobject.c
Objects/fileobject.c: In function `file_seek':
Objects/fileobject.c:328: warning: `offset' might be 
used uninitialized in this function
Objects/fileobject.c: In function `file_truncate':
Objects/fileobject.c:365: warning: `newsize' might be 
used uninitialized in this function


gcc -c -g -O3 -Wall -Wstrict-prototypes -I. -
I./Include -DHAVE_CONFIG_H  -o Objects/stringobject.o 
Objects/stringobject.c
Objects/stringobject.c: In function 
`PyString_FromFormatV':
Objects/stringobject.c:153: invalid initializer
make: *** [Objects/stringobject.o] Error 1


----------------------------------------------------------------------

>Comment By: Tim Peters (tim_one)
Date: 2001-10-04 14:08

Message:
Logged In: YES 
user_id=31435

Thanks for following up!  Closed.

As I mentioned, I'm not going to do anything about the 
warnings:  they don't make sense.  Can only imagine this 
compiler's flow analysis is confused by #if preprocessor 
statements.

linuxaudiodev will fail if you don't have appropriate sound-
card drivers, and I agree it's likely this box doesn't have 
any.

----------------------------------------------------------------------

Comment By: Bernard Niset (bniset)
Date: 2001-10-04 01:34

Message:
Logged In: YES 
user_id=47338

It compiles now ok... Here are the test results... I guess 
it is normal that linuxaudiodev fails on such a machine 
(Mainframe).
Cheers,
Bernard.


160 tests OK.
1 test failed:
    test_linuxaudiodev
14 tests skipped:
    test_al test_cd test_cl test_dl test_gl test_imgfile
    test_largefile test_nis test_ntpath test_socket_ssl
    test_socketserver test_sunaudiodev test_winreg 
test_winsound
Those skips are all expected on linux2.


----------------------------------------------------------------------

Comment By: Bernard Niset (bniset)
Date: 2001-10-03 00:03

Message:
Logged In: YES 
user_id=47338

OK.. I will test that tonight ...
Cheers.

----------------------------------------------------------------------

Comment By: Tim Peters (tim_one)
Date: 2001-10-02 14:35

Message:
Logged In: YES 
user_id=31435

I made some changes that may have repaired the error 
(the "invalid initializer").  Or maybe not -- I don't have 
access to a box of this kind, so I guess the only way we'll 
know is if you try again with current CVS Python.

Python/errors.c, rev 2.66
Objects/stringobject.c, rev 2.136

----------------------------------------------------------------------

Comment By: Tim Peters (tim_one)
Date: 2001-10-02 12:53

Message:
Logged In: YES 
user_id=31435

The two warnings look braindead:  offset and newsize are 
obviously initialized before use.  So not inclined to try 
to do anything about those.

The error needs more information:  an auto vrbl of type 
va_list is initialized to a vrbl of type va_list.  Why is 
that invalid?  What does va_list resolve to on this box?  
Is VA_LIST_IS_ARRAY #define'd by the config for this box?

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=467265&group_id=5470