On Thu, Dec 02, 2010 at 10:26:24AM -0500, Peter C. Norton wrote:
> On Thu, Dec 02, 2010 at 09:55:32AM -0500, [email protected] wrote:
> > It's trickier than it might look to do correctly. For example, isql will
> > not report where it looks for its odbc.ini. So the osql script tries to
> > infer that by searching the binary and parsing ldd(1) output. And then
> > there are the usual portability issues, such as the versions of sed(1)
> > and awk(1), and the options they accept. But after 11 tries we seem to
> > be making some progress!
>
> Quick note about the script: if you're on a platform with
> ksh/bash/zsh, can you have autoconf/configure replace #!/bin/sh with
> the more capable shell? On unix variants that have a true bourne
> shell, a lot of things don't work as expected with /bin/sh.
Ah, well, Peter, we're missing one critical resource: a more capable scripter.
Yours truly can stumble through a Bourne shell script but I've never dealt with ksh or zsh. I use bash interactively and try to color inside the lines such that bash invoked as /bin/sh behaves identically to any Bourne shell. So far that's worked OK: the problems we've had with osql were never shell problems per se, but BSD/Linux utility conflicts or unexpected unixODBC arrangements.
--jkl
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.