From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Sun, 30 Nov 2003 14:16:11 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 256 ************************************************** Saturday 29 November 2003 Number 256 ************************************************** Subjects for today 0 UnixOS2 Contact Form : ruppgd at telusplanet.net 1 Re: UnixOS/2 distro : IanM" 2 Re: UnixOS/2 distro : Jeff Robinson 3 Re: UnixOS/2 distro : IanM" 4 Re: UnixOS/2 distro : Andrew MacIntyre 5 Re: Kismet : Lewis G Rosenthal 6 curses! this libncurses thing... : Lewis G Rosenthal 7 Re: UnixOS/2 distro : Andreas Buening 8 Re: curses! this libncurses thing... : Henry Sobotka **= Email 0 ==========================** From: ruppgd at telusplanet.net Subject: UnixOS2 Contact Form This is a copy of what you submitted at http://unixos2.com/ Thank you for your feedback/comments, if you have a problem, we will try to respond as quickly as we can. *************************************** From: Gary Rupp email: ruppgd at telusplanet.net Country: Comments: - Hi UnixOS2 I would like to upgrade some parts of the base to get packages m4 1.4, autoconf 2.57 and automake 1.76 installed. I tried following the idea of 1) unzip to x:\install and then to see if there is a DOINST cmd, like what existed about a year or so ago. It appears that this has changed. Is there some doc on how to get these packages upgraded to the uxos2 base? Thanks Gary Rupp *************************************** Your time is appreciated. Regards UnixOS/2 Crew Form submitted from http://unixos2.com/pages/contact.html. The remote IP address is 198.53.58.95. **= Email 1 ==========================** Date: Sun, 30 Nov 2003 04:22:33 +1100 (EDT) From: "IanM" Subject: Re: UnixOS/2 distro Hi Andreas > 1. Technical infrastructure > > A server on which we can store the sources, binaries and everything > else of the UnixOS/2 distro. We already have this (unixos2, os2site). > Which one do we finally want to use? unixos2.com > A useful directory structure (.../unixos2/0.1-stable, > .../unixos2/0.1-beta, ...) and a maintainer for it (Ted, Ian?). Happy to maintain it, also happy for Ted to maintain it and I'll simply mirror it, it sort of depends, Ted is probably like me, if the original is on os2ports the Ted, if the original is on unixos2.com then me, unixos2.com is ment to be the home of it though, or at least the final resting place. > FTP access for package maintainers so that they can modify their > own stuff. An incoming directory for small contributions. Can do that, anyone still having problems accessing ? > 2. Distribution maintainance > > After a package maintainer has uploaded his new source (and > binary) release, we need someone who arranges the package in the > UnixOS/2 tree (not every package maintainer can know what belongs > to which place), recompiles the package if necessary, creates > the PKGINFO files, decides when the new UnixOS/2 beta reaches > stable status, and so on. (John?) Very important, otherwise we end up with pieces everywere, as we currently have. > 5. Documentation > > Someone who writes html-pages. (Jeff?) > Everytime task 4 leads to a new package or to a new version of > a package, someone has to document this. I could imagine some > web structure like this: > > [The main page] > - Installing UnixOS/2 -> link to the install page > - The UnixOS/2 packages -> link to the package page > - Environment variables -> link ... > - Known problems -> link ... > - FAQ -> ... > - TODO list (e.g., which package needs a maintainer) -> ... This is good, so is the rest of what you have written. > Since we have so (too) many different gcc releases, libraries > with/without features like fork and friends, I suggest the > following: We create a gcc-2_8_1 package which will be installed > into /usr/local/appl/gcc-2_8_1. It will be called by a gcc-2_8_1.cmd > script somewhere in the path, i.e., by setting CC=gcc-2_8_1 before > calling ./configure. Why? > Because 2.8.1 is the last real emx release, it doesn't have any > fork/socket/whatever problems, no gcc*.dll, no other funny stuff. > It can serve as reference for compiling packages. If anything > works with 2.8.1 but not with newer versions then it has to be > considered as a bug and has to be fixed. I also suggest to compile > all programs of the UnixOS/2 distro 0.1 by using 2.8.1, just to > have a standard. Programs which need newer gcc versions (e.g. C++ > programs) don't make it into release 0.1 stable but can be put > into 0.2 beta. It's just to keep the "core" release 0.1 clean. I keep downloading the latest beta's of GCC, waiting to upgrade the os2site/unixos2 versions but they seem to present more problems, dont know if its me, of a gnomes working away changing libs or something. I like the idea of standising on maybe v2.8.1. but keep for example v3.xx on the side with notes that its not guaranteed but try it if needed sort of thing, and let us know how you went :) I've all but given up on later releases to compile BIND, as one missing or wrong inc/lib leads to another, to another, then it compiles perfectly but doesnt run properly, I've had a smoother run with v2.8.1 & the EMX tree. It's becoming difficult for various people to keep track of what compiled ok under what version with some of these programs. > Does this sound reasonable to you? yes > P.S.: I apologize to you for this far too long email. I think its needed, we all tend to wonder off, so its good that someone occasionally pulls the threads towards one goal again. Gee's, I need a normal job. Night all. Cheers IanM http://www.os2site.com/ Tough choice in the 90's: Upgrade the computer, or buy more beer. **= Email 2 ==========================** Date: Sun, 30 Nov 2003 08:49:54 -0600 From: Jeff Robinson Subject: Re: UnixOS/2 distro Andrew MacIntyre wrote: > On Sun, 30 Nov 2003, IanM wrote: > > >>I keep downloading the latest beta's of GCC, waiting to upgrade >>the os2site/unixos2 versions but they seem to present more problems, >>dont know if its me, of a gnomes working away changing libs or something. >> >>I like the idea of standising on maybe v2.8.1. but keep for example v3.xx >>on the side with notes that its not guaranteed but try it if needed sort of >>thing, and let us know how you went :) > > >>From my experience with Python, gcc 2.8.1 is still a very effective C > compiler, especially in the context of EMX. I have found little value, > even with optimisation, with later releases. > > The problem comes with C++ code, where standardisation creep means that > 3.2.x is probably the baseline gcc release required at the moment. > > Regards, > Andrew. > My vote would be for gcc 3.2.1 to be "baseline" or at least included, the same way that the UX2BS gives you a 'shell' for each one... just as it is a more modern compiler. I know when it comes to 3.2.2 I can't compile some of the software I've written as some of the features don't appear to be recognized by the compiler yet. I also believe that Mozilla requires the 3.2.x series of compilers now, which would be one of the really big test-projects if we can get it to compile with the UnixOS2 tools! Jeff -- ---------------- Whatza JamochaMUD? http://jamochamud.anecho.mb.ca Or other stuff: http://www.anecho.mb.ca/~jeffnik ----------------------------------------------------------- **= Email 3 ==========================** Date: Sun, 30 Nov 2003 12:20:46 +1100 (EDT) From: "IanM" Subject: Re: UnixOS/2 distro Hi Ted/Everyone > > Actually os2ports has nothing to do with unixos2.com anymore. It was > > just a temporary home till unixos2.com got sorted out. > > > .. and it's suffering a serious case of neglect too. Probably the only > thing you can rely on is the /os2/unix/devtools being current. Need input.... Putting stuff in /nonunixos2 is easy but thats not what we really want. I do want to have it so that if someone runs Johns wget ftp://unixos2: at unixos2.com/pub/unixos2/build_system/lib/ux2_bootstrap.cmd that they will get all they need. As far as updating things in the /unixos2 tree, I can copy over anything from the /binary tree. Anyone who has access to /binary, or /source also has access to /incoming. If anyone wants to tell me what files go were, or were they come from and I'll get started tonight when I get home from work (midnight my time), also happy to do it when ever someone sends/emails me stuff/URL's etc. Not sure what type of access I've given to everyone for /incoming but I can make it so it simply requires user=unixos2, which will cut out most of the rubbish uploads. Anyone who wants to be a maintainer of a port, let me know and I will creat/give you access to directies under /binary /source, and any other relevant directories needed. Cheers IanM http://www.os2site.com/ B Gates, the worlds greatest salesman, who else could sell so many broken windows ? **= Email 4 ==========================** Date: Sun, 30 Nov 2003 12:50:19 +1100 (EST) From: Andrew MacIntyre Subject: Re: UnixOS/2 distro On Sun, 30 Nov 2003, IanM wrote: > I keep downloading the latest beta's of GCC, waiting to upgrade > the os2site/unixos2 versions but they seem to present more problems, > dont know if its me, of a gnomes working away changing libs or something. > > I like the idea of standising on maybe v2.8.1. but keep for example v3.xx > on the side with notes that its not guaranteed but try it if needed sort of > thing, and let us know how you went :) From my experience with Python, gcc 2.8.1 is still a very effective C compiler, especially in the context of EMX. I have found little value, even with optimisation, with later releases. The problem comes with C++ code, where standardisation creep means that 3.2.x is probably the baseline gcc release required at the moment. Regards, Andrew. -- Andrew I MacIntyre "These thoughts are mine alone..." E-mail: andymac at bullseye.apana.org.au (pref) | Snail: PO Box 370 andymac at pcug.org.au (alt) | Belconnen ACT 2616 Web: http://www.andymac.org/ | Australia **= Email 5 ==========================** Date: Sun, 30 Nov 2003 19:35:37 -0500 From: Lewis G Rosenthal Subject: Re: Kismet Sorry for the month-long lag in responses to this thread, John! Juergen & I are working on this one, trying to see what can be done under UX2BS. The only reference I have for Kismet as of now is the link in my original post to this thread. On 10/30/2003 10:21 am, John Poltorak thus wrote : >On Thu, Oct 30, 2003 at 02:56:10PM +0100, Adrian Gschwend wrote: > > >>On Thu, 30 Oct 2003 14:12:00 +0000, John Poltorak wrote: >> >> >> >>>What is it? And why would I want to use it? >>> >>> >>It's like a tcpdump for wireless systems (802.11b), it can find a lot >>of details about wireless systems. >> >>big fun if you have such cards :-) >> >> > >I've had a couple of such cards for almost two years, along with a >wireless router. > >Maybe I should investigate... Is there a good URL for reference? > > > >>cu >> >>Adrian >> >> >>-- >>Adrian Gschwend >> at netlabs.org >> >>ktk [a t] netlabs.org >>------- >>Free Software for OS/2 and eCS >>http://www.netlabs.org >> >> >> > > > > -- Lewis ------------------------------------------------------------ Lewis G Rosenthal, CNA Rosenthal & Rosenthal Accountants / Network Consultants New York / Northern Virginia www.2rosenthals.com Team OS/2 / NetWare Users International www.novell.com ------------------------------------------------------------ This OS/2 system (Apollo) uptime is 0 days 04:27 hours and 32 seconds **= Email 6 ==========================** Date: Sun, 30 Nov 2003 19:53:51 -0500 From: Lewis G Rosenthal Subject: curses! this libncurses thing... Does anybody have a complete ncurses build, including libncurses? Naturally, in my frustration, I decided I'd build ncurses myself, but of course, this brought along its own set of problems... It seems that all the distros of ncurses I've seen do not include libncurses. Could someone explain to me why and what the difference is between ncurses and libncurses, anyway? Sorry to sound like such a novice...it seems the farther I get into this whole porting thing, the less I feel I really know!! Anyway, hope everyone here (at least those in the States) had a good Thanksgiving. And for those outside the States, I hope everyone had at the very least a good weekend. :-) -- Lewis ------------------------------------------------------------ Lewis G Rosenthal, CNA Rosenthal & Rosenthal Accountants / Network Consultants New York / Northern Virginia www.2rosenthals.com Team OS/2 / NetWare Users International www.novell.com ------------------------------------------------------------ This OS/2 system (Apollo) uptime is 0 days 04:42 hours and 54 seconds **= Email 7 ==========================** Date: Sun, 30 Nov 2003 21:20:33 +0100 From: Andreas Buening Subject: Re: UnixOS/2 distro Jeff Robinson wrote: [snip] > My vote would be for gcc 3.2.1 to be "baseline" or at least included, > the same way that the UX2BS gives you a 'shell' for each one... just as > it is a more modern compiler. I know when it comes to 3.2.2 I can't > compile some of the software I've written as some of the features don't > appear to be recognized by the compiler yet. I suggest that we put gcc 2.8.1 into /usr/local/appl/ which means that it is an extra, not a standard package. To be true I have no idea which gcc version we should use as "default". If I unterstood correctly, then the latest gcc has an incompatible omf format for .lib libraries. So which library style do we want to use as "standard"? > I also believe that Mozilla requires the 3.2.x series of compilers now, > which would be one of the really big test-projects if we can get it to > compile with the UnixOS2 tools! If anybody needs 3.2.x, he is free to add also a package for this version. Bye, Andreas **= Email 8 ==========================** Date: Sun, 30 Nov 2003 22:12:27 -0500 From: Henry Sobotka Subject: Re: curses! this libncurses thing... Lewis G Rosenthal wrote: > > It seems that all the distros of ncurses I've seen do not include > libncurses. Could someone explain to me why and what the difference is > between ncurses and libncurses, anyway? Normally nothing except for the name. On *nix systems, libraries usually have a "lib" prefix that isn't specified when linking, e.g. "gcc foo.c -lbar" will make the linker look for libbar.a. On OS/2, the same command tells the linker to look for bar.a. So we have socket.a instead of libsocket.a, ncurses.a instead of libncurses.a etc. h~