LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
  Search this Thread
Old 01-18-2005, 12:48 PM   #1
ServerStorm
Member
 
Registered: Oct 2004
Posts: 76

Rep: Reputation: 15
make install-init creating wrong symbolic link


Hi Everyone,

I am compiling a job and I move through the compilation steps up until I run make-install and I run into a No such file or directory error. I believe the error is being generated because the compile process is attempting to set an incorrect symbolic link. Here is the output - items highlighted in green went OK, items in Red did not:

Code:
foozle:~/up-imapproxy-1.2.2 #  ./configure 
checking whether make sets ${MAKE}... yes
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for connect... yes
checking for pthread_create in -lpthread... yes
checking for mmap... yes
checking for yp_get_default_domain in -lnsl... yes
checking for request_init in -lwrap... yes
checking for EVP_DigestInit in -lcrypto... yes
checking for SSL_new in -lssl... yes
checking for initscr in -lcurses... yes
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for unistd.h... (cached) yes
checking sys/mman.h usability... yes
checking sys/mman.h presence... yes
checking for sys/mman.h... yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking for typedef nfds_t... yes
checking for gcc option to accept ANSI C... none needed
checking for an ANSI C-conforming const... yes
checking whether gcc needs -traditional... no
checking return type of signal handlers... void
checking for socket... yes
checking for poll... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: executing default commands
foozle:~/up-imapproxy-1.2.2 # make
gcc   -g -O2 -I. -I./include -c -o src/icc.o src/icc.c
gcc   -g -O2 -I. -I./include -c -o src/main.o src/main.c
gcc   -g -O2 -I. -I./include -c -o src/imapcommon.o src/imapcommon.c
gcc   -g -O2 -I. -I./include -c -o src/request.o src/request.c
gcc   -g -O2 -I. -I./include -c -o src/hash.o src/hash.c
gcc   -g -O2 -I. -I./include -c -o src/becomenonroot.o src/becomenonroot.c
gcc   -g -O2 -I. -I./include -c -o src/config.o src/config.c
gcc   -g -O2 -I. -I./include -c -o src/logging.o src/logging.c
gcc   -g -O2 -I. -I./include -c -o src/select.o src/select.c
gcc -o bin/in.imapproxyd ./src/icc.o ./src/main.o ./src/imapcommon.o ./src/request.o ./src/hash.o ./src/becomenonroot.o ./src/config.o ./src/logging.o ./src/select.o  -lssl -lcrypto -lwrap -lnsl -lpthread
gcc   -g -O2 -I. -I./include -c -o src/pimpstat.o src/pimpstat.c
gcc -o bin/pimpstat ./src/pimpstat.o ./src/config.o -lcurses
foozle:~/up-imapproxy-1.2.2 # make install
/usr/bin/install -c -o bin -g bin -m 0755 ./bin/in.imapproxyd /usr/local/sbin
/usr/bin/install -c -o bin -g bin -m 0755 ./bin/pimpstat /usr/local/sbin
foozle:~/up-imapproxy-1.2.2 #make install-conf
/usr/bin/install -c -o root -g bin -m 0755 ./scripts/imapproxy.conf /etc
foozle:~/up-imapproxy-1.2.2 # make install-init
/usr/bin/install -c -o root -g sys -m 0755 ./scripts/imapproxy.init /etc/init.d/imapproxy
ln -s ../init.d/imapproxy /etc/rc2.d/S99imapproxy
ln: creating symbolic link `/etc/rc2.d/S99imapproxy' to `../init.d/imapproxy': No such file or directory
Note the line in Red: ln -s ../init.d/imapproxy /etc/rc2.d/S99imapproxy

The rc2.d folder and S99imapproxy file are actually located in /etc/init.d/rc2.d/S99imapproxy so somewhere in the ./configure, make, make install-conf, and make install-init scripts this symbolic link is being set. incorrectly.

I went through each script and *.h files in the compile and src directories to see if I could change this but I have been unable to find it.

In addition I attempted to use the most logical ./configure flags so see if it would make a difference and I added the path /etc/init.d to the PATH: environmental variable. Neither of these two attempts helped so I removed the PATH.

Can any of you make a suggestion how I might be able to set this so that the make install-init script writes the correct symbolic link? I have exhausted my novice abilities and would appreciate your help.

Truly,
ServerStorm

Last edited by ServerStorm; 01-18-2005 at 01:02 PM.
 
Old 01-18-2005, 02:32 PM   #2
ServerStorm
Member
 
Registered: Oct 2004
Posts: 76

Original Poster
Rep: Reputation: 15
Hi

It seems I'm either asking dumb questions or I am getting good at solving my dumb questions myself

It was a symbolic link problem. I went through the make file again and I found where it was asking to set the wrong symbolic link (toward the end of the makefile) - sorry that I didn't notice this the first time! I updated the symbolic link to read:
Code:
ln -s ../init.d/imapproxy /etc/init.d/rc2.d/S99imapproxy
	ln -s ../init.d/imapproxy /etc/init.d/rc0.d/K10imapproxy
I added /init.d/ to the path of both symbolic links.

I then deleted all of the files - except the TAR and I ./compiled, make (this is where I changed the links), make install, make install-conf and
make install-init and it worked like a charm!

I hope if someone else has a problem configuring up-immaproxy-1.2.2 on SuSE 9.1 that this will help them get through.

Truly,
ServerStorm
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
cannot make symbolic link dave`2005 Debian 3 10-08-2005 10:15 AM
Is it possible to make a dir a symbolic link? dr_zayus69 Linux - General 4 03-09-2005 08:48 AM
Creating new symbolic link to libstdc kills KDE DavidLock Linux - Newbie 2 05-21-2004 03:31 AM
creating symbolic link for samba woonaks Linux - General 2 10-22-2003 10:12 PM
How to make symbolic link? Tommi Linux - General 9 05-07-2003 08:58 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 03:44 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration