Bash Errors -- NetMeeting Directory Setup

Where Penguins and Daemons chill together in the warmth of the Sun.

Moderators: SecretSquirrel, notfred

Bash Errors -- NetMeeting Directory Setup

Postposted on Sat Apr 05, 2008 2:15 pm

I recently started renting a VPS running Debian 4. I have used linux before to set up a variety of things, and my knowledge still seems pretty limited to me because of the amounts of time in between linux usage.

I'm trying to set up a NetMeeting directory. I am running along with this guide here and have run into an error that is extremely confusing. I've googled a variety of things trying to solve this, but have come up empty handed.

I am on step 3.5 of the guide, the second gray box. I've gotten everything to come out OK up until this point. Here is what happens:

wtf148:~# bash make
/usr/bin/make: /usr/bin/make: cannot execute binary file
wtf148:~# bash make install
/usr/bin/make: /usr/bin/make: cannot execute binary file


Any suggestions?
Image
bro_c
Gerbil
 
Posts: 67
Joined: Sat Feb 19, 2005 4:37 pm
Location: WI

Re: Bash Errors -- NetMeeting Directory Setup

Postposted on Sat Apr 05, 2008 2:43 pm

The 'bash' is the command prompt in the example commands from the guide. Don't type the 'bash' part. IOW, just type 'make' and 'make install'.
(this space intentionally left blank)
just brew it!
Administrator
Gold subscriber
 
 
Posts: 37859
Joined: Tue Aug 20, 2002 10:51 pm
Location: Somewhere, having a beer

Re: Bash Errors -- NetMeeting Directory Setup

Postposted on Sat Apr 05, 2008 3:53 pm

I have been working on this installation with Bro_c, and i tried to run those commands before without the bash and i got errors there too. I found that i needed to be in the openldap-2.0.7 directory for the
Code: Select all
./configure --enable-shell --disable-debug
command to run. But when I try to run make in the same directory I get this.
Code: Select all
wtf148:~/openldap-2.0.7# make
make: *** No targets specified and no makefile found.  Stop.


Here is what we have in that directory.
Code: Select all
wtf148:~/openldap-2.0.7# ls
ANNOUNCEMENT  LICENSE      acinclude.m4  confdefs.h    contrib    servers
CHANGES       Makefile.in  aclocal.m4    config.log    doc        tests
COPYRIGHT     README       build         configure     include
INSTALL       acconfig.h   clients       configure.in  libraries


Do i need to be in a different directory or specify a file for the make command?
Little_c
Gerbil In Training
 
Posts: 3
Joined: Sat Apr 05, 2008 3:43 pm

Re: Bash Errors -- NetMeeting Directory Setup

Postposted on Sat Apr 05, 2008 7:21 pm

You need to be in the directory for all the commands. It looks like the ./configure may have failed as it should have taken the Makefile.in file and converted it to a Makefile file. Can you post the output of the ./configure (just the last bit if it is huge)?
notfred
Grand Gerbil Poohbah
 
Posts: 3750
Joined: Tue Aug 10, 2004 10:10 am
Location: Ottawa, Canada

Re: Bash Errors -- NetMeeting Directory Setup

Postposted on Sun Apr 06, 2008 10:20 am

Code: Select all
wtf148:~/openldap-2.0.7# ./configure --enable-shell -disable-debug
Copyright 1998-2000 The OpenLDAP Foundation,  All Rights Reserved.
Restrictions apply, see COPYRIGHT and LICENSE files.
Configuring OpenLDAP 2.0.7-Release ...
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for mawk... no
checking for gawk... gawk
checking whether make sets ${MAKE}... yes
checking for working aclocal... missing
checking for working autoconf... missing
checking for working automake... missing
checking for working autoheader... missing
checking for working makeinfo... missing
checking for gnutar... no
checking for gtar... no
checking for tar... tar
checking configure arguments... done
checking for cc... no
checking for ranlib... ranlib
checking for gcc... no
checking for cc... no
configure: error: no acceptable cc found in $PATH
Little_c
Gerbil In Training
 
