From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Fri, 28 Jun 2002 04:28:59 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 256 ************************************************** Thursday 27 June 2002 Number 256 ************************************************** Subjects for today 1 Re: Building Perl with VisualAge? : Henry Sobotka 2 Re: Patch -p : Thomas Dickey 3 Building Patch v2.5.4 : John Poltorak 4 Re: Makeinfo does not support LFNs : John Poltorak 5 Re: Texinfo bug : John Poltorak 6 Re: Errors building with NLs : John Poltorak 7 ZLIB v1.14 : John Poltorak 8 Re: ZLIB v1.14 : paul hartman" 9 Re: Xlib.h : paul hartman" 10 Re: Perl is too hungry? : Edwin =?iso-8859-1?Q?G=FCnthner?= 11 Re: Building Perl with VisualAge? : Henry Sobotka 12 Re: Errors building with NLs : Patrick Ash 13 Re: Perl is too hungry? : Henry Sobotka 14 Re: Xlib.h : Henry Sobotka 15 Re: Makeinfo does not support LFNs : csaba.raduly at sophos.com 16 Re: Errors building with NLs : Patrick Ash 17 Re: Building Perl with VisualAge? : csaba.raduly at sophos.com 18 Re: Building Perl with VisualAge? : csaba.raduly at sophos.com 19 Re: Patch -p : John Poltorak 20 Re: Errors building with NLs : Patrick Ash 21 PID files : John Poltorak 22 Xlib.h : John Poltorak 23 Re: Perl is too hungry? : Brian Havard" 24 Re: Rebuilding \emx\lib : Stefan Neis 25 Re: UnixOS/2 Build System : John Poltorak 26 Re: Errors building with NLs : John Poltorak 27 Re: Errors building with NLs : John Poltorak 28 Re: Errors building with NLs : John Poltorak 29 Re: Building Perl with VisualAge? : csaba.raduly at sophos.com 30 Re: Rebuilding \emx\lib : Holger Veit 31 Autoconf bug ? : John Poltorak 32 Re: Makeinfo does not support LFNs : Dave and Natalie" 33 Re: Rebuilding \emx\lib : Stefan Neis 34 Re: Rebuilding \emx\lib : John Poltorak 35 Re: Rebuilding \emx\lib : Henry Sobotka **= Email 1 ==========================** Date: Fri, 28 Jun 2002 00:51:12 -0400 From: Henry Sobotka Subject: Re: Building Perl with VisualAge? Dave and Natalie wrote: > > So how hard is it to move a build from VAC to OpenWatcom? I was looking at Privoxy (Junkbusters)( > http://ijbswa.sourceforge.net/) and the readme.os2 advices building with VAC as EMX has problems > with select and can only build a single threading client. Can't say anything about OpenWatcom except suggest that the easiest way to get OpenWatcom builds is to let Win32 weenies do the work (there are more of them) and clone the results; I would expect Win32->OS/2 OpenWatcom to be a piece of cake if not work out-of-the-box in most cases. For Privoxy, another option is to use the IBM TCP/IP headers (threadsafe select) and linkage, and add code to import the handles for EMX. h~ **= Email 2 ==========================** Date: Fri, 28 Jun 2002 06:09:22 -0400 From: Thomas Dickey Subject: Re: Patch -p On Fri, Jun 28, 2002 at 10:35:26AM +0100, John Poltorak wrote: > On Mon, Jun 24, 2002 at 05:17:13PM +0100, John Poltorak wrote: > > > > Is it possible to determine the appropriate value of -p for a patch file? > > Just in case anyone is wondering, someone provided me with this handy awk > script which seems to do the job OK:- generally - but that doesn't help with people who send a collection of diffs from various directories. (fortunately not many people do that ;-) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 3 ==========================** Date: Fri, 28 Jun 2002 07:40:47 +0100 From: John Poltorak Subject: Building Patch v2.5.4 Can anyone manage to build Jun SAWATAISHI's Patch program? http://www2s.biglobe.ne.jp/~vtgf3mpr/gnu/patch-2.5.4-1.i386-OS2.rpm -- John **= Email 4 ==========================** Date: Fri, 28 Jun 2002 07:48:34 +0100 From: John Poltorak Subject: Re: Makeinfo does not support LFNs On Thu, Jun 27, 2002 at 08:56:46PM -0800, Dave and Natalie wrote: > On Thu, 27 Jun 2002 19:59:26 +0100, John Poltorak wrote: > > > > >I've just found that MAKEINFO, (as included in EMX not the seperate port > >of GNU TEXINFO which also includes it) does not support long file names... > > > >When running makeinfo to build the M4 info files they ended up being > >called m4.i01, m4.i02, m4.i03 instead of m4.info-x . > > > >Can anyone confirm this behaviour? > > > >Or have I overlooked something when installing EMX? > > I get long filenames when running makeinfo m4.texinfo. Also lots of warning about warning: `.' or `,' must follow cross reference, not f. > X:\usr\src\m4-1.4\doc>e:\emx\bin\makeinfo --version > makeinfo (GNU texinfo) 4.0 I was specifically referring to the MAKEINFO which is part of EMX in \emx\bin... > Dave > ps there is an option to change EMX from short file names to long file names though I don't remember what it was ofhand That only changes the names of some headers AFAIK. -- John **= Email 5 ==========================** Date: Fri, 28 Jun 2002 07:57:18 +0100 From: John Poltorak Subject: Re: Texinfo bug On Thu, Jun 27, 2002 at 11:08:19PM +0200, Andreas Buening wrote: > John Poltorak wrote: > > > > When I use MAKEINFO from TEXINFO v4.0 I get the following msgs when > > creating the info docs for M4:- > > > > m4.texinfo:282: warning: `.' or `,' must follow cross reference, not f. > > m4.texinfo:352: warning: `.' or `,' must follow cross reference, not f. > > m4.texinfo:358: warning: `.' or `,' must follow cross reference, not f. > > m4.texinfo:363: warning: `.' or `,' must follow cross reference, not f. > > > > This does not occur with older versions of MAKEINFO. > > > > Can anyone confirm this behaviour? > > Yes. But it's only a warning. It also seems to be a standard feature of the original. > > bye, > Andreas > > -- > One OS to rule them all, One OS to find them, > One OS to bring them all and in the darkness bind them > In the Land of Redmond where the Shadows lie. -- John **= Email 6 ==========================** Date: Fri, 28 Jun 2002 08:13:01 +0100 From: John Poltorak Subject: Re: Errors building with NLs On Thu, Jun 27, 2002 at 08:22:21AM +0000, Patrick Ash wrote: > I have recently been experiencing problems getting some packages to > build with NLs enabled. When I remove the directive for NLS from the > configure script, the package builds without problem. Is it related to your version of GETTEXT? > this has > occurred lately with dialog 0.9b, texinfo-4.2, Does Texinfo 4.2 build on OS/2? I thought OS/2 specific patches were required and I haven't come across any for this version. > Thanks for any suggestions. > > Pat > > -- > Patrick Ash > patash at comcast.net > > This OS/2 system uptime is 20 days, 01:04 hours and 05 seconds > -- John **= Email 7 ==========================** Date: Fri, 28 Jun 2002 08:23:04 +0100 From: John Poltorak Subject: ZLIB v1.14 There is a ZLIB v1.14 on Hobbes:- http://hobbes.nmsu.edu/pub/os2/dev/unix/zlib114.zip Has anyone installed this? I'm wondering whether this version should be incorporated into UnixOS/2 as a replacement for v1.13. -- John **= Email 8 ==========================** Date: Fri, 28 Jun 2002 08:53:37 -0700 From: "paul hartman" Subject: Re: ZLIB v1.14 This is a multi-part message in MIME format. ------=_NextPart_000_0067_01C21E81.4B0DDF50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit <-----Original Message-----> >From: John Poltorak > >There is a ZLIB v1.14 on Hobbes:- > >Has anyone installed this? This version of Zlib fixes a security hole which exists in previous versions (don't know whether it affects the OS/2 version or not - it has something to do with trying to free the same memory twice). See http://www.zlib.org for more info... In any case, I've used this version with a few programs and havn't noticed anything peculiar. Regards, Paul ------=_NextPart_000_0067_01C21E81.4B0DDF50 Content-Type: text/html Content-Transfer-Encoding: 7bit <-----Original Message----->
>From: John Poltorak
>
>There is a ZLIB v1.14 on Hobbes:-
>
>Has anyone installed this?

This version of Zlib fixes a security hole which exists in previous versions (don't know whether it affects the OS/2 version or not - it has something to do with trying to free the same memory twice). See http://www.zlib.org for more info...

In any case, I've used this version with a few programs and havn't noticed anything peculiar.

Regards,
Paul ------=_NextPart_000_0067_01C21E81.4B0DDF50-- **= Email 9 ==========================** Date: Fri, 28 Jun 2002 09:01:40 -0700 From: "paul hartman" Subject: Re: Xlib.h This is a multi-part message in MIME format. ------=_NextPart_000_0026_01C21E82.6A7C7BC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit <-----Original Message-----> >From: John Poltorak > >Where do I find Xlib.h and Xutil.h? I believe they are X11/Xfree86 includes... Regards, Paul ------=_NextPart_000_0026_01C21E82.6A7C7BC0 Content-Type: text/html Content-Transfer-Encoding: 7bit <-----Original Message----->
>From: John Poltorak
>
>Where do I find Xlib.h and Xutil.h?

I believe they are X11/Xfree86 includes...

Regards,
Paul
------=_NextPart_000_0026_01C21E82.6A7C7BC0-- **= Email 10 ==========================** Date: Fri, 28 Jun 2002 09:03:06 -0400 From: Edwin =?iso-8859-1?Q?G=FCnthner?= Subject: Re: Perl is too hungry? > Are the PERL module DLLs being built a.out? If so, each will get 32MB of Do not know that. But that would explain the things we see here. Henry? > address space allocated for a heap unless you take steps to override. The > 512MB of address space starts to run out pretty quick if you have a large > quantity of such DLLs. **= Email 11 ==========================** Date: Fri, 28 Jun 2002 09:25:17 -0400 From: Henry Sobotka Subject: Re: Building Perl with VisualAge? csaba.raduly at sophos.com wrote: > > Not necessarily. I could e.g. build wget with Watcom for NT (even > cross-compile under OS/2 to get an NT executable :-) but not for > OS/2 (lots of compiler errors) Interesting. Where were they coming from? Library differences? h~ **= Email 12 ==========================** Date: Fri, 28 Jun 2002 09:33:25 +0000 From: Patrick Ash Subject: Re: Errors building with NLs On Fri, 28 Jun 2002 08:13:01 +0100, John Poltorak wrote: >On Thu, Jun 27, 2002 at 08:22:21AM +0000, Patrick Ash wrote: >> I have recently been experiencing problems getting some packages to >> build with NLs enabled. When I remove the directive for NLS from the >> configure script, the package builds without problem. > >Is it related to your version of GETTEXT? It could be, but I am using the binary version of 0.10.39 provided by Andreas. langinfo.h does not change from one version to another. it is exactly the same file in every version of gettext that I have installed. It also does not matter if I use the 'included-gettext' option in the configure script, or rely on the installed version I have here. > >> this has >> occurred lately with dialog 0.9b, texinfo-4.2, > >Does Texinfo 4.2 build on OS/2? I thought OS/2 specific patches were >required and I haven't come across any for this version. I cannot comment on how well it works, but once I removed the --enable-nls option from configure, it built without problem. Pat -- Patrick Ash patash at comcast.net This OS/2 system uptime is 21 days, 02:15 hours and 09 seconds **= Email 13 ==========================** Date: Fri, 28 Jun 2002 09:49:39 -0400 From: Henry Sobotka Subject: Re: Perl is too hungry? Edwin Günthner wrote: > > > Are the PERL module DLLs being built a.out? If so, each will get 32MB of > > Do not know that. But that would explain the things we see here. > Henry? Can't say for certain as I haven't paid much attention to the details of the a.out build. My impression though, is that it uses static linkage for the standard modules, i.e. no dynaload. I don't see any other way of accounting for the approximately 5-meg difference between the 5.6.x and 5.7.x perl_.exe. h~ **= Email 14 ==========================** Date: Fri, 28 Jun 2002 09:51:03 -0400 From: Henry Sobotka Subject: Re: Xlib.h John Poltorak wrote: > > Where do I find Xlib.h and Xutil.h? XFree86/include. h~ **= Email 15 ==========================** Date: Fri, 28 Jun 2002 09:56:48 +0100 From: csaba.raduly at sophos.com Subject: Re: Makeinfo does not support LFNs On 27/06/2002 19:59:26 owner-os2-unix wrote: >I've just found that MAKEINFO, (as included in EMX not the separate port >of GNU TEXINFO which also includes it) does not support long file names... > >When running makeinfo to build the M4 info files they ended up being >called m4.i01, m4.i02, m4.i03 instead of m4.info-x . > I think that's in line with EM's goal to support FAT. Rename or copy m4.texinfo to m4withaverylongname.texinfo Try building info files from that. I suspect you'll get m4withaverylongname.i01 and so on Besides, if you build with --no-split you'd get m4.info That is clearly a "long file name" (4 character extension is long :-) -- Csaba Ráduly, Software Engineer Sophos Anti-Virus email: csaba.raduly at sophos.com http://www.sophos.com US Support: +1 888 SOPHOS 9 UK Support: +44 1235 559933 **= Email 16 ==========================** Date: Fri, 28 Jun 2002 09:58:58 +0000 From: Patrick Ash Subject: Re: Errors building with NLs On Fri, 28 Jun 2002 14:41:36 +0100, John Poltorak wrote: >> >Does Texinfo 4.2 build on OS/2? I thought OS/2 specific patches were >> >required and I haven't come across any for this version. >> >> I cannot comment on how well it works, but once I removed the >> --enable-nls option from configure, it built without problem. > >Is this the standard GNU version of Texinfo v4.2 ? > ftp://ftp.gnu.org/gnu/texinfo/texinfo-4.2.tar.gz Pat -- Patrick Ash patash at comcast.net This OS/2 system uptime is 21 days, 02:40 hours and 42 seconds **= Email 17 ==========================** Date: Fri, 28 Jun 2002 10:02:03 +0100 From: csaba.raduly at sophos.com Subject: Re: Building Perl with VisualAge? On 28/06/2002 05:36:14 owner-os2-unix wrote: >On Thu, 27 Jun 2002 12:02:50 +0100, John Poltorak wrote: > >> >>Maybe VAC is at the end of the road but OpenWatcom is only just at the >>beginning, so the principles of building Perl under VAC would also apply >>to Watcom. > >So how hard is it to move a build from VAC to OpenWatcom? I was looking at >Privoxy (Junkbusters)(http://ijbswa.sourceforge.net/) and the readme.os2 >advices building with VAC as EMX has problems with select and can only build a >single threading client. That's not a problem with Perl, as multithreading is still highly experimental. As to moving a build from VAC to OpenWatcom: just change the compiler names and substitute the appropriate switches :-) *THEN* you can start worrying about missing functions and incompatible features :-) -- Csaba Ráduly, Software Engineer Sophos Anti-Virus email: csaba.raduly at sophos.com http://www.sophos.com US Support: +1 888 SOPHOS 9 UK Support: +44 1235 559933 **= Email 18 ==========================** Date: Fri, 28 Jun 2002 10:04:36 +0100 From: csaba.raduly at sophos.com Subject: Re: Building Perl with VisualAge? On 28/06/2002 05:51:12 owner-os2-unix wrote: > >Can't say anything about OpenWatcom except suggest that the easiest way >to get OpenWatcom builds is to let Win32 weenies do the work (there are >more of them) and clone the results; I would expect Win32->OS/2 >OpenWatcom to be a piece of cake if not work out-of-the-box in most >cases. > Not necessarily. I could e.g. build wget with Watcom for NT (even cross-compile under OS/2 to get an NT executable :-) but not for OS/2 (lots of compiler errors) -- Csaba Ráduly, Software Engineer Sophos Anti-Virus email: csaba.raduly at sophos.com http://www.sophos.com US Support: +1 888 SOPHOS 9 UK Support: +44 1235 559933 **= Email 19 ==========================** Date: Fri, 28 Jun 2002 10:35:26 +0100 From: John Poltorak Subject: Re: Patch -p On Mon, Jun 24, 2002 at 05:17:13PM +0100, John Poltorak wrote: > > Is it possible to determine the appropriate value of -p for a patch file? Just in case anyone is wondering, someone provided me with this handy awk script which seems to do the job OK:- patch -p`awk 'BEGIN { min_p = 1234567 } $1 == "+++" { gsub (/[^/]/, "", $2) if (length($2) < min_p) min_p = length($2) } END { print min_p }' PATCHFILE` < PATCHFILE -- John **= Email 20 ==========================** Date: Fri, 28 Jun 2002 10:38:54 +0000 From: Patrick Ash Subject: Re: Errors building with NLs On Fri, 28 Jun 2002 15:08:41 +0100, John Poltorak wrote: >> >Is this the standard GNU version of Texinfo v4.2 ? >> > >> >> >> ftp://ftp.gnu.org/gnu/texinfo/texinfo-4.2.tar.gz > > >I just tried building it and it stopped abruptly here:- > >checking minix/config.h presence... no >checking for minix/config.h... no >checking for sigblock... no >configure[3594]: syntax error: `done' unexpected >make: Nothing to be done for `.'. >make: Nothing to be done for `install'. >end > > >Wondered what I'm doing differently... > >Did you run autoconf first? > >Which shell are you using? > I used Ilya's convert_configure.pl rather than autoconf. I have 2.53 installed, but it is not the version that Andreas has patched, and it has been a little problematic for some things in the past. I am now using pdksh 5.2.14, the latest one from ftp.math.ohio-state.edu I can send you the configure script if you want to look at it. Pat -- Patrick Ash patash at comcast.net This OS/2 system uptime is 21 days, 03:20 hours and 38 seconds **= Email 21 ==========================** Date: Fri, 28 Jun 2002 11:28:46 +0100 From: John Poltorak Subject: PID files Is there a standard, or recommended location for PID files? If I have a choice, I tend to put mine in /var/run Does this seem a reasonable standard for UnixOS/2? -- John **= Email 22 ==========================** Date: Fri, 28 Jun 2002 12:00:08 +0100 From: John Poltorak Subject: Xlib.h Where do I find Xlib.h and Xutil.h? They appear to be required by less. -- John **= Email 23 ==========================** Date: Fri, 28 Jun 2002 12:48:11 +1000 (EST) From: "Brian Havard" Subject: Re: Perl is too hungry? On Thu, 27 Jun 2002 17:12:48 -0400, Edwin Günthner wrote: >Strange, we are using theseus4 and get something different. > >> BTW, you'll find all kinds of details about Perl memory management in >> the Perl docs. > >True. But I guess we are not exactly dealing with a Perl >problem here. Guess it is more up to our environment ... Are the PERL module DLLs being built a.out? If so, each will get 32MB of address space allocated for a heap unless you take steps to override. The 512MB of address space starts to run out pretty quick if you have a large quantity of such DLLs. -- ______________________________________________________________________________ | Brian Havard | "He is not the messiah! | | brianh at kheldar.apana.org.au | He's a very naughty boy!" - Life of Brian | ------------------------------------------------------------------------------ **= Email 24 ==========================** Date: Fri, 28 Jun 2002 13:52:09 +0200 (CEST) From: Stefan Neis Subject: Re: Rebuilding \emx\lib On Thu, 27 Jun 2002, Henry Sobotka wrote: > > make all-os2 > > > > ...but it has never worked for me. > > Are you using dmake (required IIRC)? And IIRC, it also has to be a specific version of dmake, not the latest one ... Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'. **= Email 25 ==========================** Date: Fri, 28 Jun 2002 13:59:44 +0100 From: John Poltorak Subject: Re: UnixOS/2 Build System On Thu, Jun 27, 2002 at 04:42:25PM +0100, John Poltorak wrote: > > I've spent a while trying to devise a single UnixOS/2 Build framework > which consists of a few wrapper scripts and some configuration files, and > I'd like to get some feedback on how well it works. > > The idea is that any UnixOS/2 app can built within this framework using:- > > build APPNAME Just wondered if anyone had given it a try... So far I have autoconf, automake, bzip2, less and m4 working > The whole thing starts in 'lib' where you run BUILD.CMD with the build > target, eg BUILD BZIP2. > > All targets are held in a parameter table BUILD.TABLE and it's the table > which drives the process and is the key part of making the framework work > with every app, so it's structure will probably need to be modified. > > Please, let me know how you get on and if you think of any way to simplify > things, just say. > > At the moment I haven't figured out how to adjust the -p level for patch > so if '-p 1' in build.sh doesn't work, try '-p 2'. > > If anyone can come up with a solution to this, I would be interested. There is a solution to this now which has been incorporated into the main shell script build.sh. > It's as well to try Autoconf and Automake first as they are likely to be > required by various apps. I suppose it would be easiest to download the whole thing using wget, but I can't remember the syntax for logging on as a particular user. Can anyone remind me? -- John **= Email 26 ==========================** Date: Fri, 28 Jun 2002 14:41:36 +0100 From: John Poltorak Subject: Re: Errors building with NLs On Fri, Jun 28, 2002 at 09:33:25AM +0000, Patrick Ash wrote: > >> this has > >> occurred lately with dialog 0.9b, texinfo-4.2, > > > >Does Texinfo 4.2 build on OS/2? I thought OS/2 specific patches were > >required and I haven't come across any for this version. > > I cannot comment on how well it works, but once I removed the > --enable-nls option from configure, it built without problem. Is this the standard GNU version of Texinfo v4.2 ? > Pat > > -- > Patrick Ash > patash at comcast.net > > This OS/2 system uptime is 21 days, 02:15 hours and 09 seconds > -- John **= Email 27 ==========================** Date: Fri, 28 Jun 2002 15:08:41 +0100 From: John Poltorak Subject: Re: Errors building with NLs On Fri, Jun 28, 2002 at 09:58:58AM +0000, Patrick Ash wrote: > On Fri, 28 Jun 2002 14:41:36 +0100, John Poltorak wrote: > >> I cannot comment on how well it works, but once I removed the > >> --enable-nls option from configure, it built without problem. > > > >Is this the standard GNU version of Texinfo v4.2 ? > > > > > ftp://ftp.gnu.org/gnu/texinfo/texinfo-4.2.tar.gz I just tried building it and it stopped abruptly here:- checking minix/config.h presence... no checking for minix/config.h... no checking for sigblock... no configure[3594]: syntax error: `done' unexpected make: Nothing to be done for `.'. make: Nothing to be done for `install'. end Wondered what I'm doing differently... Did you run autoconf first? Which shell are you using? > Pat > > -- > Patrick Ash > patash at comcast.net > > This OS/2 system uptime is 21 days, 02:40 hours and 42 seconds -- John **= Email 28 ==========================** Date: Fri, 28 Jun 2002 15:50:21 +0100 From: John Poltorak Subject: Re: Errors building with NLs On Fri, Jun 28, 2002 at 10:38:54AM +0000, Patrick Ash wrote: > On Fri, 28 Jun 2002 15:08:41 +0100, John Poltorak wrote: > > >> >Is this the standard GNU version of Texinfo v4.2 ? > >> > > >> > >> > >> ftp://ftp.gnu.org/gnu/texinfo/texinfo-4.2.tar.gz > > > > > >I just tried building it and it stopped abruptly here:- > > > >configure[3594]: syntax error: `done' unexpected > >Wondered what I'm doing differently... > > > >Did you run autoconf first? > > > >Which shell are you using? > > > I used Ilya's convert_configure.pl rather than autoconf. I have 2.53 > installed, but it is not the version that Andreas has patched, and it > has been a little problematic for some things in the past. I am now > using pdksh 5.2.14, the latest one from ftp.math.ohio-state.edu I can > send you the configure script if you want to look at it. I've just grabbed it. My hope was that with the updated Autoconf 2.53 port there would no longer be any need to convert configure scripts as the would be built correctly in the first place. I'll see how they differ. > Pat > > > -- > Patrick Ash > patash at comcast.net > > This OS/2 system uptime is 21 days, 03:20 hours and 38 seconds -- John **= Email 29 ==========================** Date: Fri, 28 Jun 2002 16:24:58 +0100 From: csaba.raduly at sophos.com Subject: Re: Building Perl with VisualAge? On 28/06/2002 14:25:17 owner-os2-unix wrote: >csaba.raduly at sophos.com wrote: >> >> Not necessarily. I could e.g. build wget with Watcom for NT (even >> cross-compile under OS/2 to get an NT executable :-) but not for >> OS/2 (lots of compiler errors) > >Interesting. Where were they coming from? Library differences? > Huh ? Compiler errors from library differences ? No, they were conflicts between the OS/2 TCPIP headers and something else (IIRC, it's been some time). -- Csaba Ráduly, Software Engineer Sophos Anti-Virus email: csaba.raduly at sophos.com http://www.sophos.com US Support: +1 888 SOPHOS 9 UK Support: +44 1235 559933 **= Email 30 ==========================** Date: Fri, 28 Jun 2002 16:33:40 +0200 From: Holger Veit Subject: Re: Rebuilding \emx\lib On Fri, Jun 28, 2002 at 01:52:09PM +0200, Stefan Neis wrote: > On Thu, 27 Jun 2002, Henry Sobotka wrote: > > > > make all-os2 > > > > > > ...but it has never worked for me. > > > > Are you using dmake (required IIRC)? > > And IIRC, it also has to be a specific version of dmake, not the > latest one ... Maybe I have just been lucky, but I haven't observed this yet. Anyway, a working dmake.exe should be in the emxtree.zip file. Holger -- Please update your tables to my new e-mail address: holger.veit$ais.fhg.de (replace the '$' with ' at ' -- spam-protection) **= Email 31 ==========================** Date: Fri, 28 Jun 2002 16:53:53 +0100 From: John Poltorak Subject: Autoconf bug ? It looks as though there is a bug in Autoconf 2.53 for OS/2 which causes this error in Texinfo 4.2:- checking minix/config.h presence... no checking for minix/config.h... no checking for sigblock... no configure[3594]: syntax error: `done' unexpected If I don't run Autoconf, or use a configure converter this error dosn't occur. Does anyone else get this error? texinfo is here in case anyone wants to give it a whirl:- ftp://ftp.gnu.org/pub/gnu/texinfo/texinfo-4.2.tar.gz -- John **= Email 32 ==========================** Date: Fri, 28 Jun 2002 16:55:17 -0800 From: "Dave and Natalie" Subject: Re: Makeinfo does not support LFNs On Fri, 28 Jun 2002 07:48:34 +0100, John Poltorak wrote: >> >> I get long filenames when running makeinfo m4.texinfo. Also lots of warning about warning: `.' or `,' must follow cross reference, not f. >> X:\usr\src\m4-1.4\doc>e:\emx\bin\makeinfo --version >> makeinfo (GNU texinfo) 4.0 > >I was specifically referring to the MAKEINFO which is part of EMX in >\emx\bin... Sorry about that, I must of upgraded mine then forgot Dave **= Email 33 ==========================** Date: Fri, 28 Jun 2002 17:31:26 +0200 (CEST) From: Stefan Neis Subject: Re: Rebuilding \emx\lib On Fri, 28 Jun 2002, Holger Veit wrote: > On Fri, Jun 28, 2002 at 01:52:09PM +0200, Stefan Neis wrote: > > And IIRC, it also has to be a specific version of dmake, not the > > latest one ... > > Maybe I have just been lucky, but I haven't observed this yet. Anyway, > a working dmake.exe should be in the emxtree.zip file. I seem to remember that dmake4.0 was rather incompatible with earlier versions, but I haven't used dmake for some years any more... Stefan **= Email 34 ==========================** Date: Fri, 28 Jun 2002 18:21:12 +0100 From: John Poltorak Subject: Re: Rebuilding \emx\lib On Thu, Jun 27, 2002 at 01:27:49PM -0400, Henry Sobotka wrote: > John Poltorak wrote: > > > > Yes, there is \emx\doc\build.doc which has instructions for building the > > libraries. It even says:- > > > > To build all the emx libraries and C library DLLs, type: > > > > cd \emx\src\lib > > make all-os2 > > > > ...but it has never worked for me. > > Are you using dmake (required IIRC)? Yes. It does work to some extent, but I get errors. What I'm never sure about is where C_LIBRARY_PATH should be and whether rebuilding the LIBS should overwrite the originals. Is there a way to specify a target directory? I would like the new libs to appear in \usr\lib if posible, and assume the original libs must be available to build new libs... > h~ -- John **= Email 35 ==========================** Date: Fri, 28 Jun 2002 18:40:06 -0400 From: Henry Sobotka Subject: Re: Rebuilding \emx\lib John Poltorak wrote: > > Yes. It does work to some extent, but I get errors. It's been three or four years, but I vaguely recall hitting a build break, though not the details. > What I'm never sure about is where C_LIBRARY_PATH should be and whether > rebuilding the LIBS should overwrite the originals. > > Is there a way to specify a target directory? > > I would like the new libs to appear in \usr\lib if posible, and assume the > original libs must be available to build new libs... Only insofar as gcc needs the emx runtime.DLLs. C_LIBRARY_PATH is irrelevant to linkage, though might be used to determine where to install the new libraries. It does overwrite itself; IIRC that's mentioned in the build doc, which might also describe how to set the target directory. Otherwise, a look through the makefiles and/or batch files should turn up how it's handled. h~