compiling Python 2.1.1

Ignacio Vazquez-Abrams ignacio at openservices.net
Mon Aug 27 12:11:58 EDT 2001


On Mon, 27 Aug 2001, Roman Suzi wrote:

> On Mon, 27 Aug 2001, Ignacio Vazquez-Abrams wrote:
>
> > 1.1? Ouch.
> >
> >   ftp://ftp.rpmfind.net/linux/sourceforge/expat/expat-1.95.2-1.src.rpm
>
> This doesn't provide expat-devel (that is, includes and libs).

Well, it provides includes and libs, but in the main package, not in -devel.

> > db1 may be trickier. IIRC, there's some sort of conflict with 6.2 and the db1
> > packages from 7.x. Nonetheless:
> >
> >   ftp://ftp.redhat.com/pub/redhat/linux/7.1/en/os/i386/SRPMS/db1-1.85-5.src.rpm
>
> Trickier indeed:
>
> # rpm -hiv db1-1.85-5.i386.rpm db1-devel-1.85-5.i386.rpm
> error: failed dependencies:
>         glibc < 2.1.90 conflicts with db1-1.85-5
>         glibc-devel < 2.1.90 conflicts with db1-devel-1.85-5

Yeah, that's what I remember happening.

> How people compile Python 2.1.1 from src.rpm on not-so-ancient RedHat 6.2
> (without tricks)???
>
> I do not believe Python 2.1.1 requires RedHat 7.x to compile
> and run, but that is what official src.rpm for it insists.
>
> Maybe I could find alternative spec-file?

Naw, just edit the spec file:

1) Add 'rh62' to the end of the Release,
2) Change 'expat-devel...' and 'db1-devel...' in the BuildPrereq to
     'expat=1.95.2' and 'glibc-devel<=2.1.90', and
3) Rebuild with '-ba' instead of '-bb' to generate new SRPMS.

spec files may be magic, but they're not black magic ;)

> > Knock yourself out.
>
> Sincerely yours, Roman A.Suzi

Interestingly enough, rawhide's python2-2.1.1-2 doesn't seem to have a
BuildPrereq for db1-devel, although it still has expat-devel. And wouldn't you
know it, expat-1.95.1-7, also from rawhide, generates a -devel package. I
think we have a fairly reliable source for these packages, don't you? :)

  ftp://ftp.redhat.com/pub/redhat/linux/rawhide/SRPMS/SRPMS/

-- 
Ignacio Vazquez-Abrams  <ignacio at openservices.net>








More information about the Python-list mailing list