| 1 |
On 09/01/13 12:44, Diego Elio Pettenò wrote: |
| 2 |
> On 09/01/2013 12:39, justin wrote: |
| 3 |
>> I assume it is a portage problem, because the log says autoconf is run |
| 4 |
>> but configure.in didn't change. |
| 5 |
>> |
| 6 |
> |
| 7 |
> What do you mean configure.in didn't change but autoconf is run? |
| 8 |
> |
| 9 |
|
| 10 |
the build.log says |
| 11 |
|
| 12 |
Running eautoreconf in |
| 13 |
'/home/justin/extData/tmp/portage/dev-lang/tcl-8.5.13-r1/work/tcl8.5.13/unix' |
| 14 |
... |
| 15 |
Running autoconf ... [ok] |
| 16 |
Running autoheader ...[!!] |
| 17 |
>>> Source prepared. |
| 18 |
|
| 19 |
I overlooked the failed autoheader, which interesting didn't died |
| 20 |
(EAPI=4 ebuild). But autoconf should have been run successfully. |
| 21 |
|
| 22 |
A diff between the original and the two run build's configure.in shows |
| 23 |
only a difference by one of the two (in both cases the autoheader failed). |
| 24 |
|
| 25 |
|
| 26 |
> Does it cause a maintainer-mode rebuild? |
| 27 |
|
| 28 |
interesting not. |
| 29 |
|
| 30 |
> |
| 31 |
> Did you use eautoreconf? |
| 32 |
> |
| 33 |
|
| 34 |
yes |
Archives