Message196509
| Author |
sjt |
| Recipients |
amaury.forgeotdarc, mmokrejs, sjt, tim.peters, vstinner |
| Date |
2013年08月30日.04:25:53 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1377836753.97.0.396519702614.issue18843@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I have a gentoo host, but I'd like to know how did the OP get a debug Python in the first place? The ebuild for python 2.7.5-r1 doesn't say anything about debug options. "How" would preferably include information about the C compiler used, etc. If there's no information, I can probably just hack --with-pydebug into a local ebuild, but I have something like 7 C compilers installed, I'd really like a good guess at the right one. Also, did he add any optimization flags etc when building the debug Python?
(ebuild = the emerge configuration file that describes the build and install process for a package. In "2.7.5-r1" the "r1" indicates the first revised ebuild for the same upstream version.) |
|