Hi Brad: Thanks for the confirmation.
However, I have another issue related to the first problem. Basically my x86_64 CentOS is detected as "x86_64-unknown-linux-gnu" and thus it is setting LIB_SUFFIX to "lib" instead of "lib64". Do RHEL hosts really identify themselves as x86_64-redhat-linux*? How about Fedora? I do confirm that this works as expected on an openSUSE box. Perhaps we should reverse the logic and make a special case for Debian instead? Cheers, Bernard On Wed, Mar 3, 2010 at 11:28 AM, Brad Nicholes <bnicho...@novell.com> wrote: > I am seeing the same thing. To get past it I just hardcoded the path to the > sed utility. I'm guessing that either some platforms or some version of > libtool isn't setting the SED environment variable but the configure script > assumes that it is. > > Brad > >>>> On 3/2/2010 at 6:21 PM, in message > <d4c731da1003021721s695b2d27j235ecee31cdca...@mail.gmail.com>, Bernard Li > <bern...@vanhpc.org> wrote: >> Hi all: >> >> I am having problems building trunk r2290. >> >> Specifically I have 2 issues: >> >> 1) During ./configure >> >> ./configure: line 20056: syntax error near unexpected token `)' >> ./configure: line 20056: `x86_64-suse-linux*)' >> >> 2) During make -C web conf.php >> >> make: Entering directory `/root/code/ganglia.trunk/web' >> ../scripts/fixconfig conf.php.in >> ../scripts/fixconfig: line 60: @SED@: command not found >> ../scripts/fixconfig: line 67: : No such file or directory >> make: *** [conf.php] Error 1 >> make: Leaving directory `/root/code/ganglia.trunk/web' >> >> The first issue could be fixed by the following patch: >> >> Index: configure.in >> =================================================================== >> --- configure.in (revision 2290) >> +++ configure.in (working copy) >> @@ -341,8 +341,7 @@ >> # (insert others here) >> LIB_SUFFIX=lib >> case $host in >> -x86_64-redhat-linux*) >> -x86_64-suse-linux*) >> +x86_64-redhat-linux* | x86_64-suse-linux*) >> LIB_SUFFIX=lib64 >> ;; >> esac >> >> The second issue... does it have something to do with the old >> autotools that I'm using? >> >> Thanks, >> >> Bernard >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> Ganglia-developers mailing list >> Ganglia-developers@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/ganglia-developers > > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Ganglia-developers mailing list > Ganglia-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ganglia-developers > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
