From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Thu, 27 Jun 2002 04:28:53 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 255 ************************************************** Wednesday 26 June 2002 Number 255 ************************************************** Subjects for today 1 Re: M4 build problem with texinfo : Stefan Neis 2 Re: Makeflags : Stefan Neis 3 Re: unixos2 packages : Brian Havard" 4 Errors building with NLs : Patrick Ash 5 Re: Perl is too hungry? : Edwin =?iso-8859-1?Q?G=FCnthner?= 6 Debugging Make : John Poltorak 7 Re: %UNIXROOT% : John Poltorak 8 Re: Makeflags : John Poltorak 9 Re: ssh in X (was: Re:Emacs & X-Export) : Pete Milne 10 Re: Building Perl with VisualAge? : John Poltorak 11 sh -x : John Poltorak 12 Re: Rebuilding \emx\lib : Henry Sobotka 13 Rebuilding \emx\lib : John Poltorak 14 Re: Perl is too hungry? : Henry Sobotka 15 Re: Perl 5.73 and perl212F.dll : Henry Sobotka 16 Re: Patch -p : John Poltorak 17 Re: UnixOS/2 environment : John Poltorak 18 Re: Patch -p : csaba.raduly at sophos.com 19 Re: ssh in X (was: Re:Emacs & X-Export) : Dave Saville" 20 UnixOS/2 Build System : John Poltorak 21 Re: Rebuilding \emx\lib : John Poltorak 22 Re: Perl is too hungry? : Edwin =?iso-8859-1?Q?G=FCnthner?= 23 Re: Perl is too hungry? : Edwin =?iso-8859-1?Q?G=FCnthner?= 24 Re: Rebuilding \emx\lib : Stefan Neis 25 Re: Texinfo bug : Thomas Dickey 26 Re: Perl is too hungry? : Henry Sobotka 27 Perl 5.73 and perl212F.dll : Michel SUCH" 28 Re: Perl 5.73 and perl212F.dll : Michel SUCH" 29 Makeinfo does not support LFNs : John Poltorak 30 Re: Makeinfo does not support LFNs : Lyn St George" 31 Texinfo bug : John Poltorak 32 Re: Building Perl with VisualAge? : Dave and Natalie" 33 Re: Makeinfo does not support LFNs : Dave and Natalie" 34 Re: Texinfo bug : Andreas Buening 35 Re: Makeflags : Andreas Buening **= Email 1 ==========================** Date: Thu, 27 Jun 2002 00:36:40 +0200 (CEST) From: Stefan Neis Subject: Re: M4 build problem with texinfo On Wed, 26 Jun 2002, John Poltorak wrote: > Using the old version of INFO, I get:- > > making all in doc ^^^ Hm, it's not running texinfo at all for some reason :-? > With the new one I get:- > > making install in doc ^^^^^^^ > cd . && makeinfo m4.texinfo > m4.texinfo:282: warning: `.' or `,' must follow cross reference, not f. > .. > .. > .. > m4.texinfo:1625: warning: `.' or `,' must follow cross reference, not f. > .... > install-info --info-dir=c:/usr/local/info c:/usr/local/info/m4.info > make[1]: Leaving directory `C:/unixos2/workdir/m4-1.4/doc' Hm, it looks like it is succeding after all, so the warnings aren't really critical ... > The Makefiles are identical, and I don't have a clue what is happening > here. I must admit I'm lost as to why it's doing "make all" in one case and "make install" in the other ... Regards, Stefan **= Email 2 ==========================** Date: Thu, 27 Jun 2002 00:42:21 +0200 (CEST) From: Stefan Neis Subject: Re: Makeflags On Wed, 26 Jun 2002 csaba.raduly at sophos.com wrote: > >IIRC, make (at least GNUmake) is initialising AR,CC,CXX etc. from > >hardcoded defaults, I'd be most grateful if everyone forgets that nonsense I wrote... :-( > Hence, any GNU make 3.74 or newer should use the environment value. Exactly. > say: > at echo AR is now '$(AR)' > > then do > > export AR=emxomfar > make say Works at least for me, the original problem likely was a missing "export" ... Regards, Stefan **= Email 3 ==========================** Date: Thu, 27 Jun 2002 02:06:23 +1000 (EST) From: "Brian Havard" Subject: Re: unixos2 packages On Wed, 26 Jun 2002 16:21:25 +0200 (CEST), Stefan Neis wrote: >On Wed, 26 Jun 2002, Brian Havard wrote: > >> BTW, I have a patch for 0.9.7 that adds support for building OS/2 DLLs >> instead of static libraries which may be of use for building a unixos2 >> package. If anyone's interested I can put it up on my "Building OpenSSL" >> page. > >Any chance to get the patch integrated into the official 0.9.7 release? >Otherwise we'll likely see a number of incompatible DLL's being >distributed within the months following the release as OpenSSL seems to be >used more and more frequently... I subitted it some time ago but didn't get any response. I should probably try again.... -- ______________________________________________________________________________ | Brian Havard | "He is not the messiah! | | brianh at kheldar.apana.org.au | He's a very naughty boy!" - Life of Brian | ------------------------------------------------------------------------------ **= Email 4 ==========================** Date: Thu, 27 Jun 2002 08:22:21 +0000 From: Patrick Ash Subject: Errors building with NLs 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. this has occurred lately with dialog 0.9b, texinfo-4.2, and libiconv-1.8. After looking at the output from the configure script, I find that the following message seems to be present in some form for all of them. checking for langinfo.h... yes checking for nl_langinfo... no checking for nl_langinfo and CODESET... no why is the compiler unable to resolve nl_langinfo and codeset when the header file is present and found? This happens with both pgcc 2.9.5 and gcc 3.0.3. 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 **= Email 5 ==========================** Date: Thu, 27 Jun 2002 08:58:05 -0400 From: Edwin =?iso-8859-1?Q?G=FCnthner?= Subject: Re: Perl is too hungry? Hi there, question: > Here the OMF-version interpreter itself takes up less than 1 MB. > Obviously, when running a script that creates a hash out of a 20-MB > input file, it uses a lot more. How do measure this? What program are you using to retrieve this information? And again - the perl_ takes much less than the perl. Is that different in your environment? Well, I was always suspicious because it takes Perl 3 or 4 seconds to load on our OS2 machines. Unfortunately not suspicious enough to do this kind of profiling myself. **= Email 6 ==========================** Date: Thu, 27 Jun 2002 10:52:33 +0100 From: John Poltorak Subject: Debugging Make I am getting different results when running Make on a particular Makefile and I thought I would try tracing what was going on. What I'd like to do is enable debugging, but only in on particular subdirectory. Is there any way of doing that? -- John **= Email 7 ==========================** Date: Thu, 27 Jun 2002 11:22:39 +0100 From: John Poltorak Subject: Re: %UNIXROOT% On Wed, Jun 26, 2002 at 11:48:25PM +0100, Thomas Hoffmann wrote: > Some weeks ago the message which is cited below showed up on os2-unix. > > In the meantime I tried to install some unixos2 packages of software > mentioned below (man, and as a prerequisite groff) and had to do add a > lot SET statements to config.sys to get these software to work (because > the defaults of GROFF*PATH are c:\os2\... or so). > > My question is: Has there been some progress with unixrootified versions > of the software mentioned below or has the implementation of UNIXROOT in > ports to be discussed further? Personally, I don't think that %UNIXROOT% should be taken account of in any apps. It's my understanding that this variable will be used by LIBEMU and IX.SYS to convert paths such as /usr to %UNIXROOT%/usr and that nothing needs to be done by any porter. > -- > Thomas Hoffmann Telephone: > 49-351-4598831 > thoffman at zappa.sax.de Dresden, > Germany > > ..sig under construction ... -- John **= Email 8 ==========================** Date: Thu, 27 Jun 2002 11:54:03 +0100 From: John Poltorak Subject: Re: Makeflags On Wed, Jun 26, 2002 at 05:59:19PM +0100, csaba.raduly at sophos.com wrote: > > John, what happens if you add the following to the makefile: > > say: > at echo AR is now '$(AR)' > > then do > > export AR=emxomfar > make say It says:- AR is now emxomfar But having the environment variable set does not appear to have the desired effect. The only thing I have found which works is to run:- make AR=emxomfar at the command line. I don't understand what is going on here at all. -- John **= Email 9 ==========================** Date: Thu, 27 Jun 2002 12:02:01 +0100 From: Pete Milne Subject: Re: ssh in X (was: Re:Emacs & X-Export) Stefan Neis wrote: > On Wed, 26 Jun 2002, Adrian Gschwend wrote: > > > yes I guess you don't use OpenSSH 3.x, do you? > > Ah yes, you're right, thanks for clarifying why I did see a > "-X" option under Linux but not under OS/2. ;-) > > > Which window manager are you using? Must be a > > shell problem on my system > > Well, you could try to open an OS/2-window in PM and enter your > "ssh -X whatever" and hopefully password and some commands there, > maybe that will work around whatever problem you currently see. > X windows from the remote box still should make it to your XFree86 > screen. Switching around between XFree86 and PM is a bit annoying > of course, but if it works that would give a hint at the real > source of the problem (I suppose openssh has some problem with > xterm or tty handling, that's a notorious problem with code that > hasn't been ported with the idea of supporting both PM and XFree > session in mind). > > For me, this works fine with ssh-1.2.30 (whatever that exactly is) > and it works even better with HOB-X11. :-) > > Regards, > Stefan Please excuse me if I'm off the point, as I no longer have the start of this thread. What works for me is, with XFree86 running, switch back to PM, open an OS/2 window, SSH to the remote system and do "xterm", and finally switch back to XFree86. I now have an Xterm window for the remote host, and can start any application with, e.g. "emacs &" hth Pete **= Email 10 ==========================** Date: Thu, 27 Jun 2002 12:02:50 +0100 From: John Poltorak Subject: Re: Building Perl with VisualAge? On Wed, Jun 26, 2002 at 11:55:15AM -0700, James Cannon wrote: > Isn't VA at the end of it's road? It seems pointless > to put so much effort in a product that IBM isn't > supportting. Meanwhile on the GCC front, developement > continues ... 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. > ===== > Sincerely, > James Cannon -- John **= Email 11 ==========================** Date: Thu, 27 Jun 2002 12:23:29 +0100 From: John Poltorak Subject: sh -x I'm aware of the '-x' flag to enable tracing in a shell script, but is there any way to enable tracing just in a shell script called within a script? ie if I have:- #! /bin/sh export abc=xyz autoconf how would I enable tracing just within autoconf? -- John **= Email 12 ==========================** Date: Thu, 27 Jun 2002 13:27:49 -0400 From: Henry Sobotka Subject: Re: Rebuilding \emx\lib 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)? h~ **= Email 13 ==========================** Date: Thu, 27 Jun 2002 13:48:17 +0100 From: John Poltorak Subject: Rebuilding \emx\lib EMX includes all the source for rebuilding all the components so I'm interested in rebuilding all the files in \emx\lib but I'm not sure how to go about this. I assume there is a single Makefile which I can use, but I haven't found it so far. Can anyone point out where it is if such a thing does exist? -- John **= Email 14 ==========================** Date: Thu, 27 Jun 2002 13:58:40 -0400 From: Henry Sobotka Subject: Re: Perl is too hungry? Edwin Günthner wrote: > > How do measure this? What program are you using to retrieve this > information? And again - the perl_ takes much less than the > perl. Is that different in your environment? Theseus3, Here the aout version (perl_) uses somewhat more. BTW, you'll find all kinds of details about Perl memory management in the Perl docs. h~ **= Email 15 ==========================** Date: Thu, 27 Jun 2002 14:01:22 -0400 From: Henry Sobotka Subject: Re: Perl 5.73 and perl212F.dll Michel SUCH wrote: > > Sorry, it is not perl 5.73 but 5.72! > > On Thu, 27 Jun 2002 19:05:12 +0100 (CET), Michel SUCH wrote: > > >Sometimes I have this dll crashing when running perl (for example when > >running ./configure for automake 1.6.2. > >Is this a known problem and is there a fix. > >Note: after this crash, the configure script goes on and completes, but i > >am not quite sure the automake I build is clean. Are there any crash details in config.log and/or popuplog.os2? h~ **= Email 16 ==========================** Date: Thu, 27 Jun 2002 14:27:15 +0100 From: John Poltorak Subject: Re: Patch -p On Wed, Jun 26, 2002 at 04:09:55PM +0100, csaba.raduly at sophos.com wrote: > > > On 24/06/2002 19:26:44 owner-os2-unix wrote: > > >On Mon, Jun 24, 2002 at 06:05:09PM +0100, csaba.raduly at sophos.com wrote: > [snip] > >Yes, I remember that - SLICEM.CMD - excellent utility! > > > > Heh, I thought it was all mine :-) Took me some time to find it: > I was searching for files with a .pl extension. > > Try this (renamed to .cmd, put it in the current dir *or* the path) > > (See attached file: diff_prefix.txt) It looks like Majordomo stripped off the attachment before sending it out although I have managed to track it down. I don't actually agree with your results in some instances, which were -p 3 for this one:- --- old/autoconf-2.53/lib/m4sugar/m4sh.m4 Thu Feb 7 15:37:54 2002 +++ gnu/autoconf-2.53/lib/m4sugar/m4sh.m4 Thu Jun 20 22:26:44 2002 at at -175,6 +175,33 at at I'm using -p 2 in this case and it works OK. What I think I need is to determine how many directory levels appear before autoconf-2.53 and add one. I don't know a simple way of doing this from within a shell script, but I'm sure there is a way. BTW what are the identifiers '+++' and '---' for? I've also seen some patch files which use '***'. -- John **= Email 17 ==========================** Date: Thu, 27 Jun 2002 14:45:29 +0100 From: John Poltorak Subject: Re: UnixOS/2 environment On Wed, Jun 26, 2002 at 08:57:35PM +0000, Lyn St George wrote: > On Wed, 26 Jun 2002 18:12:32 +0200 (CEST), Stefan Neis wrote: > > >On Tue, 25 Jun 2002, Lyn St George wrote: > > > >> "In file included from perl.h:612, > >> from os2.c:30: > >> f:/emx/include/netinet/in.h:89: parse error before `u_long' > > > >> f:/usr/include/sys/socket.h:162: parse error before `u_short' > > > >> "os2.c: In function `file_type': > >> os2.c:583: `_emx_env' undeclared (first use in this function)" > > > >Sounds like some missing include to e.g. . As to why > >it is missing for you and apparently not for others, I'm lost. > >There's been some discussion about such a problem a few weeks ago, > >but I had the impression it was fixed in the latest release candidate > >for Perl-5.8.0. > > I'm also lost. Particularly when perl 5.6.1 builds cleanly. Well I have had 5.8.0 building, but I've inadvertantly changed something and now I get errors such as:- storage size of `t' isn't known. Argghhhh!!!! > > - > Cheers > Lyn St George > +--------------------------------------------------------------------------------- > + http://www.zolotek.net .. eCommerce hosting, consulting > + http://www.os2docs.org .. some 'How To' stuff ... > +---------------------------------------------------------------------------------- -- John **= Email 18 ==========================** Date: Thu, 27 Jun 2002 15:00:34 +0100 From: csaba.raduly at sophos.com Subject: Re: Patch -p On 27/06/2002 14:27:15 owner-os2-unix wrote: [snip] > > >BTW what are the identifiers '+++' and '---' for? I've also seen some >patch files which use '***'. > I think '---' means this is the "original" and '+++' means this is the "new" file (i.e. first and second non-option argument to diff). -- 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: Thu, 27 Jun 2002 15:08:13 +0100 (BST) From: "Dave Saville" Subject: Re: ssh in X (was: Re:Emacs & X-Export) On Thu, 27 Jun 2002 12:02:01 +0100, Pete Milne wrote: > > >Stefan Neis wrote: > >> On Wed, 26 Jun 2002, Adrian Gschwend wrote: >> >> > yes I guess you don't use OpenSSH 3.x, do you? >> >> Ah yes, you're right, thanks for clarifying why I did see a >> "-X" option under Linux but not under OS/2. ;-) >> >> > Which window manager are you using? Must be a >> > shell problem on my system >> >> Well, you could try to open an OS/2-window in PM and enter your >> "ssh -X whatever" and hopefully password and some commands there, >> maybe that will work around whatever problem you currently see. >> X windows from the remote box still should make it to your XFree86 >> screen. Switching around between XFree86 and PM is a bit annoying >> of course, but if it works that would give a hint at the real >> source of the problem (I suppose openssh has some problem with >> xterm or tty handling, that's a notorious problem with code that >> hasn't been ported with the idea of supporting both PM and XFree >> session in mind). >> >> For me, this works fine with ssh-1.2.30 (whatever that exactly is) >> and it works even better with HOB-X11. :-) >> >> Regards, >> Stefan > >Please excuse me if I'm off the point, as I no longer have the start of >this thread. >What works for me is, with XFree86 running, switch back to PM, open an >OS/2 window, SSH to the remote system and do "xterm", and finally >switch back to XFree86. >I now have an Xterm window for the remote host, and can start any >application with, e.g. "emacs &" >hth >Pete > Is this not the same problem as trying to use telnet from the xterm window? ie you can't and have to use the above workaround. -- Regards Dave Saville Please note new email address dave.saville at ntlworld.com **= Email 20 ==========================** Date: Thu, 27 Jun 2002 16:42:25 +0100 From: John Poltorak Subject: UnixOS/2 Build System 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 You should be able to access it at 213.152.37.92 using a username of 'unixos2'. The framework will be in /pub/unixos2/build_system. To start with I just want to test the overall framework and get some feedback. It's set up for my environment at the moment, so a little editing will be likely, but I'm trying to keep that down to a minimum. 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. It's as well to try Autoconf and Automake first as they are likely to be required by various apps. -- John **= Email 21 ==========================** Date: Thu, 27 Jun 2002 17:10:43 +0100 From: John Poltorak Subject: Re: Rebuilding \emx\lib On Thu, Jun 27, 2002 at 05:25:01PM +0200, Stefan Neis wrote: > On Thu, 27 Jun 2002, John Poltorak wrote: > > > EMX includes all the source for rebuilding all the components so I'm > > interested in rebuilding all the files in \emx\lib but I'm not sure how to > > go about this. I assume there is a single Makefile which I can use, but I > > haven't found it so far. > > EMX comes with an extensive docuemtnation on how to build the whole thing > from scratch, have a look in the emx/doc directory. ;-) 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. > Regards, > Stefan > -- > Micro$oft is not an answer. It is a question. The answer is 'no'. > -- John **= Email 22 ==========================** Date: Thu, 27 Jun 2002 17:12:48 -0400 From: Edwin =?iso-8859-1?Q?G=FCnthner?= Subject: Re: Perl is too hungry? 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 ... **= Email 23 ==========================** Date: Thu, 27 Jun 2002 17:24:06 -0400 From: Edwin =?iso-8859-1?Q?G=FCnthner?= Subject: Re: Perl is too hungry? Henry Sobotka wrote: > Theseus3, Here the aout version (perl_) uses somewhat more. Just a thought: which version of OS/2 are you using? **= Email 24 ==========================** Date: Thu, 27 Jun 2002 17:25:01 +0200 (CEST) From: Stefan Neis Subject: Re: Rebuilding \emx\lib On Thu, 27 Jun 2002, John Poltorak wrote: > EMX includes all the source for rebuilding all the components so I'm > interested in rebuilding all the files in \emx\lib but I'm not sure how to > go about this. I assume there is a single Makefile which I can use, but I > haven't found it so far. EMX comes with an extensive docuemtnation on how to build the whole thing from scratch, have a look in the emx/doc directory. ;-) Be warned that it requires some unusual tools like "dmake" and Microsoft's masm (IIRC). Regards, Stefan -- Micro$oft is not an answer. It is a question. The answer is 'no'. **= Email 25 ==========================** Date: Thu, 27 Jun 2002 17:39:36 -0400 From: Thomas Dickey Subject: Re: Texinfo bug On Thu, Jun 27, 2002 at 08:30:17PM +0100, 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 - I have texinfo 4.0 on Linux, and regenerating the info files gives those messages. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 26 ==========================** Date: Thu, 27 Jun 2002 18:03:48 -0400 From: Henry Sobotka Subject: Re: Perl is too hungry? Edwin Günthner wrote: > > Strange, we are using theseus4 and get something different. Actually theseus5.sys with theseus3.exe here. > Just a thought: which version of OS/2 are you using? CP1, but it's essentially the same on my WSeB box. h~ **= Email 27 ==========================** Date: Thu, 27 Jun 2002 19:05:12 +0100 (CET) From: "Michel SUCH" Subject: Perl 5.73 and perl212F.dll Sometimes I have this dll crashing when running perl (for example when running ./configure for automake 1.6.2. Is this a known problem and is there a fix. Note: after this crash, the configure script goes on and completes, but i am not quite sure the automake I build is clean. ---------------------------- Michel SUCH TEAM OS/2 FRANCE ICQ # 51654489 **= Email 28 ==========================** Date: Thu, 27 Jun 2002 19:38:18 +0100 (CET) From: "Michel SUCH" Subject: Re: Perl 5.73 and perl212F.dll Sorry, it is not perl 5.73 but 5.72! On Thu, 27 Jun 2002 19:05:12 +0100 (CET), Michel SUCH wrote: >Sometimes I have this dll crashing when running perl (for example when >running ./configure for automake 1.6.2. >Is this a known problem and is there a fix. >Note: after this crash, the configure script goes on and completes, but i >am not quite sure the automake I build is clean. >---------------------------- >Michel SUCH TEAM OS/2 FRANCE >ICQ # 51654489 > > > ---------------------------- Michel SUCH TEAM OS/2 FRANCE ICQ # 51654489 **= Email 29 ==========================** Date: Thu, 27 Jun 2002 19:59:26 +0100 From: John Poltorak Subject: Makeinfo does not support LFNs 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? -- John **= Email 30 ==========================** Date: Thu, 27 Jun 2002 20:29:08 +0000 From: "Lyn St George" Subject: Re: Makeinfo does not support LFNs 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? There is 'long.cmd', (as well as 'omflibs.cmd'), but I thought that only converted existing names. Perhaps it's worth a look inside of .. >>-- >John > > > > - Cheers Lyn St George +--------------------------------------------------------------------------------- + http://www.zolotek.net .. eCommerce hosting, consulting + http://www.os2docs.org .. some 'How To' stuff ... +---------------------------------------------------------------------------------- **= Email 31 ==========================** Date: Thu, 27 Jun 2002 20:30:17 +0100 From: John Poltorak Subject: Texinfo bug 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? -- John **= Email 32 ==========================** Date: Thu, 27 Jun 2002 20:36:14 -0800 From: "Dave and Natalie" Subject: Re: Building Perl with VisualAge? 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. Dave **= Email 33 ==========================** Date: Thu, 27 Jun 2002 20:56:46 -0800 From: "Dave and Natalie" Subject: Re: Makeinfo does not support LFNs 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 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 **= Email 34 ==========================** Date: Thu, 27 Jun 2002 23:08:19 +0200 From: Andreas Buening Subject: Re: Texinfo bug 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. 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. **= Email 35 ==========================** Date: Thu, 27 Jun 2002 23:08:59 +0200 From: Andreas Buening Subject: Re: Makeflags John Poltorak wrote: > > On Wed, Jun 26, 2002 at 05:59:19PM +0100, csaba.raduly at sophos.com wrote: > > > > John, what happens if you add the following to the makefile: > > > > say: > > at echo AR is now '$(AR)' > > > > then do > > > > export AR=emxomfar > > make say > > It says:- > > AR is now emxomfar > > But having the environment variable set does not appear to have the > desired effect. The only thing I have found which works is to run:- > > make AR=emxomfar > > at the command line. I don't understand what is going on here at all. I currently don't remember the concrete implementation but the idea is the following: 1) You set your environment _and_ you run ./configure. Your special names for *FLAGS, AWK, CC, etc. are incorporated into the Makefiles. 2) You run "make" _afterwards_. This can be two weeks or three reboots later. make has to use your configuration at the time of configuring, no matter what your current environment may be. If you really want to change the environment for make you have to specify it explicitely with the make command. This is to keep your build reproducable. Unfortunately, most configure scripts ignore $AR (unlike CC, AWK, RANLIB). Therefore you must say "make AR=emxomfar". If you really want that configure takes care of $AR then you must add the line "AC_CHECK_PROG(AR, ar, ar, ar)" to configure.in. I.e.: export RANLIB=blurb ./configure make works, but export AR=emxomfar ./configure make normally does not. 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.