Hi John, > [master] $ /bin/bash /tmp/jenkins6710415235745568817.sh > ./gnulib-tool --create-megatestdir --with-tests \ > --dir=/home/jeeves/mirrors/gnu/gnulib/gnulib > Module list with included dependencies (indented): > _Exit > _Exit-tests > ... > 3 hours, 38 minutes later
Yes, --create-megatestdir is slow and produces a huge number of configure scripts. For interactive use, everyone prefers --create-testdir - but you explicitly cite doc/build-automation.texi. > It states with the machine has GNU development tools on it is needed. > I could not find exactly what tools that it needed. > > The obvious ones from web searches were: > gcc, git, make, autoconf, automake, libtool. > > After 1 hour 54 minutes, I discovered it needed bison. > > Cleaning the work directory and re-running, it took 2 hours and 6 > minutes to discover it needed "autopoint" from gettext-devel package. > > Cleaning the work directory and re-running, it took 2 hours and 22 > minutes to discover it needs "gperf" installed. These requirements are listed in the file DEPENDENCIES. > Can the web page be updated to give a complete list of tools needed? Feel free to submit a patch to doc/build-automation.texi that references DEPENDENCIES ... > Can the web page be updated to give an estimate of how long each step > that takes more than a few minutes on at least one type of CPU / memory > combination? On Cygwin the times would be very different than on Linux. Bruno
