Movatterモバイル変換
[0]ホーム
bit by LONG_BIT (was Re: ActivePython 2.1 (build 210))
Grant Griffinnot.this at seebelow.org
Sun Apr 22 10:30:51 EDT 2001
s713221 at student.gu.edu.au wrote:>> > > Wow Windows and Quality Assurance in the same paragraph.... what's the> > > world coming to?> > >> > > BTW isn't Windows Quality Assurance an oxymoron?> >> > I didn't say we quality assured windows. Just that we do quality> > assurance ON windows. Quality assurance on unstable, inconsistent> > platforms consists of figuring out what workarounds are necessary in> > what circumunstances! We had some doozies getting out ActivePython on> > e.g. Windows 95...and that was after all of the work the core team put> > into Win95 compatibility themselves!>> Kinda sounds like trying to build an arched cathedral on quicksand.Yeah, I know what you mean. I just got involved with a new OS, and Ithink it's built on quicksand too.I installed Redhat Linux 7.0 awhile back, and I've been trying to get itto compile stuff. I've tried about a half-dozen Gnu packages, some bigand some small. I did the usual "configure/make/make install" dance. (Kindda like goin' to a hoe-down. Yee haw!) In all cases except"indent", the process halted somewhere along the way. And for those ofyou who've ever tried to work through problems like this, you know thatthe Gnu configure/make process is the biggest, most complicated, mostopaque pond of quicksand you'll ever find: the nested include filesalone'll probably kill you--if you don't drown in preprocessordirectives first.I also had a problem compiling Python 2.1. (Since it's not a Gnupackage, I thought I might have a fighting chance of compiling it on the"Gnu/Linux" system <wink>.) But it seems that the Python source codedoes a "#error" on something about "LONG_BIT". Go figure. So I hitDejanews (or whatever they're calling it these days <wink>) and foundout that this is caused by the fact that I need a new glibc; the onethat ships with Redhat 7.0 is defective. (It seems that Redhat comeswith gcc 2.96 which doesn't actually exist; 2.95 is the latest one.)So I downloaded an "errata" rpm for glibc and installed it. Or at leastI tried. The rpm installer then complained about "glibc-common = 2", orsomething silly like that. Well, obviously.So then I downloaded a new glibc-common and tried to install that. Butrpm puked. (I was beginning to see a pattern here...)Well, thank goodness for Dejanews (or whatever they're calling it thesedays <wink>). I researched the problem, and in a matter of minutesfound posts which said that you've got to install both glibc andglibc-common using the _same_ rpm command. Well, obviously. In fact,in one post, the guy said he was distressed that Redhat didn't bother totell you that. I feel his pain.Anyway, I tried installing both using the same rpm command--what do youknow?--the darn thing actually worked! A whole bunch of "#'s" came outof it. I didn't know quite what that ment, but I hadn't seen thatbefore, so it seemed like a good sign. Best of all, rpm told me it hadsucceeded. Great!Next, I tried to compile Python 2.1. But then I had _another_unexpected problem. It seems that the Python source code does a #erroron something about "LONG_BIT".Quicksand.OK, back to the drawing board. I realized that I hadn't been a Good Boyand applied the "Errata" CD that came with my Redhat package. (As bestI can tell "Errata CD" is a euphemism for that all-purpose cathedralmortar, the "Service Pack" <wink>.) But the Errata CD only installed acouple of things, and they aren't related to compilation, so (notsurprisingly) the Python and Gnu stuff still won't compile.But I kept trying to give the broken Redhat Linux cathedral anotherchance. After all, isn't that the cathedral that's most beloved by TheHolier Than Thou?So I kept trying. One large package that I was able to compilesuccessfully on the "Gnu/Linux" system is wxWindows. Everything I triedin the wxWindows package compiled and ran flawlessly. (Heck, that'snearly as good as the experiences I have compiling software that comesbundled with Microsoft Visual C++ project files <wink>.) I'm not sureif the fact that it's not a Gnu package helped here, but I can't see howit could have hurt.BTW, a couple of years ago, I had tried out the "Cygwin" system. (Forthose who don't know, Cygwin is a compatibility layer that provides aUnix-like environment to allow Gnu-style software to be compiled.) Ihad many bad experiences with it, and I eventually decided that it justbasically didn't work (at least at that time). In particular, I wasbaffled by the fact that even simple ANSI C text-in/text-out programslike "indent" wouldn't compile. (Frankly, anybody who writes an ANSI Ctext-in/text-out program that doesn't compile on Windows isn't trying. Or maybe they're secretly throwing stones at the other guy's cathedral<wink>.)But then somebody told me that it really isn't natural to make Unix runon Windows. That seemed to make sense, so the answer seemed to be touse a *true* Unix-style OS like Linux. So, more recently, I have goneto a great deal of trouble to repartition my hard disk and installRedhat Linux 7.0Silly me.the-bad-thing-about-Gnu's-quicksand-is-that-it's-recursive-ly y'rs,=g2-- _____________________________________________________________________Grant R. Griffing2 at dspguru.comPublisher of dspGuruhttp://www.dspguru.comIowegian International Corporationhttp://www.iowegian.com
More information about the Python-listmailing list
[8]ページ先頭