
Time to retire some more obsolete autoconf macros. See [1] for details. 1: Replace AC_CANONICAL_SYSTEM with AC_CANONICAL_TARGET . 2: Replace AC_ERROR with AC_MSG_ERROR . 3: Replace AC_TRY_COMPILE with AC_COMPILE_IFELSE / AC_LANG_PROGRAM . This doesn't break for me, but it affects some host-dependent parts of configure.in . It would be good to know that this works on hosts with unusual socket / iconv library routines. 4: Replace AC_TRY_LINK_FUNC with AC_LINK_IFELSE / AC_LANG_CALL . This only affects target OSes *other* than linux, solaris, osf1 and minix. Can anyone test on such a thing? 5: Indentation tweak for consistency. Regards, Jeremy Henty [1] http://www.gnu.org/software/autoconf/manual/html_node/Obsolete-Macros.html#O...

Jeremy wrote:
Time to retire some more obsolete autoconf macros. See [1] for details.
1: Replace AC_CANONICAL_SYSTEM with AC_CANONICAL_TARGET .
2: Replace AC_ERROR with AC_MSG_ERROR .
3: Replace AC_TRY_COMPILE with AC_COMPILE_IFELSE / AC_LANG_PROGRAM .
This doesn't break for me, but it affects some host-dependent parts of configure.in . It would be good to know that this works on hosts with unusual socket / iconv library routines.
4: Replace AC_TRY_LINK_FUNC with AC_LINK_IFELSE / AC_LANG_CALL .
This only affects target OSes *other* than linux, solaris, osf1 and minix. Can anyone test on such a thing?
5: Indentation tweak for consistency.
Works without giving me any problems...

corvid wrote:
Jeremy wrote:
Time to retire some more obsolete autoconf macros. See [1] for details.
1: Replace AC_CANONICAL_SYSTEM with AC_CANONICAL_TARGET .
2: Replace AC_ERROR with AC_MSG_ERROR .
3: Replace AC_TRY_COMPILE with AC_COMPILE_IFELSE / AC_LANG_PROGRAM .
This doesn't break for me, but it affects some host-dependent parts of configure.in . It would be good to know that this works on hosts with unusual socket / iconv library routines.
4: Replace AC_TRY_LINK_FUNC with AC_LINK_IFELSE / AC_LANG_CALL .
This only affects target OSes *other* than linux, solaris, osf1 and minix. Can anyone test on such a thing?
5: Indentation tweak for consistency.
Works without giving me any problems...
OK. Does anyone else have any concerns? Is this OK to push? Regards, Jeremy Henty

On Sat, Jan 08, 2011 at 11:31:56PM +0000, Jeremy Henty wrote:
corvid wrote:
Jeremy wrote:
Time to retire some more obsolete autoconf macros. See [1] for details.
1: Replace AC_CANONICAL_SYSTEM with AC_CANONICAL_TARGET .
2: Replace AC_ERROR with AC_MSG_ERROR .
3: Replace AC_TRY_COMPILE with AC_COMPILE_IFELSE / AC_LANG_PROGRAM .
This doesn't break for me, but it affects some host-dependent parts of configure.in . It would be good to know that this works on hosts with unusual socket / iconv library routines.
4: Replace AC_TRY_LINK_FUNC with AC_LINK_IFELSE / AC_LANG_CALL .
This only affects target OSes *other* than linux, solaris, osf1 and minix. Can anyone test on such a thing?
5: Indentation tweak for consistency.
Works without giving me any problems...
OK. Does anyone else have any concerns? Is this OK to push?
+1 The real feedback should arrive once we have a fltk-1.3 based release. Let's hope it happens soon. -- Cheers Jorge.-

On Sun, Jan 09, 2011 at 01:37:54PM -0300, Jorge Arellano Cid wrote:
[...] The real feedback should arrive once we have a fltk-1.3 based release. Let's hope it happens soon.
BTW, we have rc3 [1]. [1] http://fltk.org/articles.php?L1033 -- Cheers Jorge.-

Jorge Arellano Cid wrote:
On Sat, Jan 08, 2011 at 11:31:56PM +0000, Jeremy Henty wrote:
corvid wrote:
Jeremy wrote:
Time to retire some more obsolete autoconf macros. See [1] for details.
1: Replace AC_CANONICAL_SYSTEM with AC_CANONICAL_TARGET .
2: Replace AC_ERROR with AC_MSG_ERROR .
3: Replace AC_TRY_COMPILE with AC_COMPILE_IFELSE / AC_LANG_PROGRAM .
This doesn't break for me, but it affects some host-dependent parts of configure.in . It would be good to know that this works on hosts with unusual socket / iconv library routines.
4: Replace AC_TRY_LINK_FUNC with AC_LINK_IFELSE / AC_LANG_CALL .
This only affects target OSes *other* than linux, solaris, osf1 and minix. Can anyone test on such a thing?
5: Indentation tweak for consistency.
Works without giving me any problems...
OK. Does anyone else have any concerns? Is this OK to push?
+1
All pushed. I hope that anyone building Dillo on non-Linux systems will report any problems as soon as possible. I can only test on Linux so I rely on others to tell me if I break the build on other systems. Regards, Jeremy Henty

On Mon, Jan 10, 2011 at 09:58:43PM +0000, Jeremy Henty wrote:
Jorge Arellano Cid wrote:
On Sat, Jan 08, 2011 at 11:31:56PM +0000, Jeremy Henty wrote:
corvid wrote:
Jeremy wrote:
Time to retire some more obsolete autoconf macros. See [1] for details.
1: Replace AC_CANONICAL_SYSTEM with AC_CANONICAL_TARGET .
2: Replace AC_ERROR with AC_MSG_ERROR .
3: Replace AC_TRY_COMPILE with AC_COMPILE_IFELSE / AC_LANG_PROGRAM .
This doesn't break for me, but it affects some host-dependent parts of configure.in . It would be good to know that this works on hosts with unusual socket / iconv library routines.
4: Replace AC_TRY_LINK_FUNC with AC_LINK_IFELSE / AC_LANG_CALL .
This only affects target OSes *other* than linux, solaris, osf1 and minix. Can anyone test on such a thing?
5: Indentation tweak for consistency.
Works without giving me any problems...
OK. Does anyone else have any concerns? Is this OK to push?
+1
All pushed. I hope that anyone building Dillo on non-Linux systems will report any problems as soon as possible. I can only test on Linux so I rely on others to tell me if I break the build on other systems.
No problems here on DragonFly BSD. Regards, Johannes
participants (4)
-
corvid@lavabit.com
-
jcid@dillo.org
-
Johannes.Hofmann@gmx.de
-
onepoint@starurchin.org