Re: After upgrade autoconf from 1.13 to 2.57, I experienced some problems - HELP

2006-12-07 Thread Thomas Dickey
On Thu, 7 Dec 2006, Andreas Schwab wrote: Thomas Dickey <[EMAIL PROTECTED]> writes: On Thu, 7 Dec 2006, Andreas Schwab wrote: Thomas Dickey <[EMAIL PROTECTED]> writes: In contrast, I can plug current ncurses libraries into a system that's built with ncurses 5.0, and just assume it'll work.

Re: After upgrade autoconf from 1.13 to 2.57, I experienced some problems - HELP

2006-12-07 Thread Andreas Schwab
Thomas Dickey <[EMAIL PROTECTED]> writes: > On Thu, 7 Dec 2006, Andreas Schwab wrote: > >> Thomas Dickey <[EMAIL PROTECTED]> writes: >>> In contrast, I can plug current ncurses libraries into a system that's >>> built with ncurses 5.0, and just assume it'll work. That's from 1999. >> >> That's no

Re: After upgrade autoconf from 1.13 to 2.57, I experienced some problems - HELP

2006-12-06 Thread Thomas Dickey
On Thu, 7 Dec 2006, Andreas Schwab wrote: Thomas Dickey <[EMAIL PROTECTED]> writes: In contrast, I can plug current ncurses libraries into a system that's built with ncurses 5.0, and just assume it'll work. That's from 1999. That's not a useful comparison. How many new features have been ad

Re: After upgrade autoconf from 1.13 to 2.57, I experienced some problems - HELP

2006-12-06 Thread Andreas Schwab
Thomas Dickey <[EMAIL PROTECTED]> writes: > On Wed, 6 Dec 2006, Ralf Wildenhues wrote: > >> * Thomas Dickey wrote on Wed, Dec 06, 2006 at 09:15:12PM CET: >>> On Wed, 6 Dec 2006, Ralf Wildenhues wrote: >>> 2.57 was released six years ago. I don't think you can expect much help >>> >>> four ye

Re: After upgrade autoconf from 1.13 to 2.57, I experienced some problems - HELP

2006-12-06 Thread Thomas Dickey
On Wed, 6 Dec 2006, Ralf Wildenhues wrote: * Thomas Dickey wrote on Wed, Dec 06, 2006 at 09:15:12PM CET: On Wed, 6 Dec 2006, Ralf Wildenhues wrote: 2.57 was released six years ago. I don't think you can expect much help four years as of last week. agreed that it's been a while. In contr

RE: After upgrade autoconf from 1.13 to 2.57, I experienced some problems - HELP

2006-12-06 Thread J.R. Yang \(jryang\)
e same problem? Thanks in advance! - JRY --- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ralf Wildenhues Sent: Wednesday, December 06, 2006 3:54 PM To: Thomas Dickey Cc: autoconf@gnu.org Subject: Re: After upgrade autoconf

Re: After upgrade autoconf from 1.13 to 2.57, I experienced some problems - HELP

2006-12-06 Thread Ralf Wildenhues
* Thomas Dickey wrote on Wed, Dec 06, 2006 at 09:15:12PM CET: > On Wed, 6 Dec 2006, Ralf Wildenhues wrote: > > >2.57 was released six years ago. I don't think you can expect much help > > four years as of last week. Ouch, apologies for that misread of mine. > (however, it is not an unreasonabl

Re: After upgrade autoconf from 1.13 to 2.57, I experienced some problems - HELP

2006-12-06 Thread Thomas Dickey
On Wed, 6 Dec 2006, Ralf Wildenhues wrote: 2.57 was released six years ago. I don't think you can expect much help four years as of last week. even 2.50 is only a little over 5 years old. (however, it is not an unreasonable expectation from people that an application be evolved in a upwardl

Re: After upgrade autoconf from 1.13 to 2.57, I experienced some problems - HELP

2006-12-06 Thread Ralf Wildenhues
Hello, * J.R. Yang (jryang) wrote on Wed, Dec 06, 2006 at 07:19:01PM CET: > > I did some search on the web and found some solutions to some of the > known issues. I was able to run buildconf, and ./configure scripts. The > libtool was created in proper places. However, when I start the > compili

After upgrade autoconf from 1.13 to 2.57, I experienced some problems - HELP

2006-12-06 Thread J.R. Yang \(jryang\)
Hi, I did some search on the web and found some solutions to some of the known issues. I was able to run buildconf, and ./configure scripts. The libtool was created in proper places. However, when I start the compiling ("make"), I got some errors in C code and C++ code. In C code base, I got so