W3C home > Mailing lists > Public > www-lib@w3.org > January to March 2003

MacOSX, Amaya, libwww -- newbie build problems

From: Lee Harvey Osmond <particle@clara.co.uk>
Date: Sat, 18 Jan 2003 17:39:54 +0000
To: www-lib@w3.org
Message-Id: <DAF85938-2B0B-11D7-B30E-003065D0A85E@clara.co.uk>

I have:
MacOSX 10.2.3 with the Apple Public Beta X11R6 + SDK
Apple "December 2002" developer tools
GTK 1.2 (via OpenDarwin)

I want to build Amaya ; I need libwww, but can't build it from the 
instructions, hints, etc.

I'm working through http://www.w3.org/Amaya/User/cvs.html :
I've acquired sources for Amaya and libwww from CVS.  I copied the 
destination directory, for (a) backup and (b) observation of changes 
using FileMerge.app , a cool GUI frontend to 'diff'

> % cd libwww
> % libtoolize -c -f
> % perl config/winConfigure.pl
> % aclocal; autoheader; automake; autoconf

No libtoolize on MacOSX; I have done "sudo ln -s /usr/bin/glibtoolize 

> particle% libtoolize -c -f
> You should add the contents of `/usr/share/aclocal/libtool.m4' to 
> `aclocal.m4'.
> Putting files in AC_CONFIG_AUX_DIR, `config'.

aclocal.m4 doesn't exist at this point; "cat 
/usr/share/aclocal/libtool.m4 > aclocal.m4 ; libtoolize -c -f" produces 
the same warning, so I'm guessing it's bogus.  FileMerge.app shows 
changes to config/config.guess + config/config.sub + config/ltmain.sh ; 
nothing significant, changed to slightly older versions.

I conclude that libtoolize isn't necessary here.

> particle% perl config/winConfigure.pl
> assuming global: PUBLIC FILE *WWWTrace = NULL;
> assuming global: PUBLIC unsigned int WWW_TraceFlag = 0;         /* 
> Global trace flag for ALL W3 code */
which I looks OK.

> particle% aclocal
> aclocal: macro `fp_PROG_INSTALL' defined in acinclude.m4 but never used
> [iron-duke:~/Developer/w3c/libwww] particle% autoheader
> ./aclocal.m4:268: error: m4_defn: undefined macro: _m4_divert_diversion
> aclang.m4:1689: AC_C_VOLATILE is expanded from...
> ./aclocal.m4:268: the top level
> autoconf: tracing failed

The 'undefined macros' problem is severe, known, and *appears* to have 
a fix.
The fix doesn't work for me.  The general solution quoted elsewhere is 
"don't use autoconf 2.52".  I had 2.52 ; I updated to 2.57 but the 
problem persists.

I also updated aclocal/automake from 1.6.1 to 1.7.2 .  That didn't help 

As far as I can tell, the way forward involves overhauling 
'configure.in' everywhere to work with recent distributions of autoconf 
and automake, and this will have to be done by someone who groks them, 
ie not me.   What do you think?

-- lho
Received on Saturday, 18 January 2003 12:39:57 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:33:55 UTC