Problems running the new bootstrap autoconf script on CentOS 5.5
Chad Rhyner
version of OpenTSDB, and I am having troubles during the bootstrap
script. I do not have the autoconf foo required to debug this at this
time. I starting learning more about autoconf this morning, so it
might be awhile for me... :-) I have no idea if this is related to
software dependencies or if it is related to the autoconf script.
Here is the error that I am getting, though:
autoreconf: cannot create /tmp/arB18105/arB18114/art18123/arh18132/
arQ18141/arh18150/arQ18159/arY18217/arV18323/ary18332/arf18341/
arS18350/ary18359/arC18368/arJ18377/arf18386/arr18395/arj18404/
arm18413/arz18422/arr18431/arY18440/aro18449/arC18458/arU18467/
arE18476/arF18485/arw18494/arh18503/ari18512/are18521/arZ18530/
arU18547/arC18579/art18621/arO18716/arb18775/arY18840/arG18865/
arq18891/arj18900/arz18909/arv18918/arJ18927/arg18936/art18945/
aro18954/arY18963/arH18972/arG18981/arF18990/arj18999/ars19008/
arn19017/arH19026/ara19035/arG19044/arl19053/ars19062/arX19217/
arh19226/arr19235/arZ19244/aro19253/aru19262/ard19271/arO19280/
arw19289/arg19298/arQ19307/arh19316/arr19325/arX19334/arJ19343/
arf19352/arM19361/ark19370/arK19379/arT19388/are19397/arK19406/
arB19415/arm19426/arx19435/ara19452/aro19484/arv19494/arr19503/
arD19512/aro19521/arB19530/arV19539/arg19548/arv19557/arZ19566/
arM19575/arn19584/arh19593/arS19602/arb19611/aro19620/arU19629/
ara19638/arc19647/ark19656/arm19665/ard19674/ard19683/ary19692/
arU19701/ari19710/arm19785/arb19874/arY19883/arO19892/ara19901/
arJ19910/arb19919/arJ19928/arL19937/arb19946/aru19956/arh19966/
arg19977/arK19986/ark19995/arH20004/arw20013/arB20022/arX20031/
ark20040/arB20049/arc20058/arQ20067/arU20076/arE20085/arN20094/
arI20123/ars20227/arQ20321/arm20378/arb20411/arp20437/aru20446/
are20455/arq20464/arv20473/are20482/arx20491/arp20500/arK20509/
arn20518/arI20527/ard20536/arj20545/are20554/arx20563/arr20572/
arL20581/arv20590/arY20599/arA20608/arM20617/arN20626/ark20784/
are20793/arm20802/arW20811/arU20820/arO20829/arA20838/art20847/
are20856/arB20865/arh20874/arT20883/arU20892/arN20901/arl20910/
ard20919/ari20928/ard20937/arH20946/ary20955/arQ20964/arf20973/
arf20982/arP20991/arF21000/arP21009/art21018/arn21058/arK21119/
arY21216/arb21283/art21319/arU21361/arC21370/arh21379/arM21388/
arC21397/arp21406/ard21415/arX21424/arG21433/arf21442/arN21451/
art21460/arZ21469/arb21478/arR21487/arM21496/arG21505/arr21514/
arL21523/arz21532/arE21688/arZ21697/arr21706/arq21715/arF21724/
arS21733/arW21742/arZ21751/arx21760/arC21769/arT21778/arA21787/
arc21796/arO21805/arP21814/arB21823/arY21832/arS21841/arn21850/
arJ21859/arV21868/ars21877/ard21886/arp21895/arj21904/arn21913/
aro21922/arz21931/arP21940/arY21949/arA21958/arm21974/arW22014/
arF22043/arM22124/aro22210/arq22267/arU22300/ark22326/aru22335/
arM22344/arY22353/arM22362/arE22371/arM22380/arO22389/ary22398/
ars22407/aro22416/arz22425/arD22434/arw22461/arh22598/arw22607/
ars22616/arF22625/aru22634/arB22643/ara22652/arI22661/arB22670/
arE22679/arh22688/ark22697/arO22706/arG22715/aru22724/arB22733/
arX22742/arp22751/arQ22760/arR22769/arE22778/arH22787/are22796/
arJ22805/arC22814/arJ22823/arC22832/arg22841/arM22850/arB22859/
aru22868/arn22877/arf22886/arG22895/arg22904/arZ22913/arE22922/
art22935/arC22971/arR23032/ary23130/arF23200/arX23233/arR23275/
ara23284/art23293/arF23302/arm23311/arx23320/arz23329/arV23338/
aru23347/arx23548/arn23674/arW23683/arM23692/ara23701/aro23710/
arh23723/arE23732/arZ23746/ara23755/arw23771/ari23786/arB23800/
arh23836/arT23864/arh23899/aru23917/arF23930/arz23950/arY23962/
arh23985/arW24004/ary24023/arv24037/arX24049/are24058/arh24068/
arP24077/arA24086/art24095/arJ24104/arL24113/arV24122/arb24131/
are24140/arC24149/arq24158/arc24167/arM24176/arZ24186/arr24195/
arB24206/arO24223/arG24275/arg24356/arp24442/arb24499/arp24532/
arz24558/arW24567/arF24576/arW24585/arR24740/arL24749/arx24758/
arU24767/art24776/ark24785/arK24794/arG24803/arW24812/arn24821/
arc24830/arH24839/arq24848/arT24857/ars24866/arY24875/arn24884/
arQ24893/arI24902/arc24911/arG24920/ark24929/arj24939/arH24949/
arU24958/ara24967/arA24976/arN24985/ars24994/ard25003/arh25012/
arw25021/ark25030/ard25039/arM25048/art25057/arG25066/arP25075/
arB25084/arc25093/arS25102/arx25111/art25120/ari25129/arl25138/
arF25147/arR25156/arq25165/arT25174/aro25183/arm25192/arS25201/
arM25365/arr25401/aro25463/arS25560/arX25620/arh25658/arc25700/
arF25709/arw25718/are25727/arm25736/arV25745/arR25754/arb25763/
arr25772/arM25781/ary25790/arQ25799/ars25808/arR25817/aru25826/
arL25835/arW25844/arc25853/arN25862/ars25871/aro25880/arc25889/
arL25898/arG25907/ar8439.25908: File name too long
Any suggestions or
tsuna
> I just checked out a new git repo to pull in the changes for the new
> version of OpenTSDB, and I am having troubles during the bootstrap
> script. I do not have the autoconf foo required to debug this at this
> time. I starting learning more about autoconf this morning, so it
> might be awhile for me... :-) I have no idea if this is related to
> software dependencies or if it is related to the autoconf script.
> Here is the error that I am getting, though:
>
> autoreconf: cannot create /tmp/arB18105/arB18114/art18123/arh18132/
Can you please pastebin or gist the contents of config.log?
--
Benoit "tsuna" Sigoure
Software Engineer @ www.StumbleUpon.com
Chad Rhyner
> > I just checked out a new git repo to pull in the changes for the new
> > version of OpenTSDB, and I am having troubles during the bootstrap
> > script. I do not have the autoconf foo required to debug this at this
> > time. I starting learning more about autoconf this morning, so it
> > might be awhile for me... :-) I have no idea if this is related to
> > software dependencies or if it is related to the autoconf script.
> > Here is the error that I am getting, though:
>
> > autoreconf: cannot create /tmp/arB18105/arB18114/art18123/arh18132/
>
> Can you please pastebin or gist the contents of config.log?
>
installing the newest version of autoconf 2.68 but still no luck. The
first time that I tried, I had version 2.59 of autoconf installed.
Here is the config.log using patebin: http://pastebin.com/bZt93EUA
I am still reading about autoconf, and I am now learning how much I
did not know about configure scripts. In all honesty, it is pretty
humbling! :-)
tsuna
> On Aug 4, 12:17 pm, tsuna <tsuna...@gmail.com> wrote:
>> Can you please pastebin or gist the contents of config.log?
>
> Absolutely, and thank you for the help, tsuna. I have tried
> installing the newest version of autoconf 2.68 but still no luck. The
> first time that I tried, I had version 2.59 of autoconf installed.
> Here is the config.log using patebin: http://pastebin.com/bZt93EUA
Sorry if I wasn't clear enough. I was asking for the config.log
produced by OpenTSDB's configure script. The one you pasted is the
config.log from Autoconf itself.
When you run OpenTSDB ./configure, and you get the error you initially
reported in this thread, ./configure will leave behind a config.log
that contains details about what happened, and it will probably shed
some light on why you got that weird error.
Chad Rhyner
> > On Aug 4, 12:17 pm, tsuna <tsuna...@gmail.com> wrote:
> >> Can you please pastebin or gist the contents of config.log?
>
> reported in this thread, ./configure will leave behind a config.log
> that contains details about what happened, and it will probably shed
> some light on why you got that weird error.
>
configure script execution.
http://pastebin.com/W2cAdPFT
tsuna
> Not a problem. Here is the output of config.log generated from the
> configure script execution.
> http://pastebin.com/W2cAdPFT
Wow, it's failing very early on, I've never seen this kind of failure
before. Sorry to ask you to pastebin something again, but could you
pastebin the output of "sh -x ./configure" please?
Chad Rhyner
> before. Sorry to ask you to pastebin something again, but could you
> pastebin the output of "sh -x ./configure" please?
>
The configure script cannot run successfully because I am not able to
get a successful run of the bootstrap script. When I run the
configure script, the output I get is:
configure: error: cannot find install-sh, install.sh, or shtool in
build-aux "."/build-aux
I believe that these files are created during the bootstrap script,
which is still failing. Like I mentioned in my previous post, I
updated to a new version of autoconf, and still no luck. I noticed
that CentOS 5.5 comes with an old version of m4. Actually, it is
really old. I was thinking that if I updated to the latest version of
m4, it could help find additional macros that may not have been
available in previous versions. CentOS 5.5 comes with m4 version
1.4.5, and the latest version I could find (stable version, at least)
was 1.4.16. I have updated to the 1.4.16 version, and I still get the
same error.
Right now, I leaning more towards the bootstrap script might not work
with the old versions of software that I am currently using due to
using mostly just the software provided from the CentOS 5.5 distro.
This is just a hypothesis at this point, and I cannot confirm that.
Do you have a rough idea of what software versions that I would
require to successfully run the ./bootstrap script?
tsuna
> The configure script cannot run successfully because I am not able to
> get a successful run of the bootstrap script.
Oh, right. I don't know why I asked for config.log if you couldn't
even get past the ./bootstrap point, my bad. So we have to find
what's wrong with autoreconf. You said you installed newer versions
of various tools, but are you sure that when you run "autoreconf"
(which is what the ./bootstrap script does) it picks up the new
version? Some distros install newer versions under different names –
it might be the case for CentOS.
If you run this command: autoreconf -fvi
Normally you should see exactly what autoreconf is doing, for instance
on my machine I get this:
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force -I build-aux
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/bin/autoconf --force
autoreconf: configure.ac: not using Autoheader
autoreconf: running: automake --add-missing --copy --force-missing
autoreconf: Leaving directory `.'
So I can see it's running "aclocal", "/usr/bin/autoconf" and "automake".
$ aclocal --version
aclocal (GNU automake) 1.10
$ /usr/bin/autoconf --version
autoconf (GNU Autoconf) 2.61
$ automake --version
automake (GNU automake) 1.10
If you've installed Autoconf version 2.68 and your distro calls it
"autoconf-2.68" for instance, then you can set the environment
variable AUTOCONF to tell autoreconf where to find it:
env AUTOCONF=`which autoconf-2.68` ./bootstrap
It's also possible that you installed new tools under a directory that
isn't in your PATH or that comes too late in your PATH. For instance
I have:
$ autoreconf --version
autoreconf (GNU Autoconf) 2.61
But in fact I also have a newer version on my system, under a
different directory:
$ /opt/local/bin/autoreconf --version
autoreconf (GNU Autoconf) 2.65
I can update my path to pick it up:
$ export PATH=/opt/local/bin:$PATH
$ autoreconf --version
autoreconf (GNU Autoconf) 2.65
So now I can do:
$ AUTOMAKE=`which automake-1.11` ACLOCAL=`which aclocal-1.11` ./bootstrap
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: /opt/local/bin/aclocal-1.11 --force -I build-aux
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /opt/local/bin/autoconf --force
autoreconf: configure.ac: not using Autoheader
autoreconf: running: /opt/local/bin/automake-1.11 --add-missing --copy
--force-missing
autoreconf: Leaving directory `.'
And if I look in the configure script, it says "Generated by GNU
Autoconf 2.65 for opentsdb 1.0" and the Makefile.in says "Makefile.in
generated by automake 1.11.1 from Makefile.am"
> Do you have a rough idea of what software versions that I would
> require to successfully run the ./bootstrap script?
I think these are the oldest versions that can work:
Autoconf 2.60 (released June 26, 2006)
Automake 1.9.4 (released December 18, 2004)
Newer versions should be fine.
If you don't want to deal with bootstrapping issues, I've put a
pre-bootstrapped self-contained tarball of the current stable version
of OpenTSDB here:
http://tsunanet.net/~tsuna/opentsdb/opentsdb-1.0-03b7164.tar.gz
Chad Rhyner
> pre-bootstrapped self-contained tarball of the current stable version
> of OpenTSDB here:http://tsunanet.net/~tsuna/opentsdb/opentsdb-1.0-03b7164.tar.gz
>
Apologies for not really responding as of recently, I have been out
for a couple of weeks. I used the pre-bootstrapepd tarball that you
provided, and it avoided the bootstrap problem that I was running
into, and I was able to configure, compile, and successfully start
OpenTSDB. We now have it up and running, and are working on
evaluating this for all matters related to monitoring.
Thank you for your assistance!
Cheers