| 1 |
On 10/14/2012 9:29 PM, Mike Frysinger wrote: |
| 2 |
> On Sunday 14 October 2012 04:49:28 Gregory M. Turner wrote: |
| 3 |
>> "Thirdly" has been addressed ad nauseam in this thread and will be |
| 4 |
>> solved by prepending the LDFLAG rather than appending, or, preferably, |
| 5 |
>> by patching autotools (but only if I can find a simple, low-maintenance |
| 6 |
>> approach that is likely to work without building any new per-platform |
| 7 |
>> matrices or case-statements). |
| 8 |
> |
| 9 |
> i'm fairly certain this isn't autotools. i've poked around the python build |
| 10 |
> system before in the past and while it uses autoconf to do platform tests, it |
| 11 |
> doesn't use automake/libtool. make is used to bootstrap python, and then they |
| 12 |
> descend into a horrible hack of a custom build system written in python. i |
| 13 |
> suspect much of the pain you're seeing is coming from that last part. |
| 14 |
> -mike |
| 15 |
|
| 16 |
I guess I should say "in src_prepare" rather than "in autotools." |
| 17 |
|
| 18 |
Specifically, I was thinking some kind of configure.in patch might be |
| 19 |
good, since configure.in seems to churn less than Makefile.in, a good |
| 20 |
thing if I want to produce a one-size-fits-all patch. |
| 21 |
|
| 22 |
And, yeah, setup.py is definitely behind all this yucky. |
| 23 |
|
| 24 |
Python clearly has an amazing community, so I hate to say anything |
| 25 |
negative... but I sometimes wish they would "build" less and "buy" more. |
| 26 |
|
| 27 |
Anyhow, as everyone knows, bitching and moaning about FOSS is pointless |
| 28 |
so I'll stop there and spend my time fixing stuff instead :) |
| 29 |
|
| 30 |
-gmt |
Archives