[Python-Dev] Python-Dev Digest, Vol 35, Issue 143 (original) (raw)

J. Jeffrey Close jjeffreyclose at yahoo.com
Tue Jun 27 01🔞25 CEST 2006

Hi all,

Sorry for my inappropriate posting. I just joined the list and didn't realize the complete scope. I will stay on the list, I'm very interested in it from a semantics & implementation perspective as well. Thanks to Brett for the heads-up.

Jeff

--- Brett Cannon <brett at python.org> wrote:

Python-Dev is about Python the language and its development. Questions on its use (and build) should be posted elsewhere (I would try comp.lang.python ). > -Brett > On 6/26/06, J. Jeffrey Close <jjeffreyclose at yahoo.com> wrote: > > > 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 > > > > > > > > > > > > > --- python-dev-request at python.org wrote: > > > Send Python-Dev mailing list submissions to > > python-dev at 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 > > python-dev-request at python.org > > > > You can reach the person managing the list at > > python-dev-owner at python.org > > > > 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 <ncoghlan at gmail.com> > > Subject: Re: [Python-Dev] ImportWarning flood > > To: Guido van Rossum <guido at python.org> > > Cc: python-dev at python.org > > Message-ID: <449FB677.9040505 at gmail.com> > > Content-Type: text/plain; charset=ISO-8859-1; > > format=flowed > > > > Guido van Rossum wrote: > > > On 6/24/06, Jean-Paul Calderone > > <exarkun at divmod.com> 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 "", line 1, in ? > > ImportError: No module named mypackage.foo > > Diagnostic import warnings can be enabled with > > -Wd > > > > Cheers, > > Nick. > > > > -- > > Nick Coghlan | ncoghlan at gmail.com | > > Brisbane, Australia > > >

> > http://www.boredomandlaziness.org > > > > > > ------------------------------ > > > > Message: 2 > > Date: Mon, 26 Jun 2006 03:41:07 -0700 (PDT) > > From: "Ralf W. Grosse-Kunstleve" <rwgk at yahoo.com> > > Subject: Re: [Python-Dev] ImportWarning flood > > To: python-dev at python.org > > Message-ID: > > > <20060626104108.89960.qmail at web31510.mail.mud.yahoo.com> > > Content-Type: text/plain; charset="iso-8859-1" > > > > --- "Martin v. L???wis" <martin at v.loewis.de> 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, === message truncated ===

More information about the Python-Dev mailing list