Michael Carmack writes: > You've hit it! Yes, I compiled and installed this myself, and bin/imapd > IS a symlink to the imapd startup script. I've posted the complete build > log to: > > http://karmak.org/2002/01/courier/i686-pc-linux-gnu.1.log > > It's big (~1MB), but it's all there, from 'configure' to 'make install'. > Commands I've issued are prefixed with "@@" to find them easily, and > the very beginning of the log shows the environment variables that are > set. > > If you do a search for "bin/imapd", you'll notice that during the > installation the following two commands are run (this appears ~90% into > the log): > > rm -f /pkg/courier/0.36.1/.i686-pc-linux-gnu/.karmak-standard.1/bin/imapd > ln -s /pkg/courier/0.36.1/.i686-pc-linux-gnu/.karmak-standard.1/share/imapd >/pkg/courier/0.36.1/.i686-pc-linux-gnu/.karmak-standard.1/bin/imapd > > It would appear that the original bin/imapd gets deliberately removed > during 'make install', and replaced by a symlink to the imapd startup > script.
This is because your install is completely broken because you manually specified the same bindir and sbindir directories. > Glad you spotted this. I'm digging into the problem right now, but I The problem is that you specified non-default installation directories without fully understanding how they work. -- Sam _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
