Re: Which automake and autoconfig versions to compile NTOP v4?
* Kaya Saman kayasa...@gmail.com [2012-03-12 01:45]: I do understand that compiling software is part of UNIX for a pure user, no, not really. at least not any more. Using FreeBSD I would just do this: cd /usr/ports/*/ntop make install clean and providing my **ports** tree is uptodate it will work flawlessly. Additionally on Linux for RPM based would be yum install ntop or DEB based would be apt-get install ntop Great story. Uh sorry was just trying to stress or rather emphasize my point. I think eventually the only thing that got stressed was me :-( in openbsd, you just pkg_add ntop. now if that version isn't waht you want, you update the port (and submit it) - and dive into ports developers land. Would it not just be easier and cleaner to create a new list for newbies? That way the more advanced stuff could be taken care of on this list and only people willing to help others could post useful comments and help on the other list. the blind leading the blind leads nowhere. there have been attempts in that direction. As in all of my 1 week being here not much help goes on just arguments and flames. happens every now and then. it's not that we particularily like that, but that's apparently the price for an open list. -- Henning Brauer, h...@bsws.de, henn...@openbsd.org BS Web Services, http://bsws.de, Full-Service ISP Secure Hosting, Mail and DNS Services. Dedicated Servers, Root to Fully Managed Henning Brauer Consulting, http://henningbrauer.com/
Re: Which automake and autoconfig versions to compile NTOP v4?
On Mon, Mar 12, 2012 at 12:44:15AM +, Kaya Saman wrote:
my issue was how to get the Ntop config script to understand that
automake and autoconf **are** installed on the system!!!
Luckily a friendly person did explain that I should first **export** the
versions then run the config gen script which indeed worked!!!
This is very very basic Unix knowledge.
However, please note that am still learning OpenBSD after coming over
from Linux and FreeBSD and additionally I am NOT a programmer or even
good at programming
You're not very good at system admin either.
One exclamation point is enough.
Using FreeBSD I would just do this:
cd /usr/ports/*/ntop
make install clean
and providing my **ports** tree is uptodate it will work flawlessly.
Additionally on Linux for RPM based would be yum install ntop or DEB
based would be apt-get install ntop
This does work under OpenBSD too. Especially, as henning pointed out,
we have working packages, so pkg_add ntop will work.
If you want a newer version, the first thing to do, especially when you're
a complete noob with respect to ports, is to ask if someone else is working
on them.
Now I do know these without even needing to read the documentation...
however even **IF** I tried to compile on one of those platforms which I
do all the time I never need to adjust system variables or tell the
configure script what compiler or other I'm using as it is intelligent
enough to autodetect it.
The configure script is not part of the operating system, it is part of the
package/tarball, if you're using something that needs automake/autoconf
you're probably checking out development versions of software and then
complaining to the OS developers who have nothing to do with it.
Also, we're Unix. Not Linux. There's a fairly big separation between the
base system AND the ports.
autoconf is a gnu tool, and a very flawed one
at that. Which explains why you might need to install several ones
concurrently.
There are sign posts THAT BIG all over the place that explain how the
autoconf/automake/metaauto packages tie together.
I understand OpenBSD is different and I'm trying to get used to it but
please cut new users some slack as not everyone is God's gift to
computing... {I don't say this as an attack or with any bad
intentions just frustration at how unforgiving this list is sometimes}
The more you rant, the more you will get flamed, it's as simple as that.
.actually this list may become really quiet then??? As in all of
my 1 week being here not much help goes on just arguments and
flames.
So what ? you got all the help you needed with respect to your original
question, for crying out loud ! It's likely the initial messages were
not to your liking, but guess what ? it's your fault ! nobody here is
going to figure out that someone clueless enough about Unix to not know
about environment variables is going to embark on compiling a very
system-dependent tool on his own !!!
So, hey, you want to be liked on this list ? don't get so defensive at
the first hint that you're a complete newbie. Shove the angst, feel the
love.
Re: Which automake and autoconfig versions to compile NTOP v4?
On 2012 Mar 12 (Mon) at 00:44:15 + (+), Kaya Saman wrote: :Would it not just be easier and cleaner to create a new list for :newbies? That way the more advanced stuff could be taken care of on :this list and only people willing to help others could post useful :comments and help on the other list. This mailing list does exist. I've been running it (in a very lazy fasion) since 2002. You can sign up for it at http://mailman.theapt.org/listinfo/openbsd-newbies -- We can predict everything, except the future.
Re: Which automake and autoconfig versions to compile NTOP v4?
On 2012-03-11, Kaya Saman kayasa...@gmail.com wrote: Now I do know these without even needing to read the documentation... however even **IF** I tried to compile on one of those platforms which I do all the time I never need to adjust system variables or tell the configure script what compiler or other I'm using as it is intelligent enough to autodetect it. You don't usually need to run autoconf to regenerate the configure script unless you edit configure.in or other m4 files. The software authors are supposed to do that for you as part of their release process Pretty sure there is some selection mechanism for different autoconf versions on FreeBSD as well but maybe they picked a default version (at least by making it an explicit requirement OpenBSD users are less likely to be affected by incompatible autoconf versions).
Re: Which automake and autoconfig versions to compile NTOP v4?
On 2012-03-11, Kaya Saman kayasa...@gmail.com wrote: Well in mean time I found this: http://openports.se/devel/metaauto although I don't think it's installed as **find** didn't come up with anything. pkg_info | grep metaauto Also look at locate(1) which uses a database generated weekly(8) to speed up filename searches, and the pkglocate package (a locate database of files from *all* packages, not just the installed ones, also showing the package names). ntop is in ports but horribly out of date. Newer versions had some problems, I suspect many of these relating to how our old thread library worked - I might take a look at updating the port sometime now we're using rthreads. If you're looking at building it yourself I would suggest waiting for base and package snapshots to start up again, then upgrade everything to -current, before spending more time on ntop.
Re: Which automake and autoconfig versions to compile NTOP v4?
On 03/12/2012 09:59 AM, Peter Hessler wrote: On 2012 Mar 12 (Mon) at 00:44:15 + (+), Kaya Saman wrote: :Would it not just be easier and cleaner to create a new list for :newbies? That way the more advanced stuff could be taken care of on :this list and only people willing to help others could post useful :comments and help on the other list. This mailing list does exist. I've been running it (in a very lazy fasion) since 2002. You can sign up for it at http://mailman.theapt.org/listinfo/openbsd-newbies Thanks :-) And additionally I am sorry for annoying almost the whole of this list :-( I didn't mean to rant or to tick anybody off! Using OpenBSD for a bit I really do like but hence need to learn it. Regards, Kaya
Re: Which automake and autoconfig versions to compile NTOP v4?
On 03/12/2012 10:50 AM, Stuart Henderson wrote: On 2012-03-11, Kaya Samankayasa...@gmail.com wrote: Now I do know these without even needing to read the documentation... however even **IF** I tried to compile on one of those platforms which I do all the time I never need to adjust system variables or tell the configure script what compiler or other I'm using as it is intelligent enough to autodetect it. You don't usually need to run autoconf to regenerate the configure script unless you edit configure.in or other m4 files. The software authors are supposed to do that for you as part of their release process I eventually figured that one out by reading the scripts themselves, but it seems that a lot of software is unsupported on OpenBSD and the devels don't want to know either as other OS's have larger user bases. Pretty sure there is some selection mechanism for different autoconf versions on FreeBSD as well but maybe they picked a default version (at least by making it an explicit requirement OpenBSD users are less likely to be affected by incompatible autoconf versions). I will keep searching and studying this as it might be just the config scripts as you mentioned above. Regards, Kaya
Re: Which automake and autoconfig versions to compile NTOP v4?
On 03/12/2012 11:21 AM, Stuart Henderson wrote: On 2012-03-11, Kaya Samankayasa...@gmail.com wrote: Well in mean time I found this: http://openports.se/devel/metaauto although I don't think it's installed as **find** didn't come up with anything. pkg_info | grep metaauto Also look at locate(1) which uses a database generated weekly(8) to speed up filename searches, and the pkglocate package (a locate database of files from *all* packages, not just the installed ones, also showing the package names). Oh locate is available in OpenBSD? That's good news! ntop is in ports but horribly out of date. Newer versions had some problems, I suspect many of these relating to how our old thread library worked - I might take a look at updating the port sometime now we're using rthreads. If you're looking at building it yourself I would suggest waiting for base and package snapshots to start up again, then upgrade everything to -current, before spending more time on ntop. I'll do just that :-) Regards, Kaya
Which automake and autoconfig versions to compile NTOP v4?
Hi, I'm trying to compile the latest NTOP version 4.1.0 on OpenBSD RELEASE 5.0 x64 but am running into issues regarding automake and autoconfig. Basically I installed: automake-1.11.1p2 autoconf-2.67 The install script comes up saying this: # ./autogen.sh Starting ntop automatic configuration system v.0.2.3 Please be patient, there is a lot to do... 1. Testing gnu tools You must have automake installed to compile ntop. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/automake We recommend version 1.6.3 or higher You must have autoconf installed to compile autogen.sh. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/autoconf We recommend version 2.53 or higher It's weird because both packages are installed and have confirmed that running: find / -name auto(conf and make). Can anyone suggest anything? I'm actually puzzled as to why the Ntop version on the public FTP servers are s old and out of date, I mean v1.x? With that there's no Web GUI and actually works more like some of the other cli packet sniffers am used to such as trafshow, jnettop, iptraf-ng etc.. It would be so awsome to see these on the FTP servers so that all one needs to do is just pkg_add them but am stuck now compiling and not sure if it's even gona work Regards, Kaya
Re: Which automake and autoconfig versions to compile NTOP v4?
Kaya Saman wrote: Hi, I'm trying to compile the latest NTOP version 4.1.0 on OpenBSD RELEASE 5.0 x64 but am running into issues regarding automake and autoconfig. Basically I installed: automake-1.11.1p2 autoconf-2.67 The install script comes up saying this: # ./autogen.sh Starting ntop automatic configuration system v.0.2.3 Please be patient, there is a lot to do... 1. Testing gnu tools You must have automake installed to compile ntop. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/automake We recommend version 1.6.3 or higher You must have autoconf installed to compile autogen.sh. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/autoconf We recommend version 2.53 or higher It's weird because both packages are installed and have confirmed that running: find / -name auto(conf and make). Can anyone suggest anything? try: automake --version autoconf --version The messages should be self-explanatory if you didn't define certain environment variables, e.g., I have this in my environment: $ set |grep AUTO AUTOCONF_VERSION=2.65 AUTOMAKE_VERSION=1.11
Re: Which automake and autoconfig versions to compile NTOP v4?
On 03/11/2012 08:10 PM, Remco wrote: Kaya Saman wrote: Hi, I'm trying to compile the latest NTOP version 4.1.0 on OpenBSD RELEASE 5.0 x64 but am running into issues regarding automake and autoconfig. Basically I installed: automake-1.11.1p2 autoconf-2.67 The install script comes up saying this: # ./autogen.sh Starting ntop automatic configuration system v.0.2.3 Please be patient, there is a lot to do... 1. Testing gnu tools You must have automake installed to compile ntop. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/automake We recommend version 1.6.3 or higher You must have autoconf installed to compile autogen.sh. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/autoconf We recommend version 2.53 or higher It's weird because both packages are installed and have confirmed that running: find / -name auto(conf and make). Can anyone suggest anything? try: automake --version autoconf --version The messages should be self-explanatory if you didn't define certain environment variables, e.g., I have this in my environment: $ set |grep AUTO AUTOCONF_VERSION=2.65 AUTOMAKE_VERSION=1.11 automake --version autoconf --version come up with this # automake --version Provide an AUTOMAKE_VERSION environment variable, please # autoconf --version Provide an AUTOCONF_VERSION environment variable, please ?? set |grep AUTO also doesn't display anything??? However, the packages are installed in /usr/local/bin which is confirmed using **find** actually just seeing this now it turns out that automake is proceeded by a version number. So it works then I guess but why can't Ntop install script pick it out?
Re: Which automake and autoconfig versions to compile NTOP v4?
On Sun, Mar 11, 2012 at 07:42:43PM +, Kaya Saman wrote: Hi, I'm trying to compile the latest NTOP version 4.1.0 on OpenBSD RELEASE 5.0 x64 but am running into issues regarding automake and autoconfig. Basically I installed: automake-1.11.1p2 autoconf-2.67 The install script comes up saying this: # ./autogen.sh Starting ntop automatic configuration system v.0.2.3 Please be patient, there is a lot to do... 1. Testing gnu tools You must have automake installed to compile ntop. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/automake We recommend version 1.6.3 or higher You must have autoconf installed to compile autogen.sh. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/autoconf We recommend version 2.53 or higher See how the metaauto port works. autoconf and automake are actually scripts that depend on AUTOCONF_VERSION and AUTOMAKE_VERSION to select the right ones.
Re: Which automake and autoconfig versions to compile NTOP v4?
On 03/11/2012 08:20 PM, Marc Espie wrote: On Sun, Mar 11, 2012 at 07:42:43PM +, Kaya Saman wrote: Hi, I'm trying to compile the latest NTOP version 4.1.0 on OpenBSD RELEASE 5.0 x64 but am running into issues regarding automake and autoconfig. Basically I installed: automake-1.11.1p2 autoconf-2.67 The install script comes up saying this: # ./autogen.sh Starting ntop automatic configuration system v.0.2.3 Please be patient, there is a lot to do... 1. Testing gnu tools You must have automake installed to compile ntop. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/automake We recommend version 1.6.3 or higher You must have autoconf installed to compile autogen.sh. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/autoconf We recommend version 2.53 or higher See how the metaauto port works. autoconf and automake are actually scripts that depend on AUTOCONF_VERSION and AUTOMAKE_VERSION to select the right ones. Ok thankyou! .this makes sense now to me. But how to set AUTOCONF_VERSION and AUTOMAKE_VERSION??? You say metaauto port but I thought that in OpenBSD one was not supposed to used ports unlike FreeBSD which I'm used to? hmm # man metaauto man: no entry for metaauto in the manual. looks like I need to do some further Google'ing! Regards, Kaya
Re: Which automake and autoconfig versions to compile NTOP v4?
On 03/11/2012 08:20 PM, Marc Espie wrote: On Sun, Mar 11, 2012 at 07:42:43PM +, Kaya Saman wrote: Hi, I'm trying to compile the latest NTOP version 4.1.0 on OpenBSD RELEASE 5.0 x64 but am running into issues regarding automake and autoconfig. Basically I installed: automake-1.11.1p2 autoconf-2.67 The install script comes up saying this: # ./autogen.sh Starting ntop automatic configuration system v.0.2.3 Please be patient, there is a lot to do... 1. Testing gnu tools You must have automake installed to compile ntop. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/automake We recommend version 1.6.3 or higher You must have autoconf installed to compile autogen.sh. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/autoconf We recommend version 2.53 or higher See how the metaauto port works. autoconf and automake are actually scripts that depend on AUTOCONF_VERSION and AUTOMAKE_VERSION to select the right ones. Well in mean time I found this: http://openports.se/devel/metaauto although I don't think it's installed as **find** didn't come up with anything. Does this mean that without the metaauto port that the **system** or **any** install script will not know how to handle a basic compile? Am really confused now as I don't understand anything of what's going on! This might be an easier to answer question then: how do I tell the system to use one particular version of autoconf and automake...??? Which files do I need to edit to do that? Am so sorry for being slow but am just so used to running: cd /usr/ports/*/portname make install clean and everything being done in the background for me! Regards, Kaya
Re: Which automake and autoconfig versions to compile NTOP v4?
On 03/11/2012 08:20 PM, Marc Espie wrote: On Sun, Mar 11, 2012 at 07:42:43PM +, Kaya Saman wrote: Hi, I'm trying to compile the latest NTOP version 4.1.0 on OpenBSD RELEASE 5.0 x64 but am running into issues regarding automake and autoconfig. Basically I installed: automake-1.11.1p2 autoconf-2.67 The install script comes up saying this: # ./autogen.sh Starting ntop automatic configuration system v.0.2.3 Please be patient, there is a lot to do... 1. Testing gnu tools You must have automake installed to compile ntop. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/automake We recommend version 1.6.3 or higher You must have autoconf installed to compile autogen.sh. Download the appropriate package for your distribution, or get the source tarball from ftp://ftp.gnu.org/pub/gnu/autoconf We recommend version 2.53 or higher See how the metaauto port works. autoconf and automake are actually scripts that depend on AUTOCONF_VERSION and AUTOMAKE_VERSION to select the right ones. Well I actually sort-of figured this out but turned out to be a very messy hack and probably have broken other things. meaning am totally not sure of the implications of my actions! I basically moved the autoconf and automake scripts to files called auto*.scr, then symlinked the highest versions of each software to automake and autoconf respectively. i have no idea down-the-line if this will break anything but for now it works :-) Regards, Kaya
Re: Which automake and autoconfig versions to compile NTOP v4?
On Sun, Mar 11, 2012, Kaya Saman wrote: try: automake --version autoconf --version The messages should be self-explanatory if you didn't define certain environment variables, e.g., I have this in my environment: automake --version autoconf --version come up with this # automake --version Provide an AUTOMAKE_VERSION environment variable, please # autoconf --version Provide an AUTOCONF_VERSION environment variable, please How are those messages not self explanatory? Did you read them?
Re: Which automake and autoconfig versions to compile NTOP v4?
On 03/11/2012 10:34 PM, Ted Unangst wrote:
On Sun, Mar 11, 2012, Kaya Saman wrote:
try: automake --version
autoconf --version
The messages should be self-explanatory if you didn't define certain
environment variables, e.g., I have this in my environment:
automake --version
autoconf --version
come up with this
# automake --version
Provide an AUTOMAKE_VERSION environment variable, please
# autoconf --version
Provide an AUTOCONF_VERSION environment variable, please
How are those messages not self explanatory? Did you read them?
Sure I read them it's a bit difficult not to!
I also managed to get round them by providing the versions:
eg. automake-1.11 --version
my issue was how to get the Ntop config script to understand that
automake and autoconf **are** installed on the system!!!
Luckily a friendly person did explain that I should first **export** the
versions then run the config gen script which indeed worked!!!
export AUTOMAKE_VERSION=1.11 AUTOCONF_VERSION=2.67
However, please note that am still learning OpenBSD after coming over
from Linux and FreeBSD and additionally I am NOT a programmer or even
good at programming
My main base in fact is network engineering so forgive me if I don't
know the intricate details of the OpenBSD OS
Using FreeBSD I would just do this:
cd /usr/ports/*/ntop
make install clean
and providing my **ports** tree is uptodate it will work flawlessly.
Additionally on Linux for RPM based would be yum install ntop or DEB
based would be apt-get install ntop
Now I do know these without even needing to read the documentation...
however even **IF** I tried to compile on one of those platforms which I
do all the time I never need to adjust system variables or tell the
configure script what compiler or other I'm using as it is intelligent
enough to autodetect it.
I understand OpenBSD is different and I'm trying to get used to it but
please cut new users some slack as not everyone is God's gift to
computing... {I don't say this as an attack or with any bad
intentions just frustration at how unforgiving this list is sometimes}
Regards,
Kaya
Re: Which automake and autoconfig versions to compile NTOP v4?
On Sun, Mar 11, 2012 at 10:48:24PM +, Kaya Saman wrote:
On 03/11/2012 10:34 PM, Ted Unangst wrote:
On Sun, Mar 11, 2012, Kaya Saman wrote:
try: automake --version
autoconf --version
The messages should be self-explanatory if you didn't define certain
environment variables, e.g., I have this in my environment:
automake --version
autoconf --version
come up with this
# automake --version
Provide an AUTOMAKE_VERSION environment variable, please
# autoconf --version
Provide an AUTOCONF_VERSION environment variable, please
How are those messages not self explanatory? Did you read them?
Sure I read them it's a bit difficult not to!
I also managed to get round them by providing the versions:
eg. automake-1.11 --version
my issue was how to get the Ntop config script to understand that
automake and autoconf **are** installed on the system!!!
Luckily a friendly person did explain that I should first **export** the
versions then run the config gen script which indeed worked!!!
That's what providing the environment variable means.
export AUTOMAKE_VERSION=1.11 AUTOCONF_VERSION=2.67
However, please note that am still learning OpenBSD after coming over
from Linux and FreeBSD and additionally I am NOT a programmer or even
good at programming
One exclamation point is enough.
My main base in fact is network engineering so forgive me if I don't
know the intricate details of the OpenBSD OS
Those are not intricate details. Environment variables exist in virtually every
operating system available.
Using FreeBSD I would just do this:
cd /usr/ports/*/ntop
make install clean
and providing my **ports** tree is uptodate it will work flawlessly.
Additionally on Linux for RPM based would be yum install ntop or DEB
based would be apt-get install ntop
Great story.
Now I do know these without even needing to read the documentation...
however even **IF** I tried to compile on one of those platforms which I
do all the time I never need to adjust system variables or tell the
configure script what compiler or other I'm using as it is intelligent
enough to autodetect it.
The configure script is not part of the operating system, it is part of the
package/tarball, if you're using something that needs automake/autoconf you're
probably checking out development versions of software and then complaining to
the OS developers who have nothing to do with it.
I understand OpenBSD is different and I'm trying to get used to it but
please cut new users some slack as not everyone is God's gift to
computing... {I don't say this as an attack or with any bad
intentions just frustration at how unforgiving this list is sometimes}
I love this list for that.
Regards,
Kaya
Regards
Hektor Oksenberg
Re: Which automake and autoconfig versions to compile NTOP v4?
On 03/12/2012 12:21 AM, hex wrote:
On Sun, Mar 11, 2012 at 10:48:24PM +, Kaya Saman wrote:
On 03/11/2012 10:34 PM, Ted Unangst wrote:
On Sun, Mar 11, 2012, Kaya Saman wrote:
try: automake --version
autoconf --version
The messages should be self-explanatory if you didn't define certain
environment variables, e.g., I have this in my environment:
automake --version
autoconf --version
come up with this
# automake --version
Provide an AUTOMAKE_VERSION environment variable, please
# autoconf --version
Provide an AUTOCONF_VERSION environment variable, please
How are those messages not self explanatory? Did you read them?
Sure I read them it's a bit difficult not to!
I also managed to get round them by providing the versions:
eg. automake-1.11 --version
my issue was how to get the Ntop config script to understand that
automake and autoconf **are** installed on the system!!!
Luckily a friendly person did explain that I should first **export** the
versions then run the config gen script which indeed worked!!!
That's what providing the environment variable means.
I didn't know that so thanks for pointing that out.
export AUTOMAKE_VERSION=1.11 AUTOCONF_VERSION=2.67
However, please note that am still learning OpenBSD after coming over
from Linux and FreeBSD and additionally I am NOT a programmer or even
good at programming
One exclamation point is enough.
Sorry frustration got the better of me!
My main base in fact is network engineering so forgive me if I don't
know the intricate details of the OpenBSD OS
Those are not intricate details. Environment variables exist in virtually every
operating system available.
I do understand that compiling software is part of UNIX and I accept
that I don't know enough about it but the other types of OS's stated all
work without issues which ok is not the OS fault, rather that
software is mostly being designed for Linux and a really great effort to
**port** the stuff is being done by FreeBSD. But without knowing the
characteristics of an OS it's very difficult to debug issues if one
doesn't understand how it handles certain things.
Using FreeBSD I would just do this:
cd /usr/ports/*/ntop
make install clean
and providing my **ports** tree is uptodate it will work flawlessly.
Additionally on Linux for RPM based would be yum install ntop or DEB
based would be apt-get install ntop
Great story.
Uh sorry was just trying to stress or rather emphasize my point. I
think eventually the only thing that got stressed was me :-(
Now I do know these without even needing to read the documentation...
however even **IF** I tried to compile on one of those platforms which I
do all the time I never need to adjust system variables or tell the
configure script what compiler or other I'm using as it is intelligent
enough to autodetect it.
The configure script is not part of the operating system, it is part of the
package/tarball, if you're using something that needs automake/autoconf you're
probably checking out development versions of software and then complaining to
the OS developers who have nothing to do with it.
Erm I wasn't complaining. I just needed a hand to figure out how to
get the script to interact with the OS. Now it's time to take my case to
the Ntop team as the script is blocking me claiming unsupported OS.
True though it maybe I would still like to get Ntop (the current
version) working on OpenBSD as unfortunately it's not available natively.
I understand OpenBSD is different and I'm trying to get used to it but
please cut new users some slack as not everyone is God's gift to
computing... {I don't say this as an attack or with any bad
intentions just frustration at how unforgiving this list is sometimes}
I love this list for that.
Uh! :-(
Would it not just be easier and cleaner to create a new list for
newbies? That way the more advanced stuff could be taken care of on this
list and only people willing to help others could post useful comments
and help on the other list.
.actually this list may become really quiet then??? As in all of my
1 week being here not much help goes on just arguments and flames.
Regards
Hektor Oksenberg
Regards,
--K
