From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Thu, 30 Oct 2003 14:14:09 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 226 ************************************************** Wednesday 29 October 2003 Number 226 ************************************************** Subjects for today 1 Re: Kismet : John Poltorak 2 Re: Kismet : Adrian Gschwend" 3 Re: Kismet : John Poltorak 4 Re: Building Python : John Poltorak 5 Re: Building Python : Andrew MacIntyre **= Email 1 ==========================** Date: Thu, 30 Oct 2003 14:12:00 +0000 From: John Poltorak Subject: Re: Kismet On Wed, Oct 22, 2003 at 10:06:30AM +0200, Adrian Gschwend wrote: > On Wed, 22 Oct 2003 00:58:39 -0700, Lewis G Rosenthal wrote: > > > >Has anyone attempted to build Kismet (http://www.kismetwireless.net/) > >under GCC 3.2.2 as yet (it requires stdint.h and inttype.h, which appear > >to finally be included in the latest beta)? > > haven't tried but looks very interesting. Would be a cute port What is it? And why would I want to use it? > cu > > Adrian > > > -- > Adrian Gschwend > at netlabs.org > > ktk [a t] netlabs.org > ------- > Free Software for OS/2 and eCS > http://www.netlabs.org > -- John **= Email 2 ==========================** Date: Thu, 30 Oct 2003 14:56:10 +0100 (CET) From: "Adrian Gschwend" Subject: Re: Kismet 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 :-) cu Adrian -- Adrian Gschwend at netlabs.org ktk [a t] netlabs.org ------- Free Software for OS/2 and eCS http://www.netlabs.org **= Email 3 ==========================** Date: Thu, 30 Oct 2003 15:21:23 +0000 From: John Poltorak Subject: Re: Kismet 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 > -- John **= Email 4 ==========================** Date: Thu, 30 Oct 2003 20:26:13 +0000 From: John Poltorak Subject: Re: Building Python On Thu, Oct 30, 2003 at 11:43:12PM +1100, Andrew MacIntyre wrote: > You missed the warning in the "building from source" section of > README.os2emx file (in PC/os2emx) which says that make should be run from > the PC/os2emx subdirectory, not from the root of the Python source tree - Sorry about overlooking that. > ie: > > tar zxf Python-2.3.2.tar.gz > cd Python-2.3.2/PC/os2emx > make Hey, it worked! What I've notice is that the Makefile in the source package is slightly different. Should I use that one instead? > > Have you tried using Autoconf to create an OS/2-friendly configure? > > No. Last I knew, Python's configure.in was working with autoconf 2.53 and > I hadn't heard any promising noises about OS/2 versions of autoconf later > than 2.13. The configure script included in Python v2.3.2 was built with Autoconf 2.57 which I though was pretty OS/2 friendly. > configure.in will need some non-trivial changes to get an OS/2 build that: > - does the right thing with threads; > - sets up the core DLL and the associated import libraries correctly; and > - supports dynamicly loadable extensions viably. I don't pretend to understand these things, but I though you could use newer versions of Autoconf to produce DLLs. I'm sure Andreas Buening would be able to tell us, although I haven't heard much from him for a while. > 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 -- John **= Email 5 ==========================** Date: Thu, 30 Oct 2003 23:43:12 +1100 (EST) From: Andrew MacIntyre Subject: Re: Building Python On Wed, 29 Oct 2003, John Poltorak wrote: > .. so I should be able to extract the standard source tarball and run > Make with your Makefile? > > I tried that and got:- > > Python-2.3.2 > using python specific Makefile > make: $SHELL changed (was `/bin/sh', now `c:\os2\cmd.exe') > mkdir.exe out > mkdir.exe out/optimize > make: *** No rule to make target `out/optimize/config.obj', needed by `python23_s.lib'. Stop. > make: $SHELL changed (was `/bin/sh', now `c:\os2\cmd.exe') > make: *** No rule to make target `install'. Stop. > > This happens very early on, so I wondered if it was due to something like > the wrong version of MAKE or SH... > > Can you see anything obviously wrong with this? I know it doesn't look > like much to go on. You missed the warning in the "building from source" section of README.os2emx file (in PC/os2emx) which says that make should be run from the PC/os2emx subdirectory, not from the root of the Python source tree - ie: tar zxf Python-2.3.2.tar.gz cd Python-2.3.2/PC/os2emx make > > It is on my to-do list (for Python 2.4) to change the significant #defines > > used to include the OS/2 support so that a configure'ed build will be much > > closer to the Makefile build, but there will still be bits that won't get > > detected by the autoconf machinery. > > Have you tried using Autoconf to create an OS/2-friendly configure? No. Last I knew, Python's configure.in was working with autoconf 2.53 and I hadn't heard any promising noises about OS/2 versions of autoconf later than 2.13. configure.in will need some non-trivial changes to get an OS/2 build that: - does the right thing with threads; - sets up the core DLL and the associated import libraries correctly; and - supports dynamicly loadable extensions viably. As it stands, I expect a configure build to result in a monolithic, staticly linked, python.exe. Such a beast can't support dynamicly loaded extensions, so the desired extensions have to be manually edited into Modules/Setup so that they get built into the monolithic interpreter. This is not overly attractive compared to the dynamic loading support in the EMX port Makefile. 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