1 |
On 12/12/2012 1:45 PM, Fabian Groffen wrote: |
2 |
|
3 |
> so, what you basically want is |
4 |
> 1) a patch to the python-2.7.3 ebuild for cygwin |
5 |
> 2) a new tar of that |
6 |
> |
7 |
> (see the ebuild for comments about what to comment out, it's really as |
8 |
> simple as running ebuild ... prepare and tarring the result up) |
9 |
> |
10 |
> right? |
11 |
|
12 |
No. |
13 |
|
14 |
> If so, let's start with the patch that you need. |
15 |
|
16 |
I thought the log bits made it obvious, the bootstrap-prefix.sh just |
17 |
started, its not using an ebuild, it just downloaded zlib, and built it, |
18 |
then downloaded python-2.7.2-patched, and while building it the (trivial |
19 |
to fix) error stops everything. |
20 |
|
21 |
I just want to know if there is a procedure to not start from the |
22 |
beginning. The "patch" I want to do is to python-2.7.2-patched, |
23 |
specifically Python-2.7.2/Modules/_io/_iomodule.c:172 which shouldn't |
24 |
re-declare anything. |
25 |
-- |
26 |
René Berber |