| 1 |
On Thu, Apr 15, 2004 at 05:13:30PM -0400, Grant Goodyear wrote: |
| 2 |
|
| 3 |
> I suspect that several of our devs have little-to-no idea of how to |
| 4 |
> patch autoconf scripts. If somebody could provide an example, I suspect |
| 5 |
> that would be of great help. |
| 6 |
|
| 7 |
You have to dive into the configure script and use a little search function |
| 8 |
to find how the detection works, and how to convine it to disable some |
| 9 |
package. |
| 10 |
|
| 11 |
Sad but true, this varies heavily. Sometimes you can do something like |
| 12 |
|
| 13 |
use foo || myconf="${myconf} --with-foolib-prefix=/no/such/file |
| 14 |
|
| 15 |
sometimes you have to do something like |
| 16 |
|
| 17 |
use aalib || sed -e 's:no_aalib="":no_aalib="yes":g' -i configure || die |
| 18 |
"could not disable aalib" |
| 19 |
|
| 20 |
but as I said, it depends... |
| 21 |
|
| 22 |
Maybe that was not too much help, but I hope it gives you and idea of how |
| 23 |
ugly things can be :-) |
| 24 |
|
| 25 |
Bye, Patrick |
Archives