In response to Matthew's earlier comments...
obligatory Homer Simpson reference: mmm. Beer.
A fine idea, although what with a few hours of sanity still required of me, binge drinking might go over less well.. And in spite of living in the region proclaimed as "the world's best source of pot", I tend to avoid the stuff myself. :)
On to CMP's question:
>> Can you verify that the _[fs|client|wc|...].la and friends were built
>> in your source dir?
I'm not 100% sure what I _should_ be seeing, so here's the output of running "find . -iname '_*\.la'" in my source dir:
>What's that noise... oh wait, that's the ringing of a bell...
>I had some issues compiling/installing the python bindings on an antique
>RH7.0 box. I eventually discovered I had to install the python2.x-devel RPM
>then re-run make swig-py. (Might have been a "make distclean" in there too,
>In retrospect, it totally baffles me that the build process for the python
>bindings doesn't fail when the necessary libraries and headers are missing.
>Not only that, it *appears* to install correctly too... but I believe the
>libsvn directory was missing until this was resolved. Maybe an issue needs
>to be filed for this? At the time, I blew it off to being "just me" but if
>this fixes Bryan's problem too then I suppose it isn't...
>(PS - another thing I needed to do in my case was upgrade GCC & friends.
>The RH7.0 version had a bug regarding the definition of LONG_BIT which
>creeped up on "make swig-py". I doubt this will be an issue for Bryan on
>SuSE 9 though...)
Damn. That would be really boneheaded... although given that the SuSE installer initially saw fit _not_ to install a whole swath of development-related tools and libraries even after being explicitly asked to do so, somehow it wouldn't surprise me, either.
Scratch that.. I just checked and the python-devel package is installed...
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Jul 29 00:08:07 2004