Posts: 3
Joined: Sat Apr 05, 2008 3:43 pm

Re: Bash Errors -- NetMeeting Directory Setup

Postposted on Sun Apr 06, 2008 10:59 am

I think you need to install the build-essential package (at least that is what it is called in Ubuntu, I assume it is the same in Debian).
(this space intentionally left blank)
just brew it!
Administrator
Gold subscriber
 
 
Posts: 37859
Joined: Tue Aug 20, 2002 10:51 pm
Location: Somewhere, having a beer

Re: Bash Errors -- NetMeeting Directory Setup

Postposted on Sun Apr 06, 2008 11:09 am

Installed it, tried it again. Same errors. :(
Image
bro_c
Gerbil
 
Posts: 67
Joined: Sat Feb 19, 2005 4:37 pm
Location: WI

Re: Bash Errors -- NetMeeting Directory Setup

Postposted on Sun Apr 06, 2008 11:16 am

bro_c wrote:Installed it, tried it again. Same errors. :(

You still get the "no acceptable cc" error?

Try typing the commands which cc, and also which gcc and see what it says.
(this space intentionally left blank)
just brew it!
Administrator
Gold subscriber
 
 
Posts: 37859
Joined: Tue Aug 20, 2002 10:51 pm
Location: Somewhere, having a beer

Re: Bash Errors -- NetMeeting Directory Setup

Postposted on Sun Apr 06, 2008 11:24 am

Alright, we put installed the build essential package. Not then we run the ./configure command we get.
Code: Select all
wtf148:~/openldap-2.0.7# ./configure --enable-shell --disable-debug
Copyright 1998-2000 The OpenLDAP Foundation,  All Rights Reserved.
Restrictions apply, see COPYRIGHT and LICENSE files.
Configuring OpenLDAP 2.0.7-Release ...
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for mawk... no
checking for gawk... gawk
checking whether make sets ${MAKE}... yes
checking for working aclocal... missing
checking for working autoconf... missing
checking for working automake... missing
checking for working autoheader... missing
checking for working makeinfo... missing
checking for gnutar... no
checking for gtar... no
checking for tar... tar
checking configure arguments... done
checking for cc... cc
checking for ranlib... ranlib
checking for gcc... (cached) cc
checking whether the C compiler (cc   ) works... yes
checking whether the C compiler (cc   ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether cc accepts -g... yes
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking for object suffix... o
checking for executable suffix... no
checking for cc option to produce PIC... -fPIC
checking if cc PIC flag -fPIC works... yes
checking if cc supports -c -o file.o... yes
checking if cc supports -c -o file.lo... yes
checking if cc supports -fno-rtti -fno-exceptions ... no
checking if cc static flag -static works... -static
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the linker (/usr/bin/ld) supports shared libraries... yes
checking command to parse /usr/bin/nm -B output... ok
checking how to hardcode library paths into programs... immediate
checking for /usr/bin/ld option to reload object files... -r
checking dynamic linker characteristics... Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for objdir... .libs
checking for dlopen in -ldl... yes
checking for dlfcn.h... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... no
creating libtool
not updating unwritable cache ./config.cache
checking for mawk... (cached) gawk
checking whether ln works... yes
checking whether ln -s works... (cached) yes
checking for sendmail... /usr/sbin/sendmail
checking for vi... /usr/bin/vi
checking for finger... /usr/bin/finger
checking how to run the C preprocessor... cc -E
checking for AIX... no
checking for POSIXized ISC... no
checking for minix/config.h... no
checking for Cygwin environment... no
checking for mingw32 environment... no
checking for EMX OS/2 environment... no
checking for executable suffix... no
checking for object suffix... o
checking for be_app in -lbe... no
checking for cc option to accept ANSI C... none needed
checking for cc depend flag... -M
checking for afopen in -ls... no
checking for EBCDIC... no
checking for ANSI C header files... yes
checking for dirent.h that defines DIR... yes
checking for opendir in -ldir... no
checking for sys/wait.h that is POSIX.1 compatible... yes
checking POSIX termios... yes
checking whether use of TIOCGWINSZ requires sys/ioctl.h... yes
checking for arpa/inet.h... yes
checking for arpa/nameser.h... yes
checking for assert.h... yes
checking for conio.h... no
checking for crypt.h... yes
checking for direct.h... no
checking for errno.h... yes
checking for fcntl.h... yes
checking for filio.h... no
checking for getopt.h... yes
checking for grp.h... yes
checking for io.h... no
checking for libutil.h... no
checking for limits.h... yes
checking for locale.h... yes
checking for netinet/tcp.h... yes
checking for malloc.h... yes
checking for memory.h... yes
checking for psap.h... no
checking for pwd.h... yes
checking for process.h... no
checking for resolv.h... yes
checking for sgtty.h... yes
checking for shadow.h... yes
checking for stddef.h... yes
checking for string.h... yes
checking for strings.h... yes
checking for sysexits.h... yes
checking for sys/file.h... yes
checking for sys/filio.h... no
checking for sys/errno.h... yes
checking for sys/ioctl.h... yes
checking for sys/param.h... yes
checking for sys/resource.h... yes
checking for sys/select.h... yes
checking for sys/socket.h... yes
checking for sys/syslog.h... yes
checking for sys/time.h... yes
checking for sys/types.h... yes
checking for syslog.h... yes
checking for termios.h... yes
checking for unistd.h... yes
checking for winsock.h... no
checking for sigset in -lV3... no
checking for socket... yes
checking for select... yes
checking types of arguments for select()... int,fd_set *,struct timeval *
checking for regex.h... yes
checking for regfree... yes
checking for compatible POSIX regex... yes
checking for res_query... no
checking for res_query in -lbind... no
checking for __res_query in -lbind... no
checking for res_query in -lresolv... yes
checking for getaddrinfo... yes
checking for gai_strerror... yes
checking INET6_ADDRSTRLEN... yes
checking for sys/un.h... yes
checking for openssl/ssl.h... no
checking for ssl.h... no
configure: warning: Could not locate TLS/SSL package
configure: warning: TLS privacy protection not supported!
checking for ctime_r... yes
checking for gethostbyname_r... yes
checking for gethostbyaddr_r... yes
checking number of arguments of ctime_r... 2
checking number of arguments of gethostbyname_r... 6
checking number of arguments of gethostbyaddr_r... 8
checking for NT Threads... checking for _beginthread... no
no
checking for pthread.h... yes
checking POSIX thread version... final
checking for LinuxThreads pthread.h... yes
checking for GNU Pth pthread.h... no
checking for sched.h... yes
checking for pthread_create in default libraries... no
checking for pthread link with -kthread... no
checking for pthread link with -pthread... yes
checking for sched_yield... yes
checking for pthread_yield... yes
checking for pthread_kill... yes
checking for pthread_rwlock_destroy... yes
checking for pthread_detach with <pthread.h>... yes
checking for pthread_setconcurrency... yes
checking for pthread_getconcurrency... yes
checking for thr_setconcurrency... no
checking for thr_getconcurrency... no
checking for pthread_kill_other_threads_np... yes
checking for LinuxThreads implementation... yes
checking for LinuxThreads consistency... yes
checking if pthread_create() works... yes
checking if select yields when using pthreads... yes
checking for thread specific errno... yes
checking for thread specific h_errno... yes
checking for db.h... no
checking for MDBM library... checking for mdbm_set_chain... no
checking for mdbm_set_chain in -lmdbm... no
no
checking for mdbm.h... no
checking for db... no
checking for GDBM library... checking for gdbm_open... no
checking for gdbm_open in -lgdbm... no
no
checking for gdbm.h... no
checking for db... no
configure: warning: could not find suitable LDBM backend
configure: error: select appropriate LDBM options or disable


And now when we run the make command we get.

Code: Select all
wtf148:~/openldap-2.0.7# make
make: *** No targets specified and no makefile found.  Stop.
wtf148:~/openldap-2.0.7# make install
make: *** No rule to make target `install'.  Stop.



And in reply to you latest post we get.
Code: Select all
wtf148:~/openldap-2.0.7# which cc
/usr/bin/cc
wtf148:~/openldap-2.0.7# which gcc
/usr/bin/gcc
Little_c
Gerbil In Training
 
Posts: 3
Joined: Sat Apr 05, 2008 3:43 pm

Re: Bash Errors -- NetMeeting Directory Setup

Postposted on Sun Apr 06, 2008 12:09 pm

My real question is why are you building and installing OpenLDAP 2.0.7 from source (which was released in 2000! and is really, really old) when you could just apt-get install the slapd and ldap-utils packages giving you up-to-date binary versions? The prebuilt packages are generally configured with the widest range of possible options, and the the Debian/Ubuntu package has the shell backend enabled as a module. If you really must build it yourself, I'd do it from the deb source package. I skimmed the guide and didn't see any real reason why you need to use a really old version of OpenLDAP and why it must be built from source.

There are a lot of Linux resources out there on the Internet that'll tell you to build stuff from source, but really that's because it's the lowest common denominator procedure that works on all Linux distros. It is almost always the hardest and least maintainable way to install software, though. Also, this guide seems to be quite old and telling you to install a version from eight years ago. You should use distro software packages when possible.

Little_c wrote:And now when we run the make command we get.

Code: Select all
wtf148:~/openldap-2.0.7# make
make: *** No targets specified and no makefile found.  Stop.
wtf148:~/openldap-2.0.7# make install
make: *** No rule to make target `install'.  Stop.

Again, configure generates the Makefile only when it runs successfully. It exited with an error, so it won't have generated the Makefile. The error was:
Code: Select all
configure: error: select appropriate LDBM options or disable

apt-get install libgdbm-dev should add the LDBM dependency. I have a feeling after that is installed you will come across a variety of other library dependencies and you'll have to install them as well. apt-get build-dep slapd will give you all of the dependencies for building the Debian OpenLDAP package in one shot. I'd just use the binary package.
bitvector
Grand Gerbil Poohbah
 
Posts: 3234
Joined: Wed Jun 22, 2005 4:39 pm
Location: Mountain View, CA

Re: Bash Errors -- NetMeeting Directory Setup

Postposted on Sun Apr 06, 2008 12:20 pm

bitvector wrote:My real question is why are you building and installing OpenLDAP 2.0.7 from source (which was released in 2000! and is really, really old)


Hmm, wasn't aware that there was a pre-built package, otherwise of course I wouldn't be messing around with all of this.

Code: Select all
apt-get build-dep slapd
is all I need for the pre-built package?
Image
bro_c
Gerbil
 
Posts: 67
Joined: Sat Feb 19, 2005 4:37 pm
Location: WI

Re: Bash Errors -- NetMeeting Directory Setup

Postposted on Sun Apr 06, 2008 1:02 pm

bro_c wrote:
bitvector wrote:My real question is why are you building and installing OpenLDAP 2.0.7 from source (which was released in 2000! and is really, really old)

Hmm, wasn't aware that there was a pre-built package, otherwise of course I wouldn't be messing around with all of this.
Code: Select all
apt-get build-dep slapd
is all I need for the pre-built package?

No, that gives you the packages needed to build the package (build dependencies -- extra development libraries and such). Apt-get install installs a package. As I said earlier, "you could just apt-get install the slapd and ldap-utils packages." OpenLDAP is broken into several separate packages so you can install the parts you need (e.g. LDAP utilities without the LDAP server, etc.). slapd is the server and ldap-utils are the client utilities. If you want everything (and you might as well install it all):
apt-get install slapd ldap-utils libldap2 libldap2-dev
bitvector
Grand Gerbil Poohbah
 
Posts: 3234
Joined: Wed Jun 22, 2005 4:39 pm
Location: Mountain View, CA

Re: Bash Errors -- NetMeeting Directory Setup

Postposted on Sun Apr 06, 2008 1:04 pm

bro_c wrote:
bitvector wrote:My real question is why are you building and installing OpenLDAP 2.0.7 from source (which was released in 2000! and is really, really old)

Hmm, wasn't aware that there was a pre-built package, otherwise of course I wouldn't be messing around with all of this.

Code: Select all
apt-get build-dep slapd
is all I need for the pre-built package?

Actually, that (supposedly) gets you what you need to build it successfully. To install the prebuilt binaries I believe you would want to do apt-get install slapd and apt-get install ldap-utils.

Being somewhat new to Ubuntu/Debian myself (and completely clueless about LDAP), I didn't pick up on the fact that you were trying to build an 8-year-old version of a package which has a current binary version available in the repositories. My bad... I should've probably looked into that sooner instead of diving in to helping you fix something that didn't need to be fixed!

In general, it is a good idea to always check whether your distro provides a pre-built package, before attempting to build something from scratch.

(And thanks bitvector, for pointing out that we were going down the wrong path...)

Edit: And it looks like he beat me to it on this post as well...
(this space intentionally left blank)
just brew it!
Administrator
Gold subscriber
 
 
Posts: 37859
Joined: Tue Aug 20, 2002 10:51 pm
Location: Somewhere, having a beer

Re: Bash Errors -- NetMeeting Directory Setup

Postposted on Sun Apr 06, 2008 2:44 pm

Thanks for the help, guys. I was using that guide because I was completely clueless on setting up an online NetMeeting directory, and that was the only set of directions I had come across.
Many thanks!

For anyone stumbling on this, one error I did have trying to install the perl script was with make. I had to
Code: Select all
o conf make /usr/bin/make
in order to get the script installed.

Edit: I'm having a little bit of confusion with setting up the directory. The NetMeeting directory kit is found on the same website that the guide is hosted on, but as we know the guide is very outdated.

Copy netmeeting.perl to the /usr/local/libexec directory, netmeeting.schema to the /usr/local/etc/openldap/schema directory, and copy both slapd.conf and slapd2.conf to the /usr/local/etc/openldap directory. Create the directory /usr/local/var/openldap-netmeeting to store the LDAP database, and make it world writable.


Since we no longer have to build the source ourselves, the folders are off. I'm not attuned enough with linux to find whichever folder is the equivalent of the outdated folders described in the guide.
Again, I'm trying to configure an LDAP server for NetMeeting clients using the ndk-1.1 NetMeeting kit.

I'm hoping TR can provide just a little more linux guidance.
Image
bro_c
Gerbil
 
Posts: 67
Joined: Sat Feb 19, 2005 4:37 pm
Location: WI

Re: Bash Errors -- NetMeeting Directory Setup

Postposted on Sun Apr 06, 2008 11:04 pm

Since I'm rather unsure how to configure the NetMeeting kit with the pre-built packages, I've decided to just continue on using the guide, after installing the dependencies posted earlier.

I've worked my way along the guide and am not familiar with what it wants me to do here:
You now have to initialize the slave database with a single entry. This is only done once, by running the initialize script included in the kit. The "rootdn" and "rootpw" entries are in the slave config file to allow access for the initialization script, and must match the -D and -w options in the script. Once you've initialized the database with a single parent entry, you can comment out the "rootdn" and "rootpw" lines from slapd2.conf, though this is not critical.


So all I type to run the script is

Code: Select all
. initialize
correct?

Here is what I get after I run that:
Code: Select all
wtf148:~/ndk-1.1# . initialize
adding new entry "objectclass=rtperson"
Image
bro_c
Gerbil
 
Posts: 67
Joined: Sat Feb 19, 2005 4:37 pm
Location: WI

Re: Bash Errors -- NetMeeting Directory Setup

Postposted on Mon Apr 07, 2008 5:14 pm

I basically need to know how to run scripts.
Image
bro_c
Gerbil
 
Posts: 67
Joined: Sat Feb 19, 2005 4:37 pm
Location: WI

Re: Bash Errors -- NetMeeting Directory Setup

Postposted on Mon Apr 07, 2008 8:21 pm

bro_c wrote:
Copy netmeeting.perl to the /usr/local/libexec directory, netmeeting.schema to the /usr/local/etc/openldap/schema directory, and copy both slapd.conf and slapd2.conf to the /usr/local/etc/openldap directory. Create the directory /usr/local/var/openldap-netmeeting to store the LDAP database, and make it world writable.


Since we no longer have to build the source ourselves, the folders are off. I'm not attuned enough with linux to find whichever folder is the equivalent of the outdated folders described in the guide.

Debian's slapd package puts slapd config files in the /etc/ldap directory. Schemas go in /etc/ldap/schema and default LDAP databases go in /var/lib/slapd. Making the LDAP directory database world writable seems like a bad idea, though. It should only need to be writable by the uid/gid that the slapd daemon is running as.

bro_c wrote:So all I type to run the script is

Code: Select all
. initialize

correct?

No, that sources a script (a period followed by a space followed by the script name), which isn't exactly the same. "sh initialize" or "./initialize" (if the script is marked executable) will run it normally.
bitvector
Grand Gerbil Poohbah
 
Posts: 3234
Joined: Wed Jun 22, 2005 4:39 pm
Location: Mountain View, CA

Re: Bash Errors -- NetMeeting Directory Setup

Postposted on Mon Apr 07, 2008 8:32 pm

Just be sure that whenever you go to install *anything*, check for a version in apt first. The versions in apt are pre-tested and pre-configured to work with the other things in apt, they get reviewed and patched for security, and will get updated when needed.

Building things from source is both complicated and a very big potential security problem. Package managers do the work for you, don't fight them.

apt-cache search somepackage will find anything named somepackage for you. apt-get install somepackage will install same.

apt-get update to update the available lists of packages

apt-get upgrade to upgrade all installed packages which can be updated without breaking anything

apt-get dist-upgrade to upgrade *everything*, attempting to automagically add dependencies and possibly break stuff (needed rarely).


Really, all this stuff is in the manual and docs. I don't want to yell 'RTFM!' and leave you high and dry, but something like 'Debian for newbies' is out there and would help you help yourself.

That said, continue bravely trampling on. You're learning and it's painful, but in the end you can yell 'did it myself!'.
Siglessness is boring.
Image - M4800-Eight1
Image - Vargr-Z97
Forge
Lord High Gerbil
 
Posts: 8047
Joined: Wed Dec 26, 2001 7:00 pm
Location: SouthEast PA

Re: Bash Errors -- NetMeeting Directory Setup

Postposted on Mon Apr 07, 2008 9:54 pm

The NetMeeting guide has use of a Perl script to handle NetMeeting client requests. Would this still be needed with the pre-built packages?

Basically, I'm left wondering if the NetMeeting Directory Kit would still work with these pre-built packages, if all the files were applied correctly, in the same fashion as if I had built from the source.
Image
bro_c
Gerbil
 
Posts: 67
Joined: Sat Feb 19, 2005 4:37 pm
Location: WI

Re: Bash Errors -- NetMeeting Directory Setup

Postposted on Tue Apr 08, 2008 8:28 am

bro_c wrote:The NetMeeting guide has use of a Perl script to handle NetMeeting client requests. Would this still be needed with the pre-built packages?

Basically, I'm left wondering if the NetMeeting Directory Kit would still work with these pre-built packages, if all the files were applied correctly, in the same fashion as if I had built from the source.

You should be able to use the Perl script regardless of how you've installed the package.
The best things in life are free.
http://www.gentoo.org
Guy 1: Surely, you will fold with me.
Guy 2: Alright, but don't call me Shirley.
titan
Grand Gerbil Poohbah
 
Posts: 3276
Joined: Mon Feb 18, 2002 7:00 pm
Location: Great Smoky Mountains


Return to Linux, Unix, and Assorted Madness

Who is online

Users browsing this forum: No registered users and 2 guests