Mailman 3 September 2004 - Distutils-SIG

Re: report
by nobody＠xara.com 27 Sep '04

27 Sep '04

This is an automated response to your email sent to Xara Technical Support (support(a)xara.com) which explains the various help resources available from Xara. *** Please note that your original email will not be read. *** In order to offer a more efficient and timely level of technical support, 24 hours a day, 7 days a week we offer a range of online support services. A list of Frequently Asked Questions and answers can be found on our website at http://www.xara.com/support/. We aim to add to the site over time so that it is always as up to date as possible. Helpful advice by experienced users is also available in the TalkGraphics Xara forums (http://www.talkgraphics.com) and The XaraXone (http://www.xaraxone.com) website. These facilities are designed to enhance our existing email based support system, not to replace it. If you cannot find an answer to your question, the FAQ pages offer an e-mail link with which you can contact a member of the technical support staff. The FAQs answer all the common product, purchasing and account related questions and we urge you to check the FAQs first before contacting us directly, so that our experienced tech support staff can concentrate on giving a fast and effective service to those customers who require their help most. The following are the top three commonly asked questions: Q.: I receive The message 'Invalid serial number, your program has not been unlocked' when entering my serial number A.: The following information applies to customers that have purchased Xara 3D 5 between August 2002 and 31st September 2003 and are installing Xara 3D 5 from their CD. 1. Please install Xara 3D 5 from your CD and ensure it is not running. 2. Download and execute Xara3dPatch.exe from http://downloads.xara.com/downloads/software/xara3dpatch.exe 3. Run Xara 3d 5 and enter the serial number as displayed upon your CD. This will resolve the unlocking difficulties you have encountered. If problems persist, please run Xara 3D 5 and attempt to enter your serial number causing the error to be displayed prior to following the steps above. Q.: 'My unlock-code does not work' or 'I need a new unlock-code for my Xara product'. A.: Click on the link 'Enter your unlock code' on the startup panel of Webstyle 2.1/3.0/3.1 or Xara3D 4/5 or Menu Maker and follow the instructions. In the case of Xara X or older versions of Xara3D or Webstyle click on 'Purchase', then follow the instructions. You will need your XaraClub user name and password. We have a password reminder hint page here: https://secure.commerce.xara.com/registration/passwordhint.asp Q.: My Xara product does not work properly on Windows NT4, 2000 or XP A.: You must install and unlock your Xara product whilst logged on to the computers 'Administrator' account. Q.: How do I insert a Navigation Bar (NavBar) created in Webstyle within my webpage designs? A.: Please refer to the Help file: Help - Index - Navbars - using on a webpage

1 0

Pyrex/Distutils Compile - Missing Symbols in Python
by Adam McCarthy 25 Sep '04

25 Sep '04

