FreeTDS Development Group

[GUTIERREZ Pablo TESIS-TAMSA <Tesgup AT tamsa.com.mx>]

QNX 4.25 comes only with Korn shell.
The Bash shell that I used to build free-tds is also a port, since there is
no BASH shell native to QNX.
99.9% of QNX 4.25 users have only the native Korn Shell.
That's why I think that a ./configure that runs in the Korn Shell is the
proper method to target QNX users.

-----Original Message-----
From: GUTIERREZ Pablo TESIS-TAMSA [mailto:Tesgup AT tamsa.com.mx] 
Sent: Monday, April 14, 2003 11:36 AM
To: 'FreeTDS Development Group'
Subject: RE: [freetds] FREE-TDS 0.61 on QNX 4.25

When I said:
"If someone have QNX 4.25 and is willing to produce a ./configure that
runs..."

I meant:

"If someone is willing to write a configure.in"

I think it is possible to generate a ./configure that runs in QNX's Korn
Shell with little effort.

-----Original Message-----
From: Lowden, James K [mailto:LowdenJK AT bernstein.com] 
Sent: Monday, April 14, 2003 11:30 AM
To: 'FreeTDS Development Group'
Subject: RE: [freetds] FREE-TDS 0.61 on QNX 4.25

> From: GUTIERREZ Pablo TESIS-TAMSA [mailto:Tesgup AT tamsa.com.mx]
> Sent: April 14, 2003 11:38 AM
> 
> If you run ./configure under native QNX's Korn Shell it prints lots of
> errors and configuration data in files (such as max_cmd_len 
> in ./libtool or ./include/configure.h) is wrong or empty. 

A simpler explanation is that configure is a Bourne shell script.  It should
be expected to work when processed by a Bourne shell interpreter.  It should
not be expected to work when processed by any other interpreter, be it Korn,
Perl, Python, csh, etc.  The mere fact that Bourne and Korn are both shells
doesn't make them interchangeable, or even more than minimally similar.  

> If someone have QNX 4.25 and is willing to produce a 
> ./configure that runs
> in QNX's Korn shell please get in touch with me to work together.

The configure script is generated by GNU autoconf, which targets Bourne
shell syntax.  It changes as the project changes, and as autoconf changes.
Hacking it is pointless.  

Bash does a fairly good job of being Bourne compatible, and compatibility is
one of the project's expressed goals.  Many Linux distributions, notably
Debian IIRC, ship only Bash and rely on its Bourne-compatible behavior when
invoked as "sh".  Unless the QNX Korn shell has similar aspirations, you're
much better off using Bash to run configure.  

--jkl



The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above.  If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that we do not accept account orders and/or
instructions by e-mail, and therefore will not be responsible for carrying
out such orders and/or instructions.


_______________________________________________
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