Re: Output additional header file

2016-05-30 Thread Keith Marshall
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30/05/16 07:06, A.P. Horst wrote: > I am using: msys-autoconf-2.68-1-msys-1.0.17 > msys-automake-1.11.1-1-msys-1.0.13 Just curious, but why? From the package description for the former: > This msys port of autoconf has been modified > specificall

Re: Output additional header file

2016-05-30 Thread A.P. Horst
On 5/30/2016 10:07, Keith Marshall wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30/05/16 07:06, A.P. Horst wrote: I am using: msys-autoconf-2.68-1-msys-1.0.17 msys-automake-1.11.1-1-msys-1.0.13 Just curious, but why? From the package description for the former: Very valid question

Re: Output additional header file

2016-05-30 Thread Gavin Smith
On 30 May 2016 at 07:06, A.P. Horst wrote: > Thanks for your help. > Attached is a bare-minimum configure script which demonstrates the problem. Thanks, I replicated the problem. I noticed that test.h.in had MS-DOS style line endings (CR LF). When I changed it to Unix-style (LF), the output file

Re: Output additional header file

2016-05-30 Thread A.P. Horst
Glad the problem and solution is so simple. Thanks for helping out! BR, Arie On 5/30/2016 10:22, Gavin Smith wrote: On 30 May 2016 at 07:06, A.P. Horst wrote: Thanks for your help. Attached is a bare-minimum configure script which demonstrates the problem. Thanks, I replicated the problem.

Re: Output additional header file

2016-05-30 Thread Keith Marshall
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 30/05/16 09:17, A.P. Horst wrote: > On 5/30/2016 10:07, Keith Marshall wrote: >> On 30/05/16 07:06, A.P. Horst wrote: >>> I am using: msys-autoconf-2.68-1-msys-1.0.17 >>> msys-automake-1.11.1-1-msys-1.0.13 >> >> Just curious, but why? From the pa