Hi all, I have been trying for some time to build Python 2.4.x from source on OS X 10.4.6. I've found *numerous* postings on various mailing lists and web pages documenting the apparently well-known problems of doing so. Various problems arise either in the ./configure step, with configure arguments that don't work, or in the compile, or in my case in the link step with libtool.
The configure options I'm using are the following: --enable-framework --with-pydebug --with-debug=yes --prefix=/usr --with-dyld --program-suffix=.exe --enable-universalsdk I've managed to get past configure and can compile everything, but in the link I get the error "Undefined symbols: ___eprintf" . This appears to have something to do with dynamic library loading not properly pulling in libgcc. I've tried with -lgcc in the LD options, but that produces a configure error "cannot compute sizeof...". If I remove "--enable-framework" the complete build works, but unfortunately that is the one critical element that I need. The web pages I've found referring to this range from 2001 to present -- still apparently everybody is having problems with this. Does *anybody* here have Python built from source on this OS? Jeff --- [EMAIL PROTECTED] wrote: > Send Python-Dev mailing list submissions to > python-dev@python.org > > To subscribe or unsubscribe via the World Wide Web, > visit > http://mail.python.org/mailman/listinfo/python-dev > or, via email, send a message with subject or body > 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it > is more specific > than "Re: Contents of Python-Dev digest..." > > > Today's Topics: > > 1. Re: ImportWarning flood (Nick Coghlan) > 2. Re: ImportWarning flood (Ralf W. > Grosse-Kunstleve) > 3. Re: 2.5b1 Windows install (Nick Coghlan) > 4. Re: ImportWarning flood (Michael Hudson) > 5. Re: ImportWarning flood (A.M. Kuchling) > 6. Re: ImportWarning flood (Benji York) > 7. Re: Simple Switch statement (Michael Urman) > 8. Re: ImportWarning flood (Nick Coghlan) > 9. Re: Simple Switch statement (Guido van Rossum) > 10. Re: pypy-0.9.0: stackless, new extension > compiler > (Carl Friedrich Bolz) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 26 Jun 2006 20:27:03 +1000 > From: Nick Coghlan <[EMAIL PROTECTED]> > Subject: Re: [Python-Dev] ImportWarning flood > To: Guido van Rossum <[EMAIL PROTECTED]> > Cc: python-dev@python.org > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; > format=flowed > > Guido van Rossum wrote: > > On 6/24/06, Jean-Paul Calderone > <[EMAIL PROTECTED]> wrote: > >>> Actually, your application *was* pretty close to > being broken a few > >>> weeks ago, when Guido wanted to drop the > requirement that a package > >>> must contain an __init__ file. In that case, > "import math" would have > >>> imported the directory, and given you an empty > package. > >> But this change was *not* made, and afaict it is > not going to be made. > > > > Correct. We'll stick with the warning. (At least > until Py3k but most > > likely also in Py3k.) > > Perhaps ImportWarning should default to being > ignored, the same way > PendingDeprecationWarning does? > > Then -Wd would become 'the one obvious way' to debug > import problems, since it > would switch ImportWarning on without drowning you > in a flood of import > diagnostics the way -v can do. > > Import Errors could even point you in the right > direction: > > >>> import mypackage.foo > Traceback (most recent call last): > File "<stdin>", line 1, in ? > ImportError: No module named mypackage.foo > Diagnostic import warnings can be enabled with > -Wd > > Cheers, > Nick. > > -- > Nick Coghlan | [EMAIL PROTECTED] | > Brisbane, Australia > --------------------------------------------------------------- > http://www.boredomandlaziness.org > > > ------------------------------ > > Message: 2 > Date: Mon, 26 Jun 2006 03:41:07 -0700 (PDT) > From: "Ralf W. Grosse-Kunstleve" <[EMAIL PROTECTED]> > Subject: Re: [Python-Dev] ImportWarning flood > To: python-dev@python.org > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > --- "Martin v. L???wis" <[EMAIL PROTECTED]> wrote: > > So spend some of the money to come up with an > alternate solution for > > 2.5b2. With a potential damage of a million > dollars, it shouldn't be > > too difficult to provide a patch by tomorrow, > right? > > My share is only 10 man hours, payed for by the US > government at a scientist > salary. :-) > > A simple patch with a start is attached. Example: > > % ./python > Python 2.5b1 (r25b1:47027, Jun 26 2006, 03:15:33) > [GCC 4.1.0 20060304 (Red Hat 4.1.0-3)] on linux2 > Type "help", "copyright", "credits" or "license" for > more information. > >>> import foo > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > ImportError: No module named foo > Note that subdirectories are searched for imports > only if they contain an > __init__.py file. See the section on "Packages" in > the Python tutorial for > details (http://www.python.org/doc/tut/). > >>> > > > The "No module named" message is repeated in these > files (2.5b1 tree): > > ./Demo/imputil/knee.py > ./Lib/ihooks.py > ./Lib/modulefinder.py > ./Lib/xmlcore/etree/ElementTree.py > ./Lib/runpy.py > ./Lib/imputil.py > > If there is a consenus, I'd create a new exception > ImportErrorNoModule(name) > that is used consistently from all places. This > would ensure uniformity of the > message in the future. > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam > protection around > http://mail.yahoo.com > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: import_patch > Type: application/octet-stream > Size: 1090 bytes > Desc: 467797280-import_patch > Url : > http://mail.python.org/pipermail/python-dev/attachments/20060626/ce3bbfec/attachment-0001.obj > > > ------------------------------ > > Message: 3 > Date: Mon, 26 Jun 2006 20:46:57 +1000 > From: Nick Coghlan <[EMAIL PROTECTED]> > Subject: Re: [Python-Dev] 2.5b1 Windows install > To: Aahz <[EMAIL PROTECTED]> > Cc: Python-Dev <python-dev@python.org> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; > format=flowed > > Aahz wrote: > > Has anyone else tried doing an admin install with > "compile .py files" > > checked? It's causing my install to blow up, but > I'd prefer to assume > > it's some weird Windows config/bug unless other > people also have it, in > > which case I'll file an SF report. > > I tried this deliberately with b1 because it was > broken in one of the alphas. > It worked fine for me this time (installing over the > top of alpha 2). > > I think there were some bad .py files around that > caused the breakage in the > earlier alpha - could those have been lying around > in your install directory? > > Cheers, > Nick. > === message truncated === _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
