Has the build procedure changed?

It's been awhile since I've tried to build TN5250 from
CVS.  Has the 
process changed?  When I try to run ./autogen.sh, it fails
spectacularly 
with the following errors:

configure.ac:7: warning: do not use m4_patsubst: use
patsubst or 
m4_bpatsubst
aclocal.m4:546: AM_CONFIG_HEADER is expanded from...
configure.ac:7: the top level
configure.ac:234: warning: do not use m4_regexp: use regexp
or m4_bregexp
aclocal.m4:559: _AM_DIRNAME is expanded from...
configure.ac:234: the top level
configure.ac:7: warning: do not use m4_patsubst: use
patsubst or 
m4_bpatsubst
aclocal.m4:546: AM_CONFIG_HEADER is expanded from...
configure.ac:7: the top level
configure.ac:234: warning: do not use m4_regexp: use regexp
or m4_bregexp
aclocal.m4:559: _AM_DIRNAME is expanded from...
configure.ac:234: the top level
configure.ac:7: warning: do not use m4_patsubst: use
patsubst or 
m4_bpatsubst
aclocal.m4:546: AM_CONFIG_HEADER is expanded from...
configure.ac:7: the top level
configure.ac:234: warning: do not use m4_regexp: use regexp
or m4_bregexp
aclocal.m4:559: _AM_DIRNAME is expanded from...
configure.ac:234: the top level
automake: configure.ac: `AM_INIT_AUTOMAKE' must be used
libtoolize: `configure.in' does not exist
Try `libtoolize --help' for more information.
configure.ac: 18: installing `./ltmain.sh'; cannot run
`libtoolize': No 
such file or directory
libtoolize: `configure.in' does not exist
Try `libtoolize --help' for more information.
configure.ac: 18: installing `./config.guess'; cannot run
`libtoolize': No 
such file or directory
libtoolize: `configure.in' does not exist
Try `libtoolize --help' for more information.
configure.ac: 18: installing `./config.sub'; cannot run
`libtoolize': No 
such file or directory
python/Makefile.am: invalid unused variable name:
`lib5250_la_SOURCES'
autoreconf: automake failed with exit status: 1

Looking into CVS, it appears that Carey was the last person
to change the 
way autogen.sh worked.  He changed it to run
"autoreconf".

With this new system, do I need to type some different
commands or build 
TN5250 with different tools?  How do I fix the above errors?

---
Scott Klement  http://www.scottklement.c
om
-- 
This is the Linux 5250 Development Project (LINUX5250)
mailing list
To post a message email: LINUX5250midrange.com
To subscribe, unsubscribe, or change list options,
visit: 
http://lists.midrange.com/mailman/listinfo/linux5250
or email: LINUX5250-requestmidrange.com
Before posting, please take a moment to review the archives
at http://archive
.midrange.com/linux5250.

On Tue, 7 Mar 2006, Scott Klement wrote:

> It's been awhile since I've tried to build TN5250
from CVS.  Has the
> process changed?  When I try to run ./autogen.sh, it
fails spectacularly
> with the following errors:

Yes, the build has changed quite a bit.  However, autoreconf
should do the 
trick (i.e. no changed to what you type in to build it).

>
> configure.ac:7: warning: do not use m4_patsubst: use
patsubst or
> m4_bpatsubst

Not sure what this is..

> aclocal.m4:546: AM_CONFIG_HEADER is expanded from...
> configure.ac:7: the top level
> configure.ac:234: warning: do not use m4_regexp: use
regexp or m4_bregexp

Or this.

[snip]

