| 1 |
On Monday 15 October 2012 04:35:09 Gregory M. Turner wrote: |
| 2 |
> On 10/14/2012 9:29 PM, Mike Frysinger wrote: |
| 3 |
> > On Sunday 14 October 2012 04:49:28 Gregory M. Turner wrote: |
| 4 |
> >> "Thirdly" has been addressed ad nauseam in this thread and will be |
| 5 |
> >> solved by prepending the LDFLAG rather than appending, or, preferably, |
| 6 |
> >> by patching autotools (but only if I can find a simple, low-maintenance |
| 7 |
> >> approach that is likely to work without building any new per-platform |
| 8 |
> >> matrices or case-statements). |
| 9 |
> > |
| 10 |
> > i'm fairly certain this isn't autotools. i've poked around the python |
| 11 |
> > build system before in the past and while it uses autoconf to do |
| 12 |
> > platform tests, it doesn't use automake/libtool. make is used to |
| 13 |
> > bootstrap python, and then they descend into a horrible hack of a custom |
| 14 |
> > build system written in python. i suspect much of the pain you're |
| 15 |
> > seeing is coming from that last part. -mike |
| 16 |
> |
| 17 |
> And, yeah, setup.py is definitely behind all this yucky. |
| 18 |
> |
| 19 |
> Python clearly has an amazing community, so I hate to say anything |
| 20 |
> negative... but I sometimes wish they would "build" less and "buy" more. |
| 21 |
|
| 22 |
build systems are hard to get right. python is in the situation where the |
| 23 |
setups they care about mostly work and people generally aren't complaining, |
| 24 |
but it's more through a hack effort than doing it right which means all the |
| 25 |
other cases they haven't considered break horribly. cross-compiling for |
| 26 |
example has never worked correctly out of the box. |
| 27 |
-mike |
Archives