This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: --disable-sunaudiodev --disable-tk does not work
Type: Stage: resolved
Components: Build Versions: Python 2.5
Status: closed Resolution: wont fix
Dependencies: Superseder:
Assigned To: loewis Nosy List: ajaksu2, loewis, thurnerrupert
Priority: normal Keywords:

Created on 2006-10-17 15:03 by thurnerrupert, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (16)
msg30257 - (view) Author: ThurnerRupert (thurnerrupert) Date: 2006-10-17 15:03
trying to disable sunaudiodev and tk does not really 
work in solaris.

./configure --prefix=/usr/local/Python-2.5 --enable-
shared --disable-sunaudiodev --disable-tk

building 'sunaudiodev' extension
gcc -fPIC -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -
Wstrict-prototypes -I. -I/usr/local/Python-
2.5/./Include -I/cs/ecms/2.0.0/include -I./Include -
I. -I/usr/local/include -I/usr/local/Python-
2.5/Include -I/usr/local/Python-2.5 -
c /usr/local/Python-2.5/Modules/sunaudiodev.c -o 
sun/audioio.h: No such file or directory

building '_tkinter' extension
gcc -fPIC -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -
Wstrict-prototypes -DWITH_APPINIT=1 -
I/usr/openwin/include -I. -I/usr/local/Python-
2.5/./Include -I/cs/ecms/2.0.0/include -I./Include -
I. -I/usr/local/include -I/usr/local/Python-
2.5/Include -I/usr/local/Python-2.5 -
c /usr/local/Python-2.5/Modules/_tkinter.c -o 
In file included from /usr/local/Python-
/usr/local/include/tk.h:96:23: X11/Xlib.h: No such 
file or directory
In file included from /usr/local/Python-
/usr/local/include/tk.h:572: error: syntax error 
before "Window"
/usr/local/include/tk.h:572: error: `Window' declared 
as function returning a function
/usr/local/include/tk.h:575: error: syntax error 
before "XEvent"
/usr/local/include/tk.h:584: error: syntax error 
before "Tk_ClassCreateProc"
/usr/local/include/tk.h:592: error: syntax error 
before '}' token
/usr/local/include/tk.h:678: error: syntax error 
before "Bool"

is it possible to correct this or state clearly in 
the configure options how to disable it correctly?

we also checked the Modules/Setup and both seems 
msg30258 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2006-10-17 15:43
Logged In: YES 

I fail to see a bug here. What makes you think
--disable-sunaudiodev --disable-tk exist? ./configure --help
does not claim they do.

In fact, it is not possible to disable modules. Why do you
want that?
msg30259 - (view) Author: ThurnerRupert (thurnerrupert) Date: 2006-11-01 22:47
Logged In: YES 

because there is a compilation error with both. sunaudio.h seems not to exist on our 
server, and tk gives other compilation errors.

and i have no idea why i would need these modules on our server. 
msg30260 - (view) Author: ThurnerRupert (thurnerrupert) Date: 2006-11-01 22:49
Logged In: YES 

and what does that mean?

Optional Features:
  --disable-FEATURE       do not include FEATURE (same as --enable-FEATURE=no)
  --enable-FEATURE[=ARG]  include FEATURE [ARG=yes]
msg30261 - (view) Author: ThurnerRupert (thurnerrupert) Date: 2006-11-01 23:31
Logged In: YES 

and there is no X on the server.
msg30262 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2006-11-02 05:40
Logged In: YES 

Re: enable/disable: What makes you think "sunaudiodev" and
"tk" are valid values for "FEATURE"? configure --help lists
the valid values for FEATURE, namely universalsdk,
framework, shared, profiling, toolbox-glue, ipv6, and unicode.

Re: there is a compilation error. Sure, an error is
reported. However, compilation should not fail because of
that. Instead, compilation should complete successfully, and
just end up not building these modules.
msg30263 - (view) Author: ThurnerRupert (thurnerrupert) Date: 2006-11-03 11:56
Logged In: YES 

what do you suggest then to convince the build not to build it?
msg30264 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2006-11-03 23:25
Logged In: YES 

It doesn't build the modules, as it doesn't succeed when
attempting to. Why do you want it not to attempt?
msg30265 - (view) Author: ThurnerRupert (thurnerrupert) Date: 2006-11-06 09:23
Logged In: YES 

i would appreciate if the build completes without errors. i won't care if it attemts to build, but it should figure 
out that the sunaudiodev is not there. to my knowledge servers do not need that component. and python should not 
need it too then. 

do you see any reason why these components are vital for python?
msg30266 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2006-11-06 17:51
Logged In: YES 

The component isn't vital. It shouldn't be relevant for 
building sunaudiodev whether an audio device is present in
the system, as this device isn't necessary for *building*
Python. Instead, presence of /usr/include/sys/audioio.h
is necessary. I'm puzzled that this file isn't there (it
is part of the core development environment, AFAIK); the
build process assumes that the header is present if the
system name is "sunos5".
msg30267 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2006-11-19 08:15
Closing as "won't fix". There are no plans to implement  --disable-sunaudiodev --disable-tk options to configure.
msg30268 - (view) Author: ThurnerRupert (thurnerrupert) Date: 2006-11-22 11:50
may i open it again? 

there is a lot of builds on solaris without the core development environment, so assuming it is there is erronous.

e.g. we build everything with standard gnu from e.g.

msg30269 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2006-11-22 21:53
You still haven't demonstrated a problem. Compiling Python produces some error messages, sure, but does the resulting Python binary actually work or not?

If it works, what is the problem? That you appreciate not to see error messages does not make it a bug.

You cannot build Python *at all* with just the standard gnu from You do need system header files, and those are not provided by GCC. So if you have header files, where did you get them from?
msg30270 - (view) Author: ThurnerRupert (thurnerrupert) Date: 2006-11-23 08:20
which header files do you mean? the sun/audioio.h header file e.g. is not there, but standard sun header files of course are there.

it is though possible to get a running python. but i'm unsure what works and what not, so you could classify it as "cleanup" too, if you prefer.
msg30271 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2006-11-23 17:52
It's not sun/audioio.h that's missing, but (apparently) /usr/include/sys/audioio.h; this
should have come from the SUNWaudh package (Audio Header Files).

If you want to find out what works and what not, you should run the test suite.
msg84525 - (view) Author: Daniel Diniz (ajaksu2) * (Python triager) Date: 2009-03-30 07:20
Closing again, for the same reasons.
Date User Action Args
2022-04-11 14:56:20adminsetgithub: 44138
2009-03-30 07:20:21ajaksu2setstatus: open -> closed

nosy: + ajaksu2
messages: + msg84525

components: + Build, - Tkinter
stage: resolved
2006-10-17 15:03:55thurnerrupertcreate