On Mon, Jan 14, 2002 at 02:51:55PM -0800, Richard Whittaker wrote:
> Greetings:
> 
> I'm tryng to compile QPopper 4.0.3 on a Linux machine with SSL, and I'm 
> getting the following error during the compile.. Note there are no warnings 
> or errors up to this point...
> 
> Thoughts, suggestions?... Any help is appreciated!!
> 
> Regards,
> Richard.
> 
> ---
> 
> make[2]: Leaving directory `/usr/src/qpopper4.0.3/common'
> gcc   pop_dele.o pop_dropcopy.o pop_get_command.o pop_get_subcommand.o 
> pop_init.o pop_last.o pop_list.o pop_log.o pop_lower.o pop_msg.o 
> pop_parse.o pop_pass.o pop_quit.o pop_rset.o pop_send.o pop_stat.o 
> pop_updt.o pop_user.o pop_xtnd.o pop_xmit.o popper.o pop_bull.o xtnd_xlst.o 
> pop_uidl.o mktemp.o pop_rpop.o pop_apop.o md5.o pop_auth.o pop_pope.o 
> pop_extend.o scram.o hmac.o base64.o pop_util.o get_sub_opt.o msg_ptr.o 
> drac.o pop_config.o pop_tls.o pop_tls_openssl.o pop_tls_sslplus.o 
> sslplus_utils.o main.o pop_cache.o genpath.o -o popper 
> ../mmangle/libmangle.a \
>         -I../common ../common/libcommon.a \
>         -lcrypt -L/usr/local/ssl//lib -lssl -lcrypto
> ../common/libcommon.a(maillock.o): In function `Qmaillock':
> /usr/src/qpopper4.0.3/common/maillock.c:278: the use of `tempnam' is 
> dangerous, better use `mkstemp'
> /usr/local/ssl//lib/libcrypto.a(dso_dlfcn.o): In function `dlfcn_load':
> dso_dlfcn.o(.text+0xa2): undefined reference to `dlopen'
> dso_dlfcn.o(.text+0xb7): undefined reference to `dlopen'
> dso_dlfcn.o(.text+0x11b): undefined reference to `dlclose'

These link problems are coming from the crypto library on your system,
which has undefined references.  Since all of them seem to refer to
dynamic loader functions (dl prefix) my guess is that you'd need to add
"-ldl" to the list of libraries used in the Makefile.  I'm not much of
a Linux user though, so maybe you want to get a second opinion on this.
  -- Clifton

-- 
 Clifton Royston  --  LavaNet Systems Architect --  [EMAIL PROTECTED]
   WWJD?   "JWRTFM!" - Scott Dorsey (kludge)   "JWG" - Eddie Aikau

Reply via email to