You still haven't shown us the ./configure you're actually using.  Guess you
expect us to use the remote viewer (or is your host Tempest shielded?)

So please try a pure vanilla

$ ./configure



ltconfig (and the lines that load the cache file) are all standard libtool
and autoconf stuff.  And ltconfig hasn't changed in FOREVER:

$ cvs log ltconfig

RCS file: /export/home/ntop/ntop/ltconfig,v
Working file: ltconfig
head: 2.1
branch:
locks: strict
access list:
symbolic names:
        ntop_3_0_rc1: 2.1
        ntop_3_1_devbegin: 2.1
        ntop_3_0: 2.1.0.4
...
total revisions: 5;     selected revisions: 5
description:
----------------------------
revision 2.1
date: 2002/01/03 17:17:41;  author: deri;  state: Exp;  lines: +55 -84
Moved version to 2.0.1
----------------------------
...
============================================================================
=



If you have a version of the Gnu auto* tools installed (automake, autoconf
and libtool), try

1) comparing our ltconfig against any others on your system.  Maybe there's
a conflict?

2) recreating the set of files.

autoheader
automake
autoconf
./configure


-----Burton


> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf
> Of Leonardo Valcamonici
> Sent: Friday, March 26, 2004 11:56 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [Ntop-dev] Solaris 9 Sparc /dev/null problem
>
>
> The thing is that a simple ./configure changes my /dev/null. It seems to
> happen by the means of ltconfig. In fact, if I dig into the configure's
> log I can see:
> ...
> loading cache /dev/null within ltconfig
> ...
> and then:
>
> ./ltconfig: .: /dev/null: not a regular file
>
> out to the stderr.
>
> After this /dev/null get changed.
>
> This happens BEFORE any make ...
>
> BTW my shell is bash:
>
> #bash --version
> GNU bash, version 2.05.0(1)-release (sparc-sun-solaris2.9)
> Copyright 2000 Free Software Foundation, Inc
>
> Cheers,
> Leonardo
>
>
> .
>
> Burton M. Strauss III wrote:
>
> >Well, how about giving us even the tinyest bit of information...
> >
> >     WHAT COMMAND LINE ARE YOU RUNNING???
> >
> >
> >As a GUESS, try running make install.  It sounds like you are
> executing the
> >'ntop' temporary wrapper SCRIPT that is created by libtool.  That bad boy
> >tries to 'pretend' to execute ntop as if make install was run.
> But there's
> >probably some interaction with your command line... like it doesn't like
> >redirection.
> >
> >Do a
> >$ file ntop
> >ntop: Bourne shell script text executable
> >
> >^^^^^^^^^^^^^^^^^^^^^^ that's a bad thing
> >
> >$ file /usr/bin/ntop
> >/usr/bin/ntop: ELF 32-bit LSB executable, Intel 80386, version 1
> (SYSV), for
> >GNU/Linux 2.2.5, dynamically linked (uses shared libs), not stripped
> >
> >
> >
> >-----Burton
> >
> >
> >
> >
> >>-----Original Message-----
> >>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf
> >>Of Leonardo Valcamonici
> >>Sent: Friday, March 26, 2004 7:24 AM
> >>To: [EMAIL PROTECTED]
> >>Subject: [Ntop-dev] Solaris 9 Sparc /dev/null problem
> >>
> >>
> >>Hi all,
> >>I've noticed a problem configuring ntop with both 3.0 and the latest CVS
> >>(I'm not sure, but this applies even to the 2.2 ...).
> >>Before running a configure I have:
> >>
> >>lrwxrwxrwx   1 root     other         25 Mar 26 14:03 /dev/null ->
> >>/devices/pseudo/[EMAIL PROTECTED]:null
> >>
> >>When as root I start configure it cries this way:
> >>
> >>./ltconfig: .: /dev/null: not a regular file
> >>
> >>and after I get:
> >>
> >>-rw-rw-r--   1 root     other          0 Mar 26 14:07 /dev/null
> >>
> >>If I don't fix the problem manually I get an instable host which
> >>cannot mount /proc in a reboot and therefore hangs in limbo.
> >>
> >>I've seen someone posted the same problem a while ago, but the
> >>unfortunate got no answer ...
> >>Cheers,
> >>
> >>Leonardo

_______________________________________________
Ntop-dev mailing list
[EMAIL PROTECTED]
http://listgateway.unipi.it/mailman/listinfo/ntop-dev

Reply via email to