I'm trying to get a cross compiler working for arm-wince-pe. This is the output for the primes Pyrex example. If I compile simple Hello, World's etc, it works fine, but for some reason Python libraries/headers seem to produce this. I have libpython2.3.a in /usr/local/lib/gcc-lib/arm-wince-pe/3.3.3/../../../../arm-wince-pe/lib/ and /usr/lib/python2.3/config. I've checked it using arm-wince-pe-objdump. I also extracted it with arm-wince-pe-ar and it contains the symbols. Below the following output, I've also pasted a debug output from the linker. Any ideas? $ python setup.py build_ext --inplace -c cygwin running build_ext building 'Primes' extension creating build creating build/temp.cygwin-1.5.11-i686-2.3 arm-wince-pe-gcc -O -Wall -I/usr/include/python2.3 -c primes.c -o build/temp.cyg win-1.5.11-i686-2.3/primes.o primes.c: In function `__pyx_f_6primes_primes': primes.c:137: warning: label `__pyx_L4' defined but not used primes.c:108: warning: label `__pyx_L6' defined but not used primes.c:98: warning: label `__pyx_L5' defined but not used primes.c:89: warning: label `__pyx_L3' defined but not used primes.c: At top level: primes.c:12: warning: `__Pyx_UnpackItem' declared `static' but never defined primes.c:13: warning: `__Pyx_EndUnpack' declared `static' but never defined primes.c:14: warning: `__Pyx_PrintItem' declared `static' but never defined primes.c:15: warning: `__Pyx_PrintNewline' declared `static' but never defined primes.c:16: warning: `__Pyx_Raise' declared `static' but never defined primes.c:17: warning: `__Pyx_ReRaise' declared `static' but never defined primes.c:18: warning: `__Pyx_Import' declared `static' but never defined primes.c:19: warning: `__Pyx_GetExcValue' declared `static' but never defined primes.c:20: warning: `__Pyx_ArgTypeTest' declared `static' but never defined primes.c:21: warning: `__Pyx_TypeTest' declared `static' but never defined primes.c:22: warning: `__Pyx_GetStarArgs' declared `static' but never defined primes.c:23: warning: `__Pyx_WriteUnraisable' declared `static' but never define d primes.c:25: warning: `__Pyx_ImportType' declared `static' but never defined primes.c:26: warning: `__Pyx_SetVtable' declared `static' but never defined primes.c:27: warning: `__Pyx_GetVtable' declared `static' but never defined primes.c:28: warning: `__Pyx_CreateClass' declared `static' but never defined primes.c:30: warning: `__Pyx_InitStrings' declared `static' but never defined primes.c:31: warning: `__Pyx_GetName' declared `static' but never defined writing build/temp.cygwin-1.5.11-i686-2.3/Primes.def arm-wince-pe-gcc -mdll -static -s build/temp.cygwin-1.5.11-i686-2.3/primes.o bui ld/temp.cygwin-1.5.11-i686-2.3/Primes.def -L/usr/lib/python2.3/config -lpython2. 3 -o Primes.dll Cannot export initPrimes (initPrimes): symbol not found build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x30):primes.c: undefined refer ence to `PyArg_ParseTupleAndKeywords' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x54):primes.c: undefined refer ence to `PyList_New' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x130):primes.c: undefined refe rence to `PyObject_GetAttr' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x144):primes.c: undefined refe rence to `PyInt_FromLong' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x158):primes.c: undefined refe rence to `PyTuple_New' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x174):primes.c: undefined refe rence to `PyObject_CallObject' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x2d0):primes.c: undefined refe rence to `_Py_NoneStruct' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x308):primes.c: undefined refe rence to `Py_InitModule4' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x320):primes.c: undefined refe rence to `PyImport_AddModule' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x348):primes.c: undefined refe rence to `PyObject_SetAttrString' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x3d4):primes.c: undefined refe rence to `PyString_InternFromString' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x430):primes.c: undefined refe rence to `PyString_FromString' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x444):primes.c: undefined refe rence to `PyString_FromString' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x45c):primes.c: undefined refe rence to `PyModule_GetDict' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x470):primes.c: undefined refe rence to `PyTuple_New' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x484):primes.c: undefined refe rence to `PyString_FromString' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x4d0):primes.c: undefined refe rence to `PyCode_New' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x4e0):primes.c: undefined refe rence to `PyThreadState_Get' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x4f0):primes.c: undefined refe rence to `PyFrame_New' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x508):primes.c: undefined refe rence to `PyTraceBack_Here' /usr/local/lib/gcc-lib/arm-wince-pe/3.3.3/../../../../arm-wince-pe/lib/crt0.o(.t ext+0x6c): undefined reference to `WinMain' collect2: ld returned 1 exit status error: command 'arm-wince-pe-gcc' failed with exit status 1 ================================================================================ $ arm-wince-pe-gcc -mdll -static -s build/temp.cygwin-1.5.11-i686-2.3/primes.o build/temp.cygwin-1.5.11-i686-2.3/Primes.def -L/usr/lib/python2.3/config -lpythe on2.3 -o Primes.dll -v -Wl,-debug Reading specs from /usr/local/lib/gcc-lib/arm-wince-pe/3.3.3/specsundefined refe Configured with: ./configure --enable-languages=c,c++ --target=arm-wince-pe : (r econfigured) ./configure --target=arm-wince-pe --host=arm-wince-pe --enable-lang uages=c,c++ --enable-multilib=no : (reconfigured) ./configure --target=arm-wince -pe --host=arm-wince-pe --enable-languages=c,c++ --enable-multilib=no : (reconfi gured) ./configure --target=arm-pe --enable-languages=c,c++ --enable-multilib=no --with-newlib : (reconfigured) ./configure --target=arm-pe --enable-languages=c ,c++ --enable-multilib=no --with-newlib : (reconfigured) ./configure --target=ar m-pe --enable-languages=c,c++ --enable-multilib=no --with-newlib : (reconfigured ) ./configure --target=arm-wince-pe --enable-languages=c,c++ --enable-multilib=n o --with-newlib : (reconfigured) ./configure --target=arm-wince-pe --enable-lang uages=c,c++ --enable-multilib=no --with-newlib Thread model: single2.1 gcc version 3.3.3rned 1 exit status /usr/local/lib/gcc-lib/arm-wince-pe/3.3.3/collect2.exe -X -o Primes.dll -s /usr /local/lib/gcc-lib/arm-wince-pe/3.3.3/../../../../arm-wince-pe/lib/crt0.o -L/usr /lib/python2.3/config -L/usr/local/lib/gcc-lib/arm-wince-pe/3.3.3 -L/usr/local/l ib/gcc-lib/arm-wince-pe/3.3.3/../../../../arm-wince-pe/lib build/temp.cygwin-1.5 .11-i686-2.3/primes.o build/temp.cygwin-1.5.11-i686-2.3/Primes.def -lpython2.3 - debug -lcdll -lcdllimp -lcoredll Convert string '/usr/local/lib/gcc-lib/arm-wince-pe/3.3.3/:/usr/local/lib/gcc-li b/arm-wince-pe/3.3.3/:/usr/local/lib/gcc-lib/arm-wince-pe/:/usr/lib/gcc/arm-winc e-pe/3.3.3/:/usr/lib/gcc/arm-wince-pe/:/usr/local/lib/gcc-lib/arm-wince-pe/3.3.3 /../../../../arm-wince-pe/bin/arm-wince-pe/3.3.3/:/usr/local/lib/gcc-lib/arm-win ce-pe/3.3.3/../../../../arm-wince-pe/bin/' into prefixes, separator = ':' - add prefix: /usr/local/lib/gcc-lib/arm-wince-pe/3.3.3/ - add prefix: /usr/local/lib/gcc-lib/arm-wince-pe/3.3.3/ - add prefix: /usr/local/lib/gcc-lib/arm-wince-pe/ - add prefix: /usr/lib/gcc/arm-wince-pe/3.3.3/ - add prefix: /usr/lib/gcc/arm-wince-pe/ - add prefix: /usr/local/lib/gcc-lib/arm-wince-pe/3.3.3/../../../../arm-wince- pe/bin/arm-wince-pe/3.3.3/ - add prefix: /usr/local/lib/gcc-lib/arm-wince-pe/3.3.3/../../../../arm-wince- pe/bin/ Convert string '/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/cygdrive/c/WINDOWS/ system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/Progr am Files/ATI Technologies/ATI Control Panel' into prefixes, separator = ':' - add prefix: /usr/local/bin/ - add prefix: /usr/bin/ - add prefix: /bin/ - add prefix: /usr/X11R6/bin/ - add prefix: /cygdrive/c/WINDOWS/system32/ - add prefix: /cygdrive/c/WINDOWS/ - add prefix: /cygdrive/c/WINDOWS/System32/Wbem/ - add prefix: /cygdrive/c/Program Files/ATI Technologies/ATI Control Panel/ Looking for 'real-ld' Looking for 'collect-ld' Looking for 'ld' Looking for 'gnm' Looking for 'arm-wince-pe-gnm' Looking for 'nm' Looking for 'gstrip' Looking for 'arm-wince-pe-gstrip' Looking for 'strip' Looking for 'arm-wince-pe-gcc' Looking for 'arm-wince-pe-gcc' collect2 version 3.3.3 (ARM/pe) ld_file_name = /usr/local/lib/gcc-lib/arm-wince-pe/3.3.3/../../../../arm- wince-pe/bin/ld c_file_name = /usr/local/bin/arm-wince-pe-gcc nm_file_name = /usr/local/lib/gcc-lib/arm-wince-pe/3.3.3/../../../../arm- wince-pe/bin/nm strip_file_name = /usr/local/lib/gcc-lib/arm-wince-pe/3.3.3/../../../../arm- wince-pe/bin/strip c_file = /cygdrive/c/DOCUME~1/adam/LOCALS~1/Temp/ccAiL4ml.c o_file = /cygdrive/c/DOCUME~1/adam/LOCALS~1/Temp/cc0qmZzw.o COLLECT_GCC_OPTIONS = '-mdll' '-static' '-s' '-L/usr/lib/python2.3/config' '-o' 'Primes.dll' '-v' COLLECT_GCC = arm-wince-pe-gcc COMPILER_PATH = /usr/local/lib/gcc-lib/arm-wince-pe/3.3.3/:/usr/local/lib/ gcc-lib/arm-wince-pe/3.3.3/:/usr/local/lib/gcc-lib/arm-wince-pe/:/usr/lib/gcc/ar m-wince-pe/3.3.3/:/usr/lib/gcc/arm-wince-pe/:/usr/local/lib/gcc-lib/arm-wince-pe /3.3.3/../../../../arm-wince-pe/bin/arm-wince-pe/3.3.3/:/usr/local/lib/gcc-lib/a rm-wince-pe/3.3.3/../../../../arm-wince-pe/bin/ LIBRARY_PATH = /usr/local/lib/gcc-lib/arm-wince-pe/3.3.3/:/usr/lib/gcc/ar m-wince-pe/3.3.3/:/usr/local/lib/gcc-lib/arm-wince-pe/3.3.3/../../../../arm-winc e-pe/lib/arm-wince-pe/3.3.3/:/usr/local/lib/gcc-lib/arm-wince-pe/3.3.3/../../../ ../arm-wince-pe/lib/ /usr/local/lib/gcc-lib/arm-wince-pe/3.3.3/../../../../arm-wince-pe/bin/ld -X -o Primes.dll -s /usr/local/lib/gcc-lib/arm-wince-pe/3.3.3/../../../../arm-wince-pe /lib/crt0.o -L/usr/lib/python2.3/config -L/usr/local/lib/gcc-lib/arm-wince-pe/3. 3.3 -L/usr/local/lib/gcc-lib/arm-wince-pe/3.3.3/../../../../arm-wince-pe/lib bui ld/temp.cygwin-1.5.11-i686-2.3/primes.o build/temp.cygwin-1.5.11-i686-2.3/Primes .def -lpython2.3 -lcdll -lcdllimp -lcoredll Cannot export initPrimes (initPrimes): symbol not found build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x30):primes.c: undefined refer ence to `PyArg_ParseTupleAndKeywords' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x54):primes.c: undefined refer ence to `PyList_New' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x130):primes.c: undefined refe rence to `PyObject_GetAttr' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x144):primes.c: undefined refe rence to `PyInt_FromLong' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x158):primes.c: undefined refe rence to `PyTuple_New' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x174):primes.c: undefined refe rence to `PyObject_CallObject' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x2d0):primes.c: undefined refe rence to `_Py_NoneStruct' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x308):primes.c: undefined refe rence to `Py_InitModule4' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x320):primes.c: undefined refe rence to `PyImport_AddModule' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x348):primes.c: undefined refe rence to `PyObject_SetAttrString' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x3d4):primes.c: undefined refe rence to `PyString_InternFromString' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x430):primes.c: undefined refe rence to `PyString_FromString' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x444):primes.c: undefined refe rence to `PyString_FromString' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x45c):primes.c: undefined refe rence to `PyModule_GetDict' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x470):primes.c: undefined refe rence to `PyTuple_New' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x484):primes.c: undefined refe rence to `PyString_FromString' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x4d0):primes.c: undefined refe rence to `PyCode_New' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x4e0):primes.c: undefined refe rence to `PyThreadState_Get' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x4f0):primes.c: undefined refe rence to `PyFrame_New' build/temp.cygwin-1.5.11-i686-2.3/primes.o(.text+0x508):primes.c: undefined refe rence to `PyTraceBack_Here' /usr/local/lib/gcc-lib/arm-wince-pe/3.3.3/../../../../arm-wince-pe/lib/crt0.o(.t ext+0x6c): undefined reference to `WinMain' collect2: ld returned 1 exit status [Leaving /cygdrive/c/DOCUME~1/adam/LOCALS~1/Temp/ccAiL4ml.c] [Leaving /cygdrive/c/DOCUME~1/adam/LOCALS~1/Temp/cc0qmZzw.o] [Leaving /cygdrive/c/DOCUME~1/adam/LOCALS~1/Temp/ccqzXTMH.ld] [Leaving Primes.dll]

