In message <[email protected]> Simon Wilson <[email protected]> wrote:
> 2008/10/28 John Tytgat <[email protected]> > > > > > If this means you're using autoconf v2.63, then it is more or less for > > sure your problem. The GCC 4.1 build really needs autoconf v2.59 and > > no other version. > > > > > My first build of wget failed due to an autoconf issue. > > I have autoconf 2.59 in my path: > > $ which autoconf > /usr/local/bin/autoconf > $ autoconf --version > autoconf (GNU Autoconf) 2.59 > > However, wget wanted 2.13, so I tried installing that via apt-get install > autoconf-2.13 and rebuilding. It put that version into /usr/bin. It is not really wget wanting autoconf2.13, but rather Autobuilder checking the presence of a minimal set of necessary build tools and autoconf2.13 is part of that. It is perhaps debatable what is understood as 'necessary' because AFAIK autoconf2.13 is only needed when you want to build Firefox and Thunderbird. > $ ../autobuilder/build -v wget > Autobuilder: autoconf2.13 not found; is it installed on your path? > $ sudo apt-get install autoconf2.13 > $ /usr/bin/autoconf --version > Autoconf version 2.13 > > However, it then asked for 2.61. The gccsdk wiki specifically says to only > install 2.59! To build GCCSDK 4 gcc/binutils compiler, indeed you really can only use autoconf 2.59. That's a specific restriction of gcc itself. I know of recent gcc 4.4 work to allow recent autoconf versions but I don't know how finished those changes are (months ago I stopped reading gcc dev mailing list, was too high volume for me at that time). But that version restriction isn't applicable for the projects in Autobuilder. A 2nd and perhaps more relevant remark is that I don't understand why wget would want to run an autoconf as usually the sources pulled by Autobuilder should include an up to date 'configure'. Only some Autobuilder projects need to fiddle with 'configure.in' or 'configure.ac' which requires running autoconf. Could you verify if the modification data of 'configure.in' and/or 'configure.ac' is more recent than 'configure' in your unpacked wget source ? If so, a touch of configure might be a workaround. Or perhaps your 'configure' got lost. Hope this helps, John. -- John Tytgat, in his comfy chair at home BASS [email protected] ARM powered, RISC OS driven _______________________________________________ GCCSDK mailing list [email protected] Bugzilla: http://www.riscos.info/bugzilla/index.cgi List Info: http://www.riscos.info/mailman/listinfo/gcc Main Page: http://www.riscos.info/index.php/GCCSDK
