Hi Dominique,
On Wed, 9 Dec 2009, Dominique Leuenberger a.k.a DimStar wrote:
>
> The 'actual' source of the problem is autoconf that was used to
> publish the tarball:
>
> AC_C_CONST is 'buggy' in this version and causes this error.
Historically we always used fairly old autotools because it worked
well with all the Linux distros and other OSes.
The latest tarball was made on a relatively new, openSUSE 11.0 with
autoconf-2.61-85.1. So far there was no complains.
Do you know if autoconf-2.61-85.1 has update? I couldn't find.
Alternatively we can use other autoconf. Thanks.
Regards,
Szaka
> See also http://www.mail-archive.com/[email protected]/msg00825.html.
>
> I'm fiddling with autogen.sh to re-create the configure script during
> build now (for some weird reason it does not work in my chroot env,
> but it does work in my normal system... up to some nice tracing).
>
> Thanks anyhow for the pointer! That was a good help.
>
> Dominique
>
> ------------------------------------------------------------------------------
> Return on Information:
> Google Enterprise Search pays you back
> Get the facts.
> http://p.sf.net/sfu/google-dev2dev
> _______________________________________________
> ntfs-3g-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
>
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
ntfs-3g-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel