[MacPorts] #42320: py-bottleneck @0.8.0 unbuildable on small machines (was: py-bottleneck-0.8.0 unbuiltable on small machines)

[MacPorts]

#42320: py-bottleneck @0.8.0 unbuildable on small machines
----------------------------+------------------------
  Reporter:  drjesacco@…    |      Owner:  stromnov@…
      Type:  defect         |     Status:  new
  Priority:  Normal         |  Milestone:
 Component:  ports          |    Version:  2.2.1
Resolution:                 |   Keywords:
      Port:  py-bottleneck  |
----------------------------+------------------------
Changes (by ryandesign@…):

 * owner:  macports-tickets@… => stromnov@…
 * port:  py-bottleneck-0.8.0 => py-bottleneck


Old description:

> GCC runs out of memory while building py-bottleneck-0.8.0 on a small
> machine with limited RAM [old G4 PowerMac]. The problem is the two
> generated C files are huge:
>
>      func.c      17MB
>      move.c      12MB
>
> Splitting each of these up into smaller files might solve the problem.  I
> do not know enough about Cython to try this myself so I contacted Keith
> Goodman, asking about the feasibility of doing this.
>
> Keith responded [29-Jan-2014]:
>
> "Yeah, that must be painful on smaller machines. I'm sure things could be
> broken down into smaller chunks. But right now I'm just doing minimal
> maintenance on bottleneck."
>

> -Joseph

New description:

 GCC runs out of memory while building py-bottleneck-0.8.0 on a small
 machine with limited RAM [old G4 PowerMac]. The problem is the two
 generated C files are huge:

 {{{
      func.c      17MB
      move.c      12MB
 }}}

 Splitting each of these up into smaller files might solve the problem.  I
 do not know enough about Cython to try this myself so I contacted Keith
 Goodman, asking about the feasibility of doing this.

 Keith responded [29-Jan-2014]:

 "Yeah, that must be painful on smaller machines. I'm sure things could be
 broken down into smaller chunks. But right now I'm just doing minimal
 maintenance on bottleneck."


 -Joseph

--

Comment:

 This does not sound like a MacPorts-specific problem. It would be up to
 the developer of this software to correct this problem.

-- 
Ticket URL: <https://trac.macports.org/ticket/42320#comment:1>
MacPorts <http://www.macports.org/>
Ports system for OS X