Hi everyone. I have a box I'm wanting to try LiveSupport out on for one of my Internet Radio Stations. I followed the docs so far and got to the "make setup && make compile" stage, it ran for about 30 minutes, then displayed:
> Just wondering if anyone has any ideas to point me in the right direction.
> FreeBSD 5.3-RELEASE, AMD Athlon XP 2000+, PostgreSQL 8, Apache1.3.
oh oh, it seems the cp command on FreeBSD does not support the -a option.
I replaced cp -a in all scripts with cp -pPR, which is in essence it's
equivalent. please do a CVS udpate, and try again.. (and please install
doxygen before doing so).
Akos
------------------------------------------
Posted to Phorum via PhorumMail
livesupport-dev@eserver2.mdlf.org wrote:
> This message was sent from: LiveSupport Development.
>
> ----------------------------------------------------------------
>
> Hi. Sorry, I wasn't thinking straight.
>
>
>
> Did that and ran again. I had libxml 2.6.13 installed before, and I got
> this:
first, this is a bad idea. we're using libxml++-2.8.1, and we've
included it in our tools section. when you run make setup (or make
tools_setup) from the main livesupport directory, this version is
compiled and installed under livesupport/usr. that's what livesupport uses.
I'm sure you've read the getting started documentation:
Hi. Yes I read the documentation, in particular the Install doc, which I still have open. It says that the tools are expected on the system, so I guess that's why I installed it.
Here is the output of the things you requested:
--------------------
-bash-3.00$ aclocal --version
aclocal (GNU automake) 1.8.5
-bash-3.00$ automake --version
automake (GNU automake) 1.8.5
-bash-3.00$ ./autogen.sh
I am going to run ./configure with no arguments - if you wish
to pass any to it, please specify them on the ./autogen.sh command line.
Generating configuration files for Core, please wait....
livesupport-dev@eserver2.mdlf.org wrote:
> This message was sent from: LiveSupport Development.
>
> ----------------------------------------------------------------
>
> Hi. Yes I read the documentation, in particular the Install doc, which I
> still have open. It says that the tools are expected on the system, so I
> guess that's why I installed it.
excellent. you probably see that neither the development tools document:
> Here is the output of the things you requested:
>
>
>
> --------------------
>
>
>
> -bash-3.00$ aclocal --version
>
> aclocal (GNU automake) 1.8.5
>
>
>
>
>
> -bash-3.00$ automake --version
>
> automake (GNU automake) 1.8.5
>
>
>
> -bash-3.00$ ./autogen.sh
>
> I am going to run ./configure with no arguments - if you wish
>
> to pass any to it, please specify them on the ./autogen.sh command line.
>
> Generating configuration files for Core, please wait....
>
> aclocal
> --output=/usr/home/mixx941/livesupport/livesupport/modules/core/tmp/aclocal.m4
>
> acinclude.m4:39: warning: underquoted definition of PKG_CHECK_MODULES
oh, I see. can you invoke automake 1.7 instead? usually you are able to
achieve this with setting some environment variable (on my system for
example it's simply WANT_AUTOMAKE=1.7)
Akos
------------------------------------------
Posted to Phorum via PhorumMail
Right, I didn't install libxml++, I installed libxml2-2.6.19 from the FreeBSD ports as mentioned in install.html in the tarball under "Libraries". I assume libxml2-2.6.19 is different from libxml++-2.10.0, seeing as the descriptions say:
libxml++-2.10.0
XML API for C++
libxml2-2.6.19
XML parser library for GNOME
On the automake 1.7, I'm not sure how. I asked around in some FreeBSD irc rooms, and nobody there knew either.
livesupport-dev@eserver2.mdlf.org wrote:
> This message was sent from: LS Development.
>
> ----------------------------------------------------------------
>
> Right, I didn't install libxml++, I installed libxml2-2.6.19 from the
> FreeBSD ports as mentioned in install.html in the tarball under
> "Libraries". I assume libxml2-2.6.19 is different from libxml++-2.10.0,
> seeing as the descriptions say:
yes, you're totally right, LiveSupport assumes libxml2 installed, but
not libxml++.
> On the automake 1.7, I'm not sure how. I asked around in some FreeBSD irc
> rooms, and nobody there knew either.
let me know if you have automake 1.7 available. unfortunately things
changed after 1.7, if you just google for the error message:
"warning: underquoted definition of ..."
you'll get a zillion hits
Akos
------------------------------------------
Posted to Phorum via PhorumMail
The only thing I got from talking to people about automake was that 7 is no longer even in the FreeBSD ports, and I've confirmed that it is not.
I will admit I am not the best at development, but I'd like to keep trying to get your product installed. . The demo looks good, and may be exactly what I need for one of my Internet Radio Stations.
livesupport-dev@eserver2.mdlf.org wrote:
> This message was sent from: LS Development.
>
> ----------------------------------------------------------------
>
> The only thing I got from talking to people about automake was that 7 is no
> longer even in the FreeBSD ports, and I've confirmed that it is not.
this is quite strange indeed, as on Linux, if I install automake 1.9, I
get actually all versions from 1.4 to 1.9. I can invoke them explictly
by automake-1.X, or implicitly by setting an environment variable, as I
mentioned before...
> I will admit I am not the best at development, but I'd like to keep trying
> to get your product installed. . The demo looks good, and may be
> exactly what I need for one of my Internet Radio Stations.
good to hear that you find our project possibly useful!
Akos
------------------------------------------
Posted to Phorum via PhorumMail
Hi. I've been working with Fransman and Maroy on my bug report, and I was told to ask you about this part.
They told me to run bin/install.sh from tools/lcov/lcov-1.3 and check for errors.
Here is the result:
installing lcov-1.3 from /usr/home/mixx941/livesupport/livesupport/tools/lcov/lcov-1.3 to /usr/home/mixx941/livesupport/livesupport/usr
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -Naur lcov-1.3/bin/geninfo lcov-1.3-regexp-fix/bin/geninfo
|--- lcov-1.3/bin/geninfo 2004-04-29 00:57:11.000000000 +0700
|+++ lcov-1.3-regexp-fix/bin/geninfo 2004-08-02 12:51:48.996719688 +0700
--------------------------
Patching file bin/geninfo using Plan A...
Hunk 0000001 succeeded at 707.
done
bin/install.sh bin/lcov /usr/home/mixx941/livesupport/livesupport/usr/bin/lcov
bin/install.sh:No such file or directory
*** Error code 1
Stop in /usr/home/mixx941/livesupport/livesupport/tools/lcov/lcov-1.3/tmp/lcov-1.3.
you can post a bugreport on the issue, but lcov is not essential to
build LiveSupport (it's just a tool reporting code coverage metrics...)
livesupport-dev@eserver2.mdlf.org wrote:
> This message was sent from: LS Development.
>
> ----------------------------------------------------------------
>
> Hi. I've been working with Fransman and Maroy on my bug report, and I was
> told to ask you about this part.
>
> They told me to run bin/install.sh from tools/lcov/lcov-1.3 and check for
> errors.
>
> Here is the result:
>
> installing lcov-1.3 from
> /usr/home/mixx941/livesupport/livesupport/tools/lcov/lcov-1.3 to
> /usr/home/mixx941/livesupport/livesupport/usr
> Hmm... Looks like a unified diff to me...
> The text leading up to this was:
> --------------------------
> |diff -Naur lcov-1.3/bin/geninfo lcov-1.3-regexp-fix/bin/geninfo
> |--- lcov-1.3/bin/geninfo 2004-04-29 00:57:11.000000000 +0700
> |+++ lcov-1.3-regexp-fix/bin/geninfo 2004-08-02 12:51:48.996719688 +0700
> --------------------------
> Patching file bin/geninfo using Plan A...
> Hunk 0000001 succeeded at 707.
> done
> bin/install.sh bin/lcov
> /usr/home/mixx941/livesupport/livesupport/usr/bin/lcov
> bin/install.sh:No such file or directory
> *** Error code 1
>
> Stop in
> /usr/home/mixx941/livesupport/livesupport/tools/lcov/lcov-1.3/tmp/lcov-1.3.
>
>
> Thanks
>
> -Mark
>
> ----------------------------------------------------------------
> Sent using Phorum software version 3.4.3a
>
------------------------------------------
Posted to Phorum via PhorumMail