Xymon Mailing List Archive search

Compling on a mybook world NAS

4 messages in this thread

list Simon Lenz · Thu, 6 Jan 2011 16:28:03 +0100 ·
Hallo again,

I'm trying to compile xymon for several days on my mybookWorld white line
NAS

I tried the stable version and the newest beta of xymon, but everytime the
configuration script fails.

As you can see(in the following paste), the normal configure script doesn't
accept the command line parameters for the pcre and rrdtool folders, so i
use the configure.server script directly.

http://paste2.org/p/1179839

Compiling the stable version results, that he isn't able to find the
zlib.sh, which is really not in the builds folder:
http://paste2.org/p/1179843

Downloaded the archive several times, but there wasn't a zlib.sh in the
builds folder.


Is there a general fault in what i'm doing?:D

greetings
list Henrik Størner · Fri, 7 Jan 2011 12:03:17 +0000 (UTC) ·
quoted from Simon Lenz
In <user-cab208dd5f16@xymon.invalid> Simon Lenz <user-e088b8c6f0b5@xymon.invalid> writes:
I'm trying to compile xymon for several days on my mybookWorld white line
NAS
I tried the stable version and the newest beta of xymon, but everytime the
configuration script fails.
As you can see(in the following paste), the normal configure script doesn't
accept the command line parameters for the pcre and rrdtool folders, so i
use the configure.server script directly.
http://paste2.org/p/1179839
The problem here is that some of the standard Unix commands apparently
do not work on your system. If you look at the output on lines 81-83:

   Checking for RRDtool ...
   ./configure.server: build/rrd.sh: 120: tr: not found
   Makefile.test-rrd:1: Makefile.: No such file or directory

That "tr: not found" means that the "tr" command doesn't exist. That
is such a basic Unix command that the configure script assumes it is
present, and doesn't check whether that is indeed the case.

In fact, the GNU version of "tr" is part of the "core-utils" package.
You generally cannot have a Unix system without this utility.

The effect of this is that the configure script cannot generate the
test-utility it uses to determine if RRDtool is installed, and hence
it aborts with the error you see. So it's not a problem with your
rrdtool installation, it is a case of some basic Unix commands that
are missing.


Regards,
Henrik
list Simon Lenz · Fri, 7 Jan 2011 20:43:58 +0100 ·
Hallo!

you were totally correct with your suggestion:)
I installed the coreutils package via ipkg and it works! (a bit better now)

As you can see in the paste: http://paste2.org/p/1181649
The script runs now till the end (wohoo:))

But there is a warning several times:  "warning: sh_link not set for section
`.ARM.exidx'"    critical?

And additionally, there is a critical error, that prevents openssl and ldap
from working:)

   1. collect2: ld returned 1 exit status
   2. make: *** [test-link] Error 1
   3. WARNING: OpenSSL library files found in /opt/lib, but link fails.
   4. Continuing with SSL support disabled.


   1. collect2: ld returned 1 exit status
   2. make: *** [test-link] Error 1
   3. WARNING: LDAP library files found in /opt/lib, but link fails.
   4. Continuing with LDAP support disabled.

What is this ominous "link fails"?

Maybe again some missing basic packages?

Here is the list where i get all the needed packages:
http://ipkg.nslu2-linux.org/feeds/optware/cs05q1armel/cross/unstable/Packages

I've installed openssl; opennssl-dev; openldap; openldap-libs

greetings
and thanks for the help!
quoted from Henrik Størner


On 7 January 2011 13:03, Henrik Størner <user-ce4a2c883f75@xymon.invalid> wrote:
In <user-cab208dd5f16@xymon.invalid> Simon
Lenz <user-e088b8c6f0b5@xymon.invalid> writes:
I'm trying to compile xymon for several days on my mybookWorld white line
NAS
I tried the stable version and the newest beta of xymon, but everytime the
configuration script fails.
As you can see(in the following paste), the normal configure script
doesn't
accept the command line parameters for the pcre and rrdtool folders, so i
use the configure.server script directly.
http://paste2.org/p/1179839
The problem here is that some of the standard Unix commands apparently
do not work on your system. If you look at the output on lines 81-83:

  Checking for RRDtool ...
  ./configure.server: build/rrd.sh: 120: tr: not found
  Makefile.test-rrd:1: Makefile.: No such file or directory

That "tr: not found" means that the "tr" command doesn't exist. That
is such a basic Unix command that the configure script assumes it is
present, and doesn't check whether that is indeed the case.

In fact, the GNU version of "tr" is part of the "core-utils" package.
You generally cannot have a Unix system without this utility.

The effect of this is that the configure script cannot generate the
test-utility it uses to determine if RRDtool is installed, and hence
it aborts with the error you see. So it's not a problem with your
rrdtool installation, it is a case of some basic Unix commands that
are missing.


Regards,
Henrik

list Henrik Størner · Mon, 10 Jan 2011 09:30:51 +0000 (UTC) ·
In <AANLkTi==wrXpQa7obF25NBzh7=user-1ac55522c929@xymon.invalid> Simon Lenz <user-e088b8c6f0b5@xymon.invalid> writes:
But there is a warning several times:  "warning: sh_link not set for sectio=
n
`.ARM.exidx'"    critical?
No idea what this means. It is obviously ARM specific, not something
I am familiar with.
quoted from Simon Lenz
And additionally, there is a critical error, that prevents openssl and ldap
from working:)
  1. collect2: ld returned 1 exit status
  2. make: *** [test-link] Error 1
  3. WARNING: OpenSSL library files found in /opt/lib, but link fails.
  4. Continuing with SSL support disabled.
  1. collect2: ld returned 1 exit status
  2. make: *** [test-link] Error 1
  3. WARNING: LDAP library files found in /opt/lib, but link fails.
  4. Continuing with LDAP support disabled.
What is this ominous "link fails"?

The configure script will check that it can use the LDAP and SSL
libraries by first compiling a C source file, then linking it 
to produce a working executable. This error means that the link
step failed.

Sometimes this is because the LDAP/SSL libraries need some additional
libraries to work, and these may not be added automatically to the
link.

You can try running the check by hand, like this:

	MAKE=make sh -x ./build/ldap.sh

(if your "make" utility is something other than "make", then adjust
the command accordingly).

This shows what commands are used during the check. There should be
two lines like this:
	OS=Linux LDAPINC=-I/usr/include make -f Makefile.test-ldap test-compile
	OS=Linux LDAPLIB=-L/usr/lib64 LDAPLBER=-llber make -f Makefile.test-ldap test-link
which are the actual commands used to try building the LDAP test
utility.


Regards,
Henrik