From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Fri, 29 Mar 2002 04:20:49 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 178 ************************************************** Thursday 28 March 2002 Number 178 ************************************************** Subjects for today 1 Re: Porting Joe's Own Editor (JOE) : Thomas Dickey 2 Re: Porting Joe's Own Editor (JOE) : Thomas Dickey 3 Re: OGG123 strangeness : John Poltorak 4 Re: Saving Audio Stream : Michael Taylor 5 Re: Re: Building Perl.exe as a test of manhood ;-) : Henry Sobotka 6 Re: Re: Building Perl.exe as a test of manhood ;-) : John Poltorak 7 Re: Porting Joe's Own Editor (JOE) : John Poltorak 8 Re: OGG123 strangeness : Brian Havard" 9 Re: Re: Building Perl.exe as a test of manhood ;-) : John Poltorak 10 Re: iconv.a : John Poltorak 11 Re: iconv.a : John Poltorak 12 Re: Porting Joe's Own Editor (JOE) : mlaitio 13 Re: iconv.a : Andreas Buening 14 Re: iconv.a : Andrew Zabolotny" 15 Re: iconv.a : Andrew Zabolotny" 16 Re: iconv.a : John Poltorak 17 Re: Re: Building Perl.exe as a test of manhood ;-) : mlaitio **= Email 1 ==========================** Date: Fri, 29 Mar 2002 07:45:30 -0500 From: Thomas Dickey Subject: Re: Porting Joe's Own Editor (JOE) On Thu, Mar 29, 2001 at 01:27:24PM -0800, mlaitio wrote: > > > > > >Here's the termcap entry that I used: > >OS2CMD:\ > > :co#80:li#25:\ > > :cm=\E[%i%d;%dH:\ > > :nd=\E[C:\ > > :so=\E[1;35;44m:se=\E[0;44m:\ > > :us=\E[1;31;44m:ue=\E[0;44m:\ > > :mb=\E[5m:md=\E[1m:mr=\E[7m:me=\E[0;44m:\ > > :ti=\E[0;44m:te=\E[0m:\ > > > What are these termcaps and their entries? I know that there exist > termcaps like > ANSI, CYGWIN, OS2TERM, etc. and certain programs requites that certain > termcap is defined for the TERM-variable... But that's all what I can > understand... > Could somebody give short tutorial to termcaps, what will following thing > define forexample: > > :nd=\E[C:\ There's an O'Reilly book on termcap and terminfo, which is useful. For practical purposes (if you're not writing a library to implement termcap or terminfo), the terminfo manpage gives enough information to work with. For example, "nd" (a termcap name) is listed: cursor_right cuf1 nd non-destructive space (move right one space) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 2 ==========================** Date: Fri, 29 Mar 2002 08:24:32 -0500 From: Thomas Dickey Subject: Re: Porting Joe's Own Editor (JOE) On Fri, Mar 29, 2002 at 03:11:02PM -0800, mlaitio wrote: > Did that, and > > http://www.hmug.org/man/5/termcap.html > > offered a good answer. Thanks... that one's interesting (to me) since it documents Darwin. However, the link on that page to curses points to ncurses (which I understood was not the default for Darwin - like EMX it came with BSD curses - perhaps that's changed). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net **= Email 3 ==========================** Date: Fri, 29 Mar 2002 10:12:13 +0000 From: John Poltorak Subject: Re: OGG123 strangeness On Fri, Mar 29, 2002 at 02:16:24PM +1000, Brian Havard wrote: > On Thu, 28 Mar 2002 20:33:25 +0000, John Poltorak wrote: > > >Today I had BBC Radio 4 playing via ogg123 for around an hour with hardly > >any CPU usage according to the system activity monitor, but subsequently > >the same URL pegs CPU usage to 100%. > > > > > >What could explain such a variation? > > There's a bug in the buffering routines that puts 1 of the threads in a > non-blocking (& therefore CPU eating) loop when the buffer gets low. I > should have a fix shortly. I've found the use of '-b 500' makes it work fine. > -- > ______________________________________________________________________________ > | Brian Havard | "He is not the messiah! | > | brianh at kheldar.apana.org.au | He's a very naughty boy!" - Life of Brian | > ------------------------------------------------------------------------------ -- John **= Email 4 ==========================** Date: Fri, 29 Mar 2002 10:22:12 +1100 From: Michael Taylor Subject: Re: Saving Audio Stream According to ogg123.txt use "-d wav" or "-d raw" John Poltorak wrote: > > Is it possible to save Streamed Audio as a file? > > ie. can I do something like? :- > > ogg123 | tee audio.dat > > -- > John -- Regards, Mick -- ----------------------------------------------------------------------- Michael Taylor miket at pcug.org.au ----------------------------------------------------------------- Home Page: http://www.geocities.com/miket5au/ http://users.bigpond.net.au/miket5au ----------------------------------------------------------------- ----------------------------------------------------------------------- **= Email 5 ==========================** Date: Fri, 29 Mar 2002 10:53:22 -0500 From: Henry Sobotka Subject: Re: Re: Building Perl.exe as a test of manhood ;-) John Poltorak wrote: > > Is there any chance of you doing a special build with? :- > > Configure -des -D prefix=c:/usr/lib Sure, if I get that far. My priorities are straightening out the fork() problem, getting a gcc 3.x build working, and doing ~12 hours of work that have shortened the weekend. > Whatever drive letter is selected will not please everyone. The default is > F: which caused me all sorts of problems when I first installed Perl. Actually, if prefix isn't specified, the default is whatever drive the source code is on. h~ **= Email 6 ==========================** Date: Fri, 29 Mar 2002 11:57:19 +0000 From: John Poltorak Subject: Re: Re: Building Perl.exe as a test of manhood ;-) On Tue, Mar 26, 2002 at 11:07:25AM -0500, Henry Sobotka wrote: > Edwin Günthner wrote: > > > > Uups. And perl_ isn't part of your package if I remember that correctly. > > Any plans / time to build a new package and drop it at Hobbes? > > Yes. I should get a chance to tackle it over the upcoming long weekend. Is there any chance of you doing a special build with? :- Configure -des -D prefix=c:/usr/lib and just dumping it somewhere on:- http://www.elzahir.org/ UnixOS/2 really needs a PERL package as it seems to be a fundamental building block, and try as I do, I'm not going to get anywhere close to creating a build as good as yours. > h~ -- John **= Email 7 ==========================** Date: Fri, 29 Mar 2002 12:47:33 +0000 From: John Poltorak Subject: Re: Porting Joe's Own Editor (JOE) On Thu, Mar 29, 2001 at 01:27:24PM -0800, mlaitio wrote: > > > > > >Here's the termcap entry that I used: > >OS2CMD:\ > > :co#80:li#25:\ > > :cm=\E[%i%d;%dH:\ > > :nd=\E[C:\ > > :so=\E[1;35;44m:se=\E[0;44m:\ > > :us=\E[1;31;44m:ue=\E[0;44m:\ > > :mb=\E[5m:md=\E[1m:mr=\E[7m:me=\E[0;44m:\ > > :ti=\E[0;44m:te=\E[0m:\ > > > What are these termcaps and their entries? I know that there exist > termcaps like > ANSI, CYGWIN, OS2TERM, etc. and certain programs requites that certain > termcap is defined for the TERM-variable... But that's all what I can > understand... > Could somebody give short tutorial to termcaps, what will following thing > define forexample: > > :nd=\E[C:\ Try a search for 'man termcap' on Google. > Mika > > -- John **= Email 8 ==========================** Date: Fri, 29 Mar 2002 14:16:24 +1000 (EST) From: "Brian Havard" Subject: Re: OGG123 strangeness On Thu, 28 Mar 2002 20:33:25 +0000, John Poltorak wrote: >Today I had BBC Radio 4 playing via ogg123 for around an hour with hardly >any CPU usage according to the system activity monitor, but subsequently >the same URL pegs CPU usage to 100%. > > >What could explain such a variation? There's a bug in the buffering routines that puts 1 of the threads in a non-blocking (& therefore CPU eating) loop when the buffer gets low. I should have a fix shortly. -- ______________________________________________________________________________ | Brian Havard | "He is not the messiah! | | brianh at kheldar.apana.org.au | He's a very naughty boy!" - Life of Brian | ------------------------------------------------------------------------------ **= Email 9 ==========================** Date: Fri, 29 Mar 2002 14:26:06 +0000 From: John Poltorak Subject: Re: Re: Building Perl.exe as a test of manhood ;-) On Thu, Mar 29, 2001 at 03:00:23PM -0800, mlaitio wrote: > John Poltorak wrote: > > >On Tue, Mar 26, 2002 at 11:07:25AM -0500, Henry Sobotka wrote: > > > >>Edwin Günthner wrote: > >> > >>>Uups. And perl_ isn't part of your package if I remember that correctly. > >>>Any plans / time to build a new package and drop it at Hobbes? > >>> > >>Yes. I should get a chance to tackle it over the upcoming long weekend. > >> > > > >Is there any chance of you doing a special build with? :- > > > >Configure -des -D prefix=c:/usr/lib > > > >and just dumping it somewhere on:- > > > >http://www.elzahir.org/ > > > >UnixOS/2 really needs a PERL package as it seems to be a fundamental > >building block, and try as I do, I'm not going to get anywhere close to > >creating a build as good as yours. > > > I hope that you will not put this drive-letter fixed version to the > UnixOS2 distribution, as I am using totally different directory for the > OS/2-tools. (C is only small fat-partition which I can build very fastly). Whatever drive letter is selected will not please everyone. The default is F: which caused me all sorts of problems when I first installed Perl. There are ways round this though. You can either set n environment variable or you could patch the binary... I think it is only the DLL which holds all the hard coded paths. I wrote a small REXX program which could be used for patching and I think this is something which could be incorporated into the installation process at some point. > What I could try to do (slowly during the next few weeks) is to setup > minimal parts of the UnixOS2-tools and gcc 3.03 (I would like to install > also this in a way that it is integrated to unixos2-directory structure) > to a totally fresh warp-machine and start testing autoconf & make > combination for building and installing some UnixOS2-extra tools and > libraries above that. The amount of time I spend at my home where I > have OS2 available is very limited, there are some times weeks when I do > not have time to read mails from my OS/2-mail-boxes, but in my spare > time I really would like to help testing to get UnixOS2-distribution > usable. Great! > Do you have any suggestions > > 1) What is the minimum set of tools I should install from the UnixOS2 > binary-packages to get started. Depends on what you want to do... If you want to build apps, you will need:- EMX/GCC gzip tar sed grep awk Text Utils Shell Utils File Utils patch Perl, Diff, Find are also useful, but I'm not sure if they are required. > 2) Should I try to use bash or the newest PDKSH? (Is the newest pdksh > bundlet to UnixOS2-distro?) as a sh? If I have understood correctly, OS2 > bash maintainer is more willing to fix > bugs I may encounter during the UnixOS2 build operations than OS/2 > pdksh-maintainer. PDKSH is not included in any UnixOS/2 package yet. Slackware, which UnixOS/2 is modelled on uses KSH93, the original Korn Shell. I was hoping to get an OS/2 port of that, and still may do, but it isn't available yet. The question of which SHELL to use still isn't satisfactorily resolved. I tend to prefer BASH (2.03) rather than PDKSH, but it varies depending on which app is being built. Perl won't build using BASH, neither will NCURSES, but I have problems using PDKSH with a number of apps. > 3) Is there any fixes I should apply top of the newest autoconf? (I > assume that I will download autoconf from the gnu's official ftp-site) Not at the moment. There is an OS/2 port of v2.50 which I was very happy with but I'm not sure how much of that port is redundant because of improvements in the latest version of Autoconf. Stay tuned... > Sorry, that I can not give any fast help, but as I said, the time I have > access to OS2 is currently very limited. But if there is some easily > separatable work I could do in small parts, then I believe I could be > helpful. Any feedback is always welcome. There are actually a number of old apps which require an 'owner'. Ie. an OS/2 port was made a long time ago but the maintainer has disappeared or left the OS/2 scene. Often these apps have remained without any major changes anyway so we are not missing out, but it's always useful to have someone looking after them in case an update does arrive. I'm thinking specifically about apps such as DIFF, FIND, CPIO, FLEX, ASH etc. > Mika -- John **= Email 10 ==========================** Date: Fri, 29 Mar 2002 14:33:25 +0000 From: John Poltorak Subject: Re: iconv.a On Fri, Mar 29, 2002 at 05:29:23PM +0300, Andrew Zabolotny wrote: > ... in continuation of next message: > > Oh sorry, I just have noticed - I already have separated iconv from gettext. You > can find it in the same place where gettext 0.11.1 binary distribution is - > http://195.131.97.220:9000/zap/os2/iconv-0.1.0.zip > > But it does not contain yet the iconv tool - just the iconv binary library and > sources/makefile. Andy, Can you check this zipfile? It looks to be missing a few files. > > Greetings, > _\ndy > > -- John **= Email 11 ==========================** Date: Fri, 29 Mar 2002 14:43:34 +0000 From: John Poltorak Subject: Re: iconv.a On Fri, Mar 29, 2002 at 05:21:49PM +0300, Andrew Zabolotny wrote: > Hello! > > I have noticed there is a discussion about gettext/iconv.a here. Sorry for > late reply, I'm quite busy lately. > > First, it depends which version of gettext you are building. I'm particularly interested in updating INTL.DLL. If you look at the OS2LIBS package here (if you can get through) :- ftp://unixos2.com/pub/unixos2/unixos2-current/unixos2/a1 you will see an INTL.DLL on which you can run BLDLEVEL and see:- Build Level Display Facility Version 5.59.105 Mar 15 1999 (C) Copyright IBM Corporation 1993-1999 Signature: at #UX2:0.10.39.0# at INTL - GNU intl library 0.10.39 Vendor: UX2 Revision: 0.10.39.0 File Version: 0.10 Description: INTL - GNU intl library 0.10.39 This is the sort of signature I would like to get into all programs in the UnixOS/2 distro. Currently this needs to be updated to work with GCC v3.0.3. > Greetings, > _\ndy > > -- John **= Email 12 ==========================** Date: Fri, 29 Mar 2002 15:11:02 -0800 From: mlaitio Subject: Re: Porting Joe's Own Editor (JOE) Did that, and http://www.hmug.org/man/5/termcap.html offered a good answer. Thanks... Mika > > >Try a search for 'man termcap' on Google. > > >>Mika >> >> > **= Email 13 ==========================** Date: Fri, 29 Mar 2002 17:10:29 +0100 From: Andreas Buening Subject: Re: iconv.a John Poltorak wrote: > > On Thu, Mar 28, 2002 at 11:22:48PM +0100, Andreas Buening wrote: [snip] > > _OS/2_ iconv (by Andrew Zabolotny, I guess) that is intended > > to be used with that gettext versions. If you're trying > > to get _GNU_ iconv working instead you should know that > > That version is here:- > > http://195.131.97.220:9000/zap/os2/iconv%2d0.1.0.zip > > Why don't you check it out and tell me if you notice anything about it? Hmm, looks like some headers are missing. Okay, I guess I got your point. The good news is I think we could remove the included iconv.h and use iconv.h from the GNU iconv package to avoid confusion. However, I don't think it would help if you get GNU iconv working. If I remember those docs correctly they don't want to add any further charsets which you would need for full OS/2 charset support for gettext. In my opinion before we can "fix" that small iconv lib we have to define first how we expect this (and also other packages) should behave. Which prerequisites do we require? The README says gcc 3.x which sounds somewhat oversized. Some extra header files? What should happen if those are not present? Using some replacement code (may lead to autoconf)? What is the output? Which compiler flags? A static/import .a/.lib library or even four of them to maximize confusion? Do we require that emx, any gcc version, some default unix tools, GNU make and maybe some other unixos2 packages have to be sufficient to build a package? Or do we also allow other tools like nmake, watcom, vac? Btw. do you already have a unixos2-check script that tests your build environment? I have some ideas how this could be implemented. 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 14 ==========================** Date: Fri, 29 Mar 2002 17:21:49 +0300 From: "Andrew Zabolotny" Subject: Re: iconv.a Hello! I have noticed there is a discussion about gettext/iconv.a here. Sorry for late reply, I'm quite busy lately. First, it depends which version of gettext you are building. At the time version 0.11.1 has been released the OS/2 makefile (and the OS/2 port in general) was _broken_. I have submitted the required patches to Bruno Haible (the maintainer) and I hope the next version will be (finally) compilable. I have the "fixed gettext 0.11.1" binary distribution at hand, but don't remember if I have posted it anywhere. In any case, you can find it at http://195.131.97.220:9000/zap/os2/. Note that the binary distribution does not contain any patches. I have sent them all to the maintainer and hope they will be included with the next release. The iconv library will be included (for the beginning) inside the gettext/os2/iconv directory. There will be a separate makefile there: you will have to cd there first and run "make" (the official 0.11.1 distribution did not contained a makefile for libiconv - the maintainer forgot to put it there). Later I plan to release libiconv (non-GNU) as a separate package, with a "iconv" tool included (command line format compatible with its GNU counterpart). Then you run "make install" and the iconv.a, iconv_s, iconv.h, iconv.dll files will be copied to their respective locations. Finally, you cd one level up and build the gettext library. You won't have to run "configure" since that makefile will generate automatically the missing header files (which are usually built by configure). Hope this helps. Greetings, _\ndy **= Email 15 ==========================** Date: Fri, 29 Mar 2002 17:29:23 +0300 From: "Andrew Zabolotny" Subject: Re: iconv.a ... in continuation of next message: Oh sorry, I just have noticed - I already have separated iconv from gettext. You can find it in the same place where gettext 0.11.1 binary distribution is - http://195.131.97.220:9000/zap/os2/iconv-0.1.0.zip But it does not contain yet the iconv tool - just the iconv binary library and sources/makefile. Greetings, _\ndy **= Email 16 ==========================** Date: Fri, 29 Mar 2002 17:54:58 +0000 From: John Poltorak Subject: Re: iconv.a On Fri, Mar 29, 2002 at 05:10:29PM +0100, Andreas Buening wrote: > John Poltorak wrote: > > > In my opinion before we can "fix" that small iconv lib > we have to define first how we expect this (and also other > packages) should behave. Which prerequisites do we require? My immediate interest in iconv is because I want to update INTL.DLL. The one included ia a UnixOS/2 package does not work with gcc 3.0.3. > The README says gcc 3.x which sounds somewhat oversized. > Some extra header files? What should happen if those are > not present? Using some replacement code (may lead to > autoconf)? What is the output? Which compiler flags? > A static/import .a/.lib library or even four of them > to maximize confusion? Do we require that emx, any gcc version, > some default unix tools, GNU make and maybe some other > unixos2 packages have to be sufficient to build a package? > Or do we also allow other tools like nmake, watcom, vac? Well there do seem to be a number of ports being made using VAC, and I can see Watcom become more and more popular, so it make sense to consider how they could be incorporated into a build environment. However I think the primary focus should be on getting a sound environment in place centred on gcc and the standard GNU Build System. > > Btw. do you already have a unixos2-check script that tests > your build environment? Not at present, because I don't think we have established all the essential parts of that build environment. There are too many duplicates of REGEX and INTL as yet, and the behavior of various SHELLs is still unpredicatable. > I have some ideas how this could be implemented. Let's hear them then... > bye, > Andreas -- John **= Email 17 ==========================** Date: Fri, 29 Mar 2002 23:13:12 -0800 From: mlaitio Subject: Re: Re: Building Perl.exe as a test of manhood ;-) > > >Depends on what you want to do... >If you want to build apps, you will need:- > I would just like to help for verifying that the tools in UnixOS2 works and builds ok. I know that you have also done similar kind of work, but I thought that I could be some kind of "double-checker" or verifier for the basic stuff. Ie, if you have installation instructions for some tools, then I could try to follow them, and if I found some mistakes, I could try to correct them. If I have understood, I should maybe start things in this order... 1) Install some UnixOS2 base packages 2) Install/integrate gcc 3.03 to Unixos2-distribution 3) Install "newest" autoconf 4) Build and bash/pdksh from the UnixOS2-sources and install them to UnixOS2-distribution 5) Build and install some other basic libraries - regex - intl - zlib - ncurses - gzip - tar - sed - grep - awk - patch 6) Build and install perl 7) Build and install ??? > >There are actually a number of old apps which require an 'owner'. Ie. >an OS/2 port was made a long time ago but the maintainer has disappeared >or left the OS/2 scene. Often these apps have remained without any major >changes anyway so we are not missing out, but it's always useful to have >someone looking after them in case an update does arrive. I'm thinking >specifically about apps such as DIFF, FIND, CPIO, FLEX, ASH etc. > At least for now I can not promise for begin to be an "owner" of any of the ports, because I wont have that much time. But as I said, I would like to help in checking that things which are included are supposed to be easily buildable are really doing so and that correct versions of each tool is included to the distribution. (According to the discussion in this list during the last few weeks, there are lot of things like whether to use IconV from Andrew Zabolotny or from GNU, and how to build that from source in UnixOS2 distribution...) Mika