1 0

Query distutils for directory names
by Bill Spotz 23 Sep '04

23 Sep '04

Is there a way to query distutils to give me the name of the lib and/or temp directories (i.e., on my machine, build/lib.darwin-7.5.0-PowerMacintosh-2.3 and build/temp.darwin-7.5.0-PowerMacintosh-2.3) that distutils creates during its build process? I can't find anything in the documentation. This would be useful for telling test scripts where to find the local versions of the module(s), as well as for linking to SWIG runtime libraries that I would like to have distutils compile. I wrote some usable python code that manually concatenates the pieces together, put I do not trust its portability. Thanks ** Bill Spotz ** ** Sandia National Laboratories Voice: (505)845-0170 ** ** P.O. Box 5800 Fax: (505)284-5451 ** ** Albuquerque, NM 87185-0316 Email: wfspotz(a)sandia.gov **

2 1

Variations in packaging
by Paul Lambert 21 Sep '04

21 Sep '04

Hello, I'm trying to build three different distributions from the same set of packages, with slight variations in the modules that are included. What's the best way to accomplish these 'setup' variations? Currently, since the setup.py needs to be in the root directory, I've simply created three different setup's (with different names). This is problomatic given that they all share the same MANIFEST and MANIFEST.in file. So, now I'm resorting to dynamically creating a MANIFEST.in ... It seems like there should be an easier way... Thanks in advance for your help, Paul

