Re: Can't make SQSH 2.1.7 with freetds 0.91

Casey Boardman <[email protected]>
Newsgroups gmane.comp.db.tds.freetds
Message-ID <833E9AA56926514AB3B3A4DA29913556401CDF9C@bfm-exchange2.batterymarch.com>
"You could say it's a sqsh error.  You could also blame Solaris or autoconf.  But the solution will probably come from you."

Well said, sir.  Well said.


Solution:  When editing src/Makefile, I got rid of -ltds (as suggested here) and changed -ldl to -liconv.  I got that last bit from the cygwin version of the sqsh README.  I used SYBASE=/usr/local/freetds/.

After that I had to set the LD_LIBRARY_PATH=$SYBASE/lib/:/usr/local/lib/ to get the freetds and liconv libraries.

Sqsh now runs.  (Though I haven't done any actual connections yet).  

Thanks for all the help.

-Casey


-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of [email protected]
Sent: Wednesday, September 21, 2011 14:14
To: FreeTDS Development Group
Subject: Re: [freetds] Can't make SQSH 2.1.7 with freetds 0.91

On Wed, Sep 21, 2011 at 12:50:18PM -0400, Casey Boardman wrote:
> No dice so far.  Here are the end results of make with SYBASE set to the two different values.  This does affect the SYBASE_LIBS in the Makefile.
> 
> Should I reinstall the package to the /usr/local/ vs /usr/local/freetds/?  
> Is this a sqsh error at this point?

You could say it's a sqsh error.  You could also blame Solaris or autoconf.  
But the solution will probably come from you.  

> With 
> - environment: SYBASE=/usr/local/freetds 
> - Makefile (edited by me): SYBASE_LIBS   =    -lct    -lnsl -ldl -lm
> 
> gcc    -L/usr/local/freetds/lib -L/usr/local/lib cmd_alias.o cmd_bcp.o cmd_buf.o cmd_connect.o cmd_do.o cmd_echo.o cmd_exit.o cmd_for.o cmd_func.o cmd_go.o cmd_help.o cmd_history.o cmd_if.o cmd_input.o cmd_jobs.o cmd_kill.o cmd_lock.o cmd_loop.o cmd_misc.o cmd_read.o cmd_reconnect.o cmd_redraw.o cmd_reset.o cmd_return.o cmd_rpc.o cmd_set.o cmd_shell.o cmd_show.o cmd_sleep.o cmd_wait.o cmd_warranty.o cmd_while.o var_ctlib.o var_date.o var_debug.o var_dsp.o var_hist.o var_misc.o var_passwd.o var_readline.o var_thresh.o dsp.o dsp_bcp.o dsp_csv.o dsp_conv.o dsp_desc.o dsp_horiz.o dsp_html.o dsp_meta.o dsp_none.o dsp_out.o dsp_pretty.o dsp_vert.o dsp_x.o sqsh_alias.o sqsh_args.o sqsh_avl.o sqsh_buf.o sqsh_cmd.o sqsh_compat.o sqsh_ctx.o sqsh_debug.o sqsh_env.o sqsh_error.o sqsh_expand.o sqsh_f
 d.o sqsh_filter.o sqsh_fork.o sqsh_func.o sqsh_getopt.o sqsh_global.o sqsh_history.o sqsh_init.o sqsh_job.o sqsh_readline.o sqsh_sig.o sqsh_sigcld.o sqsh_stdin.o sqsh_strchr.o sqsh_tok.o sqs
 h_
>  varbuf.o sqsh_main.o -lct    -lnsl -ldl -lm   -lreadline -lcurses  -o sqsh
> ld: warning: global symbol `_END_' has non-global binding:
>         (file /usr/local/freetds/lib/libct.so value=LOCL);
> ld: warning: global symbol `_START_' has non-global binding:
>         (file /usr/local/freetds/lib/libct.so value=LOCL);
> Undefined                       first referenced
>  symbol                             in file
> libiconv_close                      /usr/local/freetds/lib/libct.so
> libiconv_open                       /usr/local/freetds/lib/libct.so
> libiconv                            /usr/local/freetds/lib/libct.so

Did you configure FreeTDS using --disable-libiconv?  If not, you need to supply 
the sqsh link command with the name of the iconv library.  Most operating 
systems these days include that function with their standard C library, but 
apparently Solaris isn't one of them.  


HTH.  

--jkl
_______________________________________________
FreeTDS mailing list
[email protected]
http://lists.ibiblio.org/mailman/listinfo/freetds

This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.