Hi Aldas
Aldas Nabazas-2 wrote:
>
>
> Hey,
>
>>> This worries me a bit as well. I'm going to do a new build using
>>> autoconf
>>> 2.65, i don't think i fancy the idea of patching m4 files regularly to
>>> overcome whatever might've been broken in autoconf 2.66 or 2.67.
>
> Could you please try reverting only last autoconf commit :
> svn merge -r 37052:37051 .
>
done
>
> I have a feeling that fix we have with autoconf 2.66 is fine
>
> Thanks,
> Aldas
>
>
Done that. I still run into the same error when building Poppler (stage 5).
configure:18740: error: possibly undefined macro: AS_MESSAGE_LOG_FDdnl
If this token and others ar elegitimate, please use the m4_pattern
allow.
See the autoconf documentation.
Could you please confirm if when building Poppler, you have this problem if
using autoconf 2.66 + hotfix mentioned above?
I seem to get this in 2.66, 2.66+hotfix, 2.67 no matter what, and the
culprit ends up being pkgconfig's pkg.m4. There's something fishy going on
here. Going for the 4th build with 2.65 now.
Luisbf
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [email protected] with a subject of: unsubscribe t2
>
>
--
View this message in context:
http://old.nabble.com/Patches-fixes-for-9.0-trunk-tp29401692p29411051.html
Sent from the T2 mailing list archive at Nabble.com.
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
