| 1 |
Helmut Jarausch writes: |
| 2 |
|
| 3 |
> I'm trying to find out why I get a configure error (on one machine) |
| 4 |
> |
| 5 |
> ./configure: line 14859: test: too many arguments |
| 6 |
> |
| 7 |
> Looking at this line it shows |
| 8 |
> if test $ax_python_header != no; then |
| 9 |
> |
| 10 |
> So, how can I find out the value of $ax_python_header. |
| 11 |
> |
| 12 |
> Putting some echo statements into configure doesn't work, |
| 13 |
> it seems to regenerated on each 'ebuild .... compile' |
| 14 |
|
| 15 |
I'd call the configure script by hand, search for it in /var/tmp/portage. |
| 16 |
If it gives the same error (which may not be the case because you do not |
| 17 |
give it the same arguments as portage does), add the echo statement, and |
| 18 |
try again to see the value of $ax_python_header. I guess it has whitespace |
| 19 |
in it, so the test fails. This would be solved by quoting the variable. |
| 20 |
The configure script is created from something like configure.ac, you will |
| 21 |
probably find the test statement there, too. You could change it (adding |
| 22 |
quotes), and use ebuild ... compile to build. |
| 23 |
|
| 24 |
Please file a bug for the package. |
| 25 |
|
| 26 |
Wonko |
Archives