tummy compile Mandrake 7.2

[Joal Heagney]

myself wrote:

> <Joal wrote some cool stuff, but you'll have to backtrack>

*Joal blushes*

> hey Joal, I hate to break it to ya, but YOU'RE DA MAN!! I never would have
> figured all that out, and certainly would never have proceeded to the rpm
> -bb stage after what looked like a total failure of the rpm -bi. So far it
> looks good, but even if it turns out things aren't exactly right, I
> learned a lot, and could go back in and try again.

I can't remember what first triggered me to try it. I think it was the
point that rpm still built dependencies based on what was in the spec
file, after the auto-dependencies chucked a wobbly.

> A few notes- used python2-2.1-5.src.rpm- changelog looked ok, so why not;
> along the way installed openssl & -devel-0.9.6-7, expat & -devel-1.95.1-3,
> and libgmp3-3.11-3, all mdk.i586.rpm, mostly cooker IIRC, no dep. probs.
> w/ any. Line #'s were different in spec file, but your instructions were
> clear enough that it didn't matter.

Yep. Unfortunatly you usually have to build rpms from source to maintain
Mandrake's optimisations and enhancements, but if you can only get a
binary i386.rpm, don't be too troubled about using it. If the
dependencies are satisfied, it should work, and the optimisations that
Mandrake uses doesn't actually get you that much extra speed. Keep those
built rpms lying around somewhere though. You wouldn't believe how they
can speed up system recovery if you do something silly. (And if you
don't, you're not trying hard enough!)

> from reprtest:
> 
> 122 tests OK.
> 1 test failed: test_socket ("already in use").
> 14 tests skipped: test_al test_bsddb test_cd test_cl test_dbm test_dl
> test_gl test_idev test_sundry test_winreg test_winsound
> 
> which is vast improvement- as user I previously had more skips and
> <gasp> crashes on some imp't ones like _builtin_ and _types_!

Okay, the test_socket one probably isn't too important, though I'd be
curious to know what caused it. The skipped tests are because the build
didn't make certain modules. If you want those modules, such as the
gl-module, rpm -bp <specfile> (prep), then go into the build directory
and run a normal source compile, ensuring you alter Modules/Setup first.
(Or whatever. You'll have to read the build instructions or ask someone
who's build python from source recently.) Then go back to the spec file
and rpm -bi --short-circuit <specfile> etc. Of course you could try to
alter that by creating a patch file and learning the %patch LM macros,
but I usually just fiddle by doing the build myself and then handing
everything back to rpm for the install and packaging steps.

> many thanks! and to the group- in most other ng's, there are always folks
> whose purpose in life seems to be ridiculing the newbie (and other lost
> souls). That almost never happens here; I've only posted in two threads,
> and already given you guys ample opportunity. Thank you for your civility
> and patience.

Most of the people here remember when they were newbies and how well we
were treated ourselves. Additionally, most of us secretly watch
responses to new users avidly because we nearly always learn something
new from them ourselves. Of course we do ask that new users visit
www.python.org and search the documentation where possible, but building
on a Mandrake system brings up problems slightly out of the ordinary.
(Like that *#@$ bz2 thing. *sighs*)

> ps- do toilets *really* flush clockwise in the land downunder?

*groans in pain* Yes they do, and vines also tend to climb trees
clockwise as well.
Happy indenting.
-- 
      Joal Heagney is: _____           _____
   /\ _     __   __ _    |     | _  ___  |
  /__\|\  ||   ||__ |\  || |___|/_\|___] |
 /    \ \_||__ ||___| \_|! |   |   \   \ !