1 0

Packaging with bdist_wininst on Python 2.3, installing on Python 2.4
by David Handy 16 Sep '04

16 Sep '04

Packaging with bdist_wininst on Python 2.3, installing on Python 2.4 I decided to try installing a distutils package produced by bdist_wininst on Python 2.3 on an alpha release of Python 2.4 (2.4a1). It's a pure python package, designed for Python 2.3 and greater, so it should just work, right? The good news is that the package .py files and data files got copied to the right places. The bad news is that the bdist_wininst message gave me an ugly error message: *** Could not load Python *** It did not run my post-install script, even though it said "Postinstall script finished". (Also it did not compile .py files to .pyc) Furthermore, it created an entry for my package in the "Add or Remove Programs" control panel applet, but when I went to actually uninstall the package, the package Remove*.exe program crashed. So I can't uninstall it and I can't remove it from the list of installed programs (except by hacking the registry.) Is this all "expected behavior"? Am I hosed? Do I have to produce separate bdist_wininst packages for Python 2.3 and Python 2.4, and then try to document for my poor naive users (who are just learning computer programming) which one to download and when? What should I expect to happen if I produce a bdinst_wininst package with Python 2.4 and then install it in Python 2.3? Help! David H.

1 0

limiting symbols in C module
by Brandon Craig Rhodes 10 Sep '04

