FreeTDS Development Group

[Todd Szymanski <gator AT szymanski.net>]

I went back to the build environment.  The two install binaries on
Solairs /usr/sbin/install and /usr/ucb/install seem to be consider
incompatible in the configure source and are excluded.  That leaves
the install-sh, which the one that is included in the distribution is
old, so it fails.

However, I copied the /usr/ucb/install on Solaris over to
/usr/bin/install and reran the configure, which then picked it up.
After it decided to use the install binary I copied everything worked.

So either the install-sh needs to get upgraded or the configure script
shouldn't exclude /usr/ucb/install on Solaris.

On Sat, Sep 3, 2011 at 10:55 AM, Mike Slifcak <slif AT bellsouth.net> wrote:
> autogen driving autoconf/automake is viable.  I know that Net-SNMP uses 
> autoconf on
> Solaris with no issues.
> -Mike Slifcak
>
> James K. Lowden wrote:
>> On Wed, 31 Aug 2011 14:41:25 -0400
>> Todd Szymanski <toddzman AT gmail.com> wrote:
>>
>>> Just wanted to pass along that I was unable to successfully do a 'make
>>> install' on 0.9.1.  It seems like it worked, but it doesn't when you
>>> go to use it.  It looks like the install-sh that is included in the
>>> distribution does not handle multiple files on one command line (I've
>>> only tried it on Solaris).
>>
>> Your experience isn't typical, to say the least.  I wonder: does
>> Solaris have an install(1) on the PATH?
>>
>> $ file $(which install)
>> /usr/bin/install: ELF 64-bit LSB executable, x86-64 ....
>>
>> It seems you *did* find a bug, albeit one masked on machines with a
>> built-in install utility.  The FreeTDS distribution tarball includes
>> an install script, but configuration.ac -- from which the configure
>> script is generated by autoconf -- does not reference it as
>> AC_PROG_INSTALL.  I would think configure, finding no built-in install
>> utility and having not been directed to use another, would simply
>> fail.  Apparently, it uses the one it finds in the current working
>> directory, if extant.  And fails silently.  :-/
>>
>> I'm inclined to simply remove install-sh from the FreeTDS
>> distribution.  In 2011, machines without an install utility must be
>> very rare, and a message like "sh: install: command not found" would be
>> better than pretending to work.
>>
>> That leaves it to the sysadmin to provide an install utility.  The
>> alternatives I don't like as well.  If we force configure to use a
>> shell script, installation speed suffers.  If we don't, but include
>> a shell script as a last resort, it will be used infrequently,
>> and likely not work when called upon.
>>
>> --jkl
>> _______________________________________________
>> FreeTDS mailing list
>> FreeTDS AT lists.ibiblio.org
>> http://lists.ibiblio.org/mailman/listinfo/freetds
>>
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds
>