🌐 Mailman 3 September 2002 - Pythonmac-SIG - python.org

Re: [Pythonmac-SIG] ObjC stuff
by Jack Jansen March 20, 2003

March 20, 2003

Recently, Steve Spicklemire <steve(a)spvi.com> said: > So it's in CVS somewhere? I'll do a check-out and see if I can find it. I don't know, Steven Majewski may know (I think he is the one who looked at it). If it isn't in the repository it probably should be, preferrably in the Modules directory (because it is useful for non-Mac users) but if there's objections against that we'll put it in the Mac/Modules dir. > I just ordered CW-6 today so I might be able to pitch in a bit. While very useful for other things (like MacPython development) you don't need it for OSX unix-Python development: this is all make and gcc-based (and you have those on your OSX developer disc). -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm

5 4

Configure question
by bill fancher Dec. 14, 2002

Dec. 14, 2002

I'm running 10.2 and upgraded autoconf to 2.53 so that I can regenerate configure from configure.in. Having done so, I now notice that I get the following line in configure output: checking LINKCC... ld: Undefined symbols: ___gxx_personality_v0 Should I worry? Is it just something I overlooked before? Is anyone else seeing this? (He asked, hoping to avoid having to isolate, and perhaps remedy, the underlying cause.) -- bill "They laughed at Columbus, they laughed at Fulton, they laughed at the Wright brothers. But they also laughed at Bozo the Clown." Carl Sagan

2 2

Re: [Pythonmac-SIG] mxDateTime for MacPython 2.1 (Classic andCarbon would be nice)
by Chris Barker Oct. 7, 2002

Oct. 7, 2002

Vincent Marchetti wrote: > Chris Barker wrote: > >Has anyone got the various mxTools compiled for MacPython? I only need > >mxDateTime at the moment, but the other stuff in mxBase would be nice > >too. > I am enclosing shared library I use with Python 2.2; thanks, that might be helpful, but I also need a version for Python 2.1 (Classic). >I compile this with the following files in my CodeWarrior > project: > > MSL_ShLibRuntime_PPC.Lib > CarbonLib (stub) > PythonCoreCarbon (stub) > mxDateTime.c I have: mxDateTime.c MSL ShLibRuntime.Lib PythonCore I'm making a classic version, so I shouldn't need the Carbon stuff, but I get the follwoing errors: Link Error : undefined 'floor' (code) Referenced from 'mxDateTime_FromGMTicks' in mxDateTime.c Referenced from 'mxDateTime_FromAbsDays' in mxDateTime.c Referenced from 'mxDateTime_AsString' in mxDateTime.c Referenced from 'mxDateTime_FromTicks' in mxDateTime.c Referenced from 'mxDateTime_CalcTicks' in mxDateTime.c Referenced from 'mxDateTime_AsTicksWithOffset' in mxDateTime.c Referenced from 'mxDateTime_TimeString' in mxDateTime.c Referenced from 'mxDateTimeDelta_AsString' in mxDateTime.c Anyone have any idea how to solve this?? It sure looks like a mathlib problem, but I have no idea what to include.

2 2

porting a python extension to OS X 10.2
by Stephen A. Langer Oct. 3, 2002

Oct. 3, 2002

Hello -- Can someone point me to a summary of how to compile and link a Python extension module, written in C++, under OS X 10.2? On other Unixes (Linux, SGI), we compile with gcc 2.95.x and link with gcc -shared, producing a .so file which Python is happy to load. gcc 3.1 on OS X doesn't understand -shared. Do I have to use libtool instead? When I try to do that, libtool complains at the end about all sorts of undefined symbols, which should have been resolved by the list of libraries it was given. What am I missing? Many thanks, Steve -- -- EMail: stephen.langer(a)nist.gov Phone: (301) 975-5423 -- -- WWW: http://math.nist.gov/mcsd/Staff/SLanger/ Fax: (301) 990-4127 -- -- Mail: NIST; 100 Bureau Drive -- Stop 8910; Gaithersburg, Md 20899-8910 --

2 3

Problems simulating command-line arguments
by Robin Siebler Oct. 2, 2002

Oct. 2, 2002

When I try to simulate command-line arguments by holding down the option key and double-clicking on a script, I am getting the following behavior: 1. The finder window containing the script immediately closes. I find this *highly* annoying. Is this a known bug, or something I can turn off? 2. 75% of the time, the interpreter launches without the dialog (where command-line arguments can be set) appearing. 3. 25% of the time, the dialog appears and I am able to set the command-line arguments. Robin L. Siebler Software Test Engineer Palm --------------------------------------- Monty' Burns: Get me Steven Spielberg! Waylon Smithers: He's unavaliable. Monty' Burns: Then get me his non-union Mexican equivalent!

4 3

Failing to import PyGreSQL module (Python 2.2.1 on 10.2.1)
by Philippe Schmid Sept. 30, 2002

Sept. 30, 2002

