| 1 |
On 12-12-2012 15:24:04 -0600, René Berber wrote: |
| 2 |
> On 12/12/2012 1:45 PM, Fabian Groffen wrote: |
| 3 |
> |
| 4 |
> > so, what you basically want is |
| 5 |
> > 1) a patch to the python-2.7.3 ebuild for cygwin |
| 6 |
> > 2) a new tar of that |
| 7 |
> > |
| 8 |
> > (see the ebuild for comments about what to comment out, it's really as |
| 9 |
> > simple as running ebuild ... prepare and tarring the result up) |
| 10 |
> > |
| 11 |
> > right? |
| 12 |
> |
| 13 |
> No. |
| 14 |
> |
| 15 |
> > If so, let's start with the patch that you need. |
| 16 |
> |
| 17 |
> I thought the log bits made it obvious, the bootstrap-prefix.sh just |
| 18 |
> started, its not using an ebuild, it just downloaded zlib, and built it, |
| 19 |
> then downloaded python-2.7.2-patched, and while building it the (trivial |
| 20 |
> to fix) error stops everything. |
| 21 |
|
| 22 |
... and I told you how that tar was created, and thus what a good next |
| 23 |
step would be to help you further. |
| 24 |
|
| 25 |
> I just want to know if there is a procedure to not start from the |
| 26 |
> beginning. The "patch" I want to do is to python-2.7.2-patched, |
| 27 |
> specifically Python-2.7.2/Modules/_io/_iomodule.c:172 which shouldn't |
| 28 |
> re-declare anything. |
| 29 |
|
| 30 |
Just re-run the installer with identical input, and it will "resume". |
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
Fabian Groffen |
| 35 |
Gentoo on a different level |
Archives