10 Sep '04

Python modules are often written as single .c files (sometimes quite large) so that everything can be declared "static" except for the init<module>() function; and though the Extending and Embedding document is unfortunately rather quiet on the many issues that arise during linking, the suggestion seems to be that minimizing the number of symbols exported by the module is good. As I update a Python module that provides an interface to an extensive collection of existing C functions, I note that the process of linking my module .o with all of the .o files produced by compiling the other code produces a Python module with a huge number of symbols. 1) Is this bad and should be avoided? I note that running strip(1) with the "-K" option allows me to strip all defined symbols from the module except for the one init<module> symbol that I want to keep. 2) Do the distutils know how to perform this operation? This would even allow normal Python modules - that have all original code rather than being linked with existing .o files - to be written as several manageable .c files rather than one huge one. 3) Can the distutils be induced to perform such a strip even if they do not quite know how themselves, or is the whole issue going to be different enough on, say, Windows, that it cannot be handled portably with the distutils in their current form? Is there a portable way to put the strip command within a stanza that will only run on appropriately Unixish systems? -- Brandon Craig Rhodes brandon(a)rhodesmill.org http://rhodesmill.org/brandon

4 4

Feedback on a couple of patches for bdist_rpm.
by Sean Reifschneider 06 Sep '04

06 Sep '04

I've just been assigned a couple of patches related to bdist_rpm. They are from Anthony Tuininga (atuining), and I'd like to get feedback from the Distutils SIG on them. The first is: Summary: topdir calculated incorrectly in bdist_rpm URL: https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1022003&group_… The _topdir directive to the bdist_rpm command is calculated incorrectly when the --bdist-base or --dist-dir options to the command use absolute path names. It should use os.path.abspath() instead, I believe. It would be nice if this patch was backported to earlier versions of Python as well but it is not critical for me. If you have further questions, let me know. This patch changes the RPM command-line as: rpm_cmd.extend(['--define', - '_topdir %s/%s' % (os.getcwd(), self.rpm_base),]) + '_topdir %s' % os.path.abspath(self.rpm_base)]) That looks good to me. The next patch is: Summary: add support for the AutoReq flag in bdist_rpm URL: https://sourceforge.net/tracker/?func=detail&atid=305470&aid=1022011&group_… This patch supplies a new option to bdist_rpm to allow the setting of the AutoReq flag in RPM to false. This ensures that no dependencies are calculated automatically. If you have further questions or want the name of the option changed, please feel free to ask. The option in this case is called "--no-autoreq". I think these patches are both fine, but wanted to get feedback on them. Any thoughts? Thanks, Sean -- I love the smell of napalm in the morning. It smells like... Victory. -- _Apocalypse_Now_ Sean Reifschneider, Member of Technical Staff <jafo(a)tummy.com> tummy.com, ltd. - Linux Consulting since 1995. Qmail, Python, SysAdmin

1 0