Date: Wed, 4 May 2005 00:05:15 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 548 ************************************************** Tuesday 03 May 2005 Number 548 ************************************************** Subjects for today 1 Re: Generating diffs : Stefan.Neis at t-online.de 2 Innotek GCC & Python : Paul Smedley **= Email 1 ==========================** Date: Mon, 02 May 2005 16:53:08 +0200 (CEST) From: Stefan.Neis at t-online.de Subject: Re: Generating diffs Paul Smedley schrieb: > Is there any easy way to make diffs based on files in two > separate trees diff -C -r old_tree new_tree HTH, Stefan **= Email 2 ==========================** Date: Tue, 03 May 2005 20:18:53 +0930 From: Paul Smedley Subject: Innotek GCC & Python Hiya Andy, Andrew MacIntyre wrote: > Paul Smedley wrote: > That will definitely make things easier for getting patches ready for > integration into Python CVS. patches sent to Andy off-list. > If you're going to defer the configure problem for a bit, then we > can put the detection of the correct PYCC_GCC value directly in > pyconfig.h: > > #if defined(__INNOTEK_LIBC__) > #define PYCC_GCC 2 > #else > #define PYCC_GCC 1 > #endif > > (assuming __INNOTEK_LIBC__ is what we should base the decision on) I've done something very similar to this in the patches I sent you..... >> I'll hopefully get some patches to the 2.5 tree to get the Python-cvs to >> the same point with Innotek GCC that I'm at with 2.4.1 - that is - >> problems with curses & bittorrent 4.0 but everything else seems OK. > > I went back to the message you sent with the traceback from the curses > module. I don't think linking is your problem, but I wonder whether > calling conventions might be? Did you build the curses lib yourself? Yeah - there's doesn't seem to be a build of curses with Innotek GCC.... I was starting to think the same thing last night about calling conventions... The part I don't yet understand is why the pyds (which are renamed OS/2 DLLs) work but it appears at least that loading _curses.dll doesn't... I did try making a lib out of the curses.a in the port of curses on Hobbes but causes all sorts of problems in getting python to compile... > The FreeBSD manpages state that nocbreak() changes the tty from raw > mode back to cooked mode - perhaps Thomas Dickey could explain how this > might go wrong. personally I think all of curses is borked in my build.... I'm just at a bit of a loss to determine why :( > The only Python curses code that I can think of, other than BitTorrent, > is a demo version of Conway's Life in the psyco package; there is also > a curses test in Python's regression test suite which might be worth a > try (though I don't recall it working correctly when I tried it). > Curses test has a similar error to bittorrent..... Cheers, Paul.