I am trying to use the PyGreSQL python module ... without much success. Compiling seems to be fine with cc -shared -flat_namespace -undefined suppress -o _pg.so -I/usr/include/python2.2 -I/Users/higgins/Documents/postgres/postgresql-7.2.2/src/include/ -I/usr/local/pgsql/include -L/usr/local/pgsql/lib -lpq pgmodule.c but when trying to "import _pg" in Python (interpreter), I get this: Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: Failure linking new module I also tried to compile with "standards" flags, as CFLAGS = -no-cpp-precomp and LDFLAGS = -lgcc If someone has another DB working module for Postgres, that would be also fine (I also tried the PyPgSQL one, but compilation fails and I do not have soo much time to debug this now). Someone an Idea ? Many thanks for helping... Philippe Schmid <phschmid(a)cadinfo.ch>

1 0

Re: [Pythonmac-SIG] Jaguar Macho Build woes
by Michael Hudson Sept. 28, 2002

Sept. 28, 2002

"Stephen R. Figgins" <fig(a)monitor.net> writes: > On 9/27/02 3:35 AM, "Michael Hudson" <mwh(a)python.net> wrote: > > > > This is awfully hard to diagnose. What happens when setup.py tries to > > build _socket? > > It didn't even try. The default modules/Setup file didn't say to build it. I'm guessing you don't quite understand how extension modules are built any more? setup.py (note: NOT Modules/Setup) certainly should try to build _socket... > You have two options in that file, you can do plain sockets or support SSL. > Enabling either of those you will run into some build problems though with > missing symbols when you go to make python. You need to include the > libcrypt or libssl libraries, to build SSL support and something else for > IPV6, which I wasn't sure about. I ended up configuring Python without IPV6 > support (--disable ipv6) since I didn't need it and couldn't figure out the > right command to search my library files for the missing symbols. This should be fixed in CVS (both HEAD and release22-maint). > I wasn't exactly sure how to put -lssl and -lcrypt into the make command to > build the modules either, so I just ran the command manually where make > bombed out, then resumed make. This is a new one on me; I've not heard of ssl problems before. Cheers, M. -- (Unfortunately, while you get Tom Baker saying "then we were attacked by monsters", he doesn't flash and make "neeeeooww-sploot" noises.) -- Gareth Marlow, ucam.chat, from Owen Dunn's review of the year

1 0

Re: [Pythonmac-SIG] Jaguar Macho Build woes
by Michael Hudson Sept. 27, 2002

Sept. 27, 2002

Russell E Owen <owen(a)astro.washington.edu> writes: > Stephen R. Figgins <fig(a)monitor.net> wrote: > >I am following Tony Lownds instructions for Macho Python + Tkinter and > >compiling on Jaguar...I am missing some shared object files. Most > >importantly, _socket. > > I'm seeing the same thing. I did the standard unix build (after > installing ReadLines 4.2 and Tcl/Tk 8.something (3 or 4, I don't > recall which at the moment). It all seemed to build OK, though I may > have missed some error messages. The result seems just fine except no > _socket. I have no idea how to fix it. This is awfully hard to diagnose. What happens when setup.py tries to build _socket? Cheers, M. -- That one is easily explained away as massively intricate conspiracy, though. -- Chris Klein, alt.sysadmin.recovery

3 2

Compiling MachoPython 2.2.1 on Jaguar: _socket
by Russell E Owen Sept. 27, 2002

Sept. 27, 2002

Brian Lenihan kindly gave me permission to post his fix. This patch is NOT needed in the upcoming Python versions 2.2.2 and 2.3. Brian also said that he personally uses Python 2.3 from CVS. -- Russell ----- email from Brian Lenihan, posted with permission ----- There is a work-around for an OS X bug in the socketmodule which is no longer needed and prevents the socketmodule from compiling. line 216 of Modules/socketmodule.c: #ifdef __APPLE__ /* On OS X, getaddrinfo returns no error indication of lookup failure, so we must use the emulation instead of the libinfo implementation. Unfortunately, performing an autoconf test for this bug would require DNS access for the machine performing the configuration, which is not acceptable. Therefore, we determine the bug just by checking for __APPLE__. If this bug gets ever fixed, perhaps checking for sys/version.h would be appropriate, which is 10/0 on the system with the bug. */ /*#undef HAVE_GETADDRINFO*/ /* avoid clashes with the C library definition of the symbol. */ /*#define getaddrinfo fake_getaddrinfo*/ #endif You can delete the whole section, or comment out the #undef and the #define as long as you don't nest the comments. I've found it is prudent to run make again after a Python build to see if any modules failed to compile.

1 0

Re: [Pythonmac-SIG] Jaguar Macho Build woes
by Russell E Owen Sept. 27, 2002

Sept. 27, 2002

Correction: the person who sent me instructions for getting _socket to build was Brian Lenihan. My deepest apologies for being careless and for wasting bandwidth. -- Russell

1 0