> configure.ac:234: the top level
> automake: configure.ac: `AM_INIT_AUTOMAKE' must be
used
> libtoolize: `configure.in' does not exist
> Try `libtoolize --help' for more information.
> configure.ac: 18: installing `./ltmain.sh'; cannot run
`libtoolize': No
> such file or directory

This looks to me like it is trying to use the old
configure.in instead of 
the new configure.ac.  I wonder if you have old copies of
things lying 
around?

> Looking into CVS, it appears that Carey was the last
person to change the
> way autogen.sh worked.  He changed it to run
"autoreconf".
>
> With this new system, do I need to type some different
commands or build
> TN5250 with different tools?  How do I fix the above
errors?

autoreconf should do everything perfectly (at least it does
for me and the 
other people I've had test it).  It could be that your
auto* tools are 
rather old, though the new configure.ac doesn't use any
syntax that is 
particularly new.

James Rich

It's not the software that's free; it's you.
 	- billyskank on Groklaw
-- 
This is the Linux 5250 Development Project (LINUX5250)
mailing list
To post a message email: LINUX5250midrange.com
To subscribe, unsubscribe, or change list options,
visit: 
http://lists.midrange.com/mailman/listinfo/linux5250
or email: LINUX5250-requestmidrange.com
Before posting, please take a moment to review the archives
at http://archive
.midrange.com/linux5250.

> This looks to me like it is trying to use the old
configure.in instead of
> the new configure.ac.  I wonder if you have old copies
of things lying
> around?

No, I wiped out everything, then did a fresh checkout. 
There's nothing 
old in the tn5250 directory.


>> With this new system, do I need to type some
different commands or build
>> TN5250 with different tools?  How do I fix the
above errors?
>
> autoreconf should do everything perfectly (at least it
does for me and the
> other people I've had test it).  It could be that your
auto* tools are
> rather old, though the new configure.ac doesn't use
any syntax that is
> particularly new.

Which versions of the auto* tools should I be using?    I
was using the 
versions that I was using because they were the ones that
worked with 
TN5250.
-- 
This is the Linux 5250 Development Project (LINUX5250)
mailing list
To post a message email: LINUX5250midrange.com
To subscribe, unsubscribe, or change list options,
visit: 
http://lists.midrange.com/mailman/listinfo/linux5250
or email: LINUX5250-requestmidrange.com
Before posting, please take a moment to review the archives
at http://archive
.midrange.com/linux5250.

On Tue, 7 Mar 2006, Scott Klement wrote:

> Which versions of the auto* tools should I be using?   
I was using the
> versions that I was using because they were the ones
that worked with
> TN5250.

Here's what I have:

autoreconf (GNU Autoconf) 2.59
automake (GNU automake) 1.9.4

James Rich

It's not the software that's free; it's you.
 	- billyskank on Groklaw
-- 
This is the Linux 5250 Development Project (LINUX5250)
mailing list
To post a message email: LINUX5250midrange.com
To subscribe, unsubscribe, or change list options,
visit: 
http://lists.midrange.com/mailman/listinfo/linux5250
or email: LINUX5250-requestmidrange.com
Before posting, please take a moment to review the archives
at http://archive
.midrange.com/linux5250.

> autoreconf (GNU Autoconf) 2.59
> automake (GNU automake) 1.9.4

Thanks.   Can you also tell me the version of libtool?

-- 
This is the Linux 5250 Development Project (LINUX5250)
mailing list
To post a message email: LINUX5250midrange.com
To subscribe, unsubscribe, or change list options,
visit: 
http://lists.midrange.com/mailman/listinfo/linux5250
or email: LINUX5250-requestmidrange.com
Before posting, please take a moment to review the archives
at http://archive
.midrange.com/linux5250.

On Wed, 8 Mar 2006, Scott Klement wrote:

>> autoreconf (GNU Autoconf) 2.59
>> automake (GNU automake) 1.9.4
>
> Thanks.   Can you also tell me the version of libtool?

ltmain.sh (GNU libtool) 1.5.10 (1.1220.2.130 2004/09/19
12:13:49)

James Rich

It's not the software that's free; it's you.
 	- billyskank on Groklaw
-- 
This is the Linux 5250 Development Project (LINUX5250)
mailing list
To post a message email: LINUX5250midrange.com
To subscribe, unsubscribe, or change list options,
visit: 
http://lists.midrange.com/mailman/listinfo/linux5250
or email: LINUX5250-requestmidrange.com
Before posting, please take a moment to review the archives
at http://archive
.midrange.com/linux5250.

>>> autoreconf (GNU Autoconf) 2.59
>>> automake (GNU automake) 1.9.4
>>> ltmain.sh (GNU libtool) 1.5.10 (1.1220.2.130
2004/09/19 12:13:49)

I tried these versions and it worked.  I also tried the
latest versions, 
and that also worked.  Here are the versions I'm currently
running:

autoconf 2.59
automake 1.9.6
libtool 1.5.22

I do receive the following warning message:

     Using `AC_PROG_RANLIB' is rendered obsolete by
`AC_PROG_LIBTOOL'

But this doesn't seem to hurt anything?

Thanks for your help!
-- 
This is the Linux 5250 Development Project (LINUX5250)
mailing list
To post a message email: LINUX5250midrange.com
To subscribe, unsubscribe, or change list options,
visit: 
http://lists.midrange.com/mailman/listinfo/linux5250
or email: LINUX5250-requestmidrange.com
Before posting, please take a moment to review the archives
at http://archive
.midrange.com/linux5250.

The build for Win32 worked first time out.
I did the *nix build process under Cygwin and that worked,
too.

Both versions of the terminal worked OK but I did not do an
extensive
test.  I will start using the Win32 build ver 0.17.4 from
now on and
will report any issues.

You guys are doing a splendid job supporting us *nix
newbies.  Very commendable.
  --buck

-- 
This is the Linux 5250 Development Project (LINUX5250)
mailing list
To post a message email: LINUX5250midrange.com
To subscribe, unsubscribe, or change list options,
visit: 
http://lists.midrange.com/mailman/listinfo/linux5250
or email: LINUX5250-requestmidrange.com
Before posting, please take a moment to review the archives
at http://archive
.midrange.com/linux5250.