From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Sun, 17 Aug 2003 14:10:04 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 169 ************************************************** Saturday 16 August 2003 Number 169 ************************************************** Subjects for today 1 automake 1.7.6 : Andreas Buening 2 autoconf question : Stefan Neis 3 Re: autoconf question : Dave and Natalie" 4 Re: autoconf question : Stefan Neis 5 Re: automake 1.7.6 : Andreas Buening 6 Re: autoconf question : Andreas Buening 7 Re: autoconf question : Stefan Neis 8 Re: autoconf question : Stefan Neis **= Email 1 ==========================** Date: Sun, 17 Aug 2003 00:09:05 +0200 From: Andreas Buening Subject: automake 1.7.6 Hello! I've uploaded automake 1.7.6. It worked out of the box: http://unix.os2site.com/pub/source/automake/automake-1_7_6.zip As a new feature for a (possible) UnixOS/2 distro I've also uploaded what I call "binary" package of autoconf and automake: http://unix.os2site.com/pub/binary/autoconf/autoconf-2_57-bin.zip http://unix.os2site.com/pub/binary/automake/automake-1_7_6-bin.zip Those "binary" packages have two advantages: - You don't need to run ./configure, you just unzip them. - They're significantly smaller than the source packages. :-) Disadvantage: The paths are hardcoded, e.g. perl and m4 have to be in /usr/bin. How it works: You unzip the package into your UNIXROOT drive and run the included install script: sh -c ./install-ux2.sh For this you need patchux2: http://unix.os2site.com/pub/binary/autoconf/patchux2-0_1-bin.zip patchux2 replaces the drive letter in shell scripts by the UNIXROOT drive letter. If nobody objects I'll add patchux2 to /bin in the UnixOS/2 FHS. Please, keep in mind the autoconf/make binary packages are still experimental. ;-) Bye, Andreas **= Email 2 ==========================** Date: Sun, 17 Aug 2003 09:47:04 +0200 (CEST) From: Stefan Neis Subject: autoconf question Hello (Andreas), What exactly are the differences between configure scripts generated by autoconf-2.57 for OS/2 and normal autoconf-2.57? ac_executable_extension defaulting to .exe and path handling? Or anything else as well? Is there a script available to do those extra changes prior to calling configure? Currently, I'm getting a syntax error in the configure script for wxWindows-2.5.0 when I regenerate it on OS/2 while no such thing happens on Unix, so actually being able to run the Unix variant on OS/2 would help debugging a bit ... Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'. **= Email 3 ==========================** Date: Sun, 17 Aug 2003 10:44:01 -0800 From: "Dave and Natalie" Subject: Re: autoconf question --_=_=_=IMA.BOUNDARY.HJRQ9D138764=_=_=_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Sun, 17 Aug 2003 09:47:04 +0200 (CEST), Stefan Neis wrote: >Hello (Andreas), > >What exactly are the differences between configure scripts generated by >autoconf-2.57 for OS/2 and normal autoconf-2.57? ac_executable_extension >defaulting to .exe and path handling? Or anything else as well? Is there a >script available to do those extra changes prior to calling >configure? Currently, I'm getting a syntax error in the configure script >for wxWindows-2.5.0 when I regenerate it on OS/2 while no such thing >happens on Unix, so actually being able to run the Unix variant on OS/2 >would help debugging a bit ... I use a config.site that allows me to run most configure scripts without autoconf. Sometimes need to use Andreas config.guess so EMX is detected. It is only 1k compressed so I include it here. Don't forget to edit paths and perhaps CFLAGS etc. Dave --_=_=_=IMA.BOUNDARY.HJRQ9D138764=_=_=_ Content-Type: application/octet-stream; name="config.site.gz" Content-Transfer-Encoding: base64 H4sICJDLPz8ABmNvbmZpZy5zaXRlAK1VbXPaRhD+rhn9hw2Q4jgjKNiJW2cugwwyZiKQB6lj3JAo Qj7BxXqr7nBw4/737umAkAan7Uzuy+09+763d1t9whe6VoUwSyM2b3AmqDxuF6cCoOuMzgd93x14 FlmdNqMsa34lr2sbiQvLtom0SFd5VgjYxaVcFZxcsIT9GQiWpXDQH/0GSXBL4ahxcgxhkKaZgBmF OAtu6A2cGgfPTqUWTVYSAiOBo5+BLxp0hUK83ERRbuym3DhVe7W0K8lv9ecFzUshuqWiLRUGotyL pNySO4Xm+00tU/ZHKTALOE2DhKogMPeSmAefbpWirgWhH975i4wLwo5+eWnkoZHxtoH2dO1L4S5N 74J8CBOVRTOECg0XGTyV+NMKPMgEwaBQ550prk6zM69/0LXByPVMNPFB3OeY12kTzTZnLG2ylIsg jqW1hz2q63PjEDodaUcFmQdi4a81Se3z2vhfujY031hEFhavvEvmYYgV6U4mwDhkaXwPUVZAv9uF duPXF4B0Sj/RAmUnEzJ//hx0zbx6Q2RRdM22JiSKKSY/Nkf24IzIPHXt2kTD9Rnj2B7GfV3XPHNM dvIRQaEKivAW3GBnQ+/60iIsFZI+u/YslxxjTceDkWee2ZbvuP7IHFrEcZttDOvcNvsuqRs937eG E98Ho+e4bTB+TwRWClHX84eeb43HIwe5yJCXYjgoEmUJE0ZU4JUbeYYeaYEaXBRpiJ0QJjmRNENC wTuoBOtlUf6n/x/oHq/C7m3cP+ZOOuLold/zO4OzeRrE5VEE4S28aLUxiWoSFOGC3L4sWwfDoytB 1GWoVtoDld3l+92L/vhyfev/YDhXo32MsXuxhWOJF5KxhuTbTO4huLlh8m/h2KzHJDptLnlR9khy rGLAVrDPBq4z2u2qst8U/9Ia2ySnRayO1uRyvGsGP7Z1s7lWj6x/m03y4VIEs5giKWjKZRSkIvkV XeufnJD5yYmStnskXitO+pbnWRNv18dqToVAG0pij8BX/Orm7e9/9eii1Ro7jkcmqkjyjfKc4l+w TMMsSWgqQCwYl7xvXwT+c+sb/s6zcJDZG1um7Q9c/9x2TA/PI2dybo2H1nDT1VcY0SOdGy3TIotj AyWMOMtybLOIpTFLqWSF5YUiFAVcYDxiIft3X7T/HqyKtYwnCWLsaeWPfDlvHe5gH5eJlKmXA2A9 2krnsqQbBRCU48fzWdcAWARvASq1VgUIVIxVBd7BKywzTSUX5+qCRUKRpagRKeGNFBRULIsUTxHb ipV/e63VwOkArdfpMob2659asFH5ro78Of6Tzmo9Q2qHOGx2ps17NSMeGSDTaaOmJoi0IYcp1N9P D6pPpg9vYSreHWK75kUWTp/VobaCbSBSnsacKr3ZksWCqUJiPToVCUcMXk11DadPtVoFyzmH6g9Z fwMk7f69+wgAAA== --_=_=_=IMA.BOUNDARY.HJRQ9D138764=_=_=_-- **= Email 4 ==========================** Date: Sun, 17 Aug 2003 16:38:31 +0200 (CEST) From: Stefan Neis Subject: Re: autoconf question On Sun, 17 Aug 2003, Stefan Neis wrote: > Hello (Andreas), > > What exactly are the differences between configure scripts generated by > autoconf-2.57 for OS/2 and normal autoconf-2.57? OK, I'm going to ask a better question. I installed autoconf-2.57 on my OS/2 system (README.OS2 is dated 19.12.02, if that helps to identify the version I'm using more clearly). Now, whenever I regenerate configure for wxWindows-2.5 on my system and run the script, I get errors like this: ../../configure.os2[31259]: syntax error: `done' unexpected However, if I "manually" change backward to forward slashed, manually set ac_executable_extensions and then run the configure script generated on Unix, everything does work as expected, no syntax errors. Any idea? Miss-Installation of autoconf? Or is this a bug in the OS/2 specific code? BTW, while it makes no difference in the resulting script whether I run autoconf under sh (from pdksh) or under ash, running it under ash is considerably faster. Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'. **= Email 5 ==========================** Date: Sun, 17 Aug 2003 21:52:28 +0200 From: Andreas Buening Subject: Re: automake 1.7.6 Jeff Robinson wrote: [snip] > Sounds alright to me... I'll also add your make and autoconf to the > status list ( http://unixos2.com/pages/Status.html )... though by the > sounds of it I shouldn't mark them as "complete" just yet, huh? automake: yes autoconf: yes (restrictions see Stefan Neis' thread) make: not extensively tested and not (yet) all patches applied to the CVS repository. Bye, Andreas **= Email 6 ==========================** Date: Sun, 17 Aug 2003 21:52:47 +0200 From: Andreas Buening Subject: Re: autoconf question Stefan Neis wrote: > > On Sun, 17 Aug 2003, Stefan Neis wrote: > > > Hello (Andreas), > > > > What exactly are the differences between configure scripts generated by > > autoconf-2.57 for OS/2 and normal autoconf-2.57? [snip] - Sets ac_executable_extensions=".exe" - Changes back to forward slashes - Changes the AC_CHECK_LIB macro (otherwise link386 causes problems) This can be a problem if AC_CHECK_LIB is not quoted correctly. Bye, Andreas **= Email 7 ==========================** Date: Sun, 17 Aug 2003 22:43:43 +0200 (CEST) From: Stefan Neis Subject: Re: autoconf question On Sun, 17 Aug 2003, Andreas Buening wrote: > - Changes the AC_CHECK_LIB macro (otherwise link386 causes problems) > This can be a problem if AC_CHECK_LIB is not quoted correctly. Sounds like a likely explanation for my problem. I'll have to check the AC_CHECK_LIB macros when I find some time to do it ... Thanks, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'. **= Email 8 ==========================** Date: Sun, 17 Aug 2003 22:46:23 +0200 (CEST) From: Stefan Neis Subject: Re: autoconf question On Sun, 17 Aug 2003, Andreas Buening wrote: > - Sets ac_executable_extensions=".exe" > - Changes back to forward slashes > - Changes the AC_CHECK_LIB macro (otherwise link386 causes problems) > This can be a problem if AC_CHECK_LIB is not quoted correctly. Are those going to be included in next autoconf release? For now, I added code for the first two to wxWindows configure.in, so I no longer need to distribute OS/2-specific versions of the configure scripts ... (Since I'm expecting to build in a.out mode, link386 problems are not really relevant ... :-) ). Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'.