Re: [tbox-l] Python compiled with gcc, but no gcc RPM is provided

[Marc S. <ma...@au...>]

We're getting there.  In the next couple of weeks we will be releasing
new versions of a lot of things which will solve several problems, but 
cause a one-time headache.  

  1) We will be using the shared library ABI which libtool will be producing
     in the future.  The libtool changes will increase the number of
     open source projects which will be able to produce shared libraries
     for AIX without modification to the Makefiles. 
  2) We will produce compatibility members in those archives to match the
     names of members currently referenced by the Bull freeware code.  If
     we produce libfoo.a(libfoo.so.1), but they produce libfoo.a(shr.o),
     we will provide a load-only shr.o member which will import symbols
     from libfoo.so.1.  This will significantly increase our compatibility
     with Bull's freeware, though I would expect them to migrate to the
     future shared library convention since that's what the sources will
     produce out of the box.
  3) Where possible, we will provide our binaries built with the Visual Age 
     C compiler, since that is still the better performing compiler on Power. 
     The SPEC files will be structured to use the same compiler which we
     used if it is available, but fall through to gcc if vac is unavailable.
     We have to use g++ for C++ programs since the ABIs are incompatible
     between various C++ compilers (and even different versions of g++ are
     incompatible).
  4) We will be providing RPMs for gcc, g++, gdb, and binutils for 4.3.3 
     and 5.1.

The one-time headache will be that the new shared library structure will
cause the existing RPMS and rpm.rte to be incompatible.  Though it is
possible to mix and match the ABIs through clever techniques, I'll 
probably recommend blasting away all of the installed RPMS and will
provide a script to do just that.  I can't apologize enough for the
inconvenience that is going to cause.

I'll pass along the request for a searchable archive to the developerworks
people.  It's a SourceForge-based system.  

Marc

> 
> On 28.03.01, Ole Holm Nielsen wrote:
> >=20
> > Question:  Is it possible for IBM to solve this problem ?
> > One might imagine 2 solutions:  1) Compile your Python RPMs
> > using the IBM C compiler, or 2) provide an RPM containing
> > the gcc-compiler that you have used.
> Ole,
> 
> did you try the gcc from
> ftp://ftp.software.ibm.com/aix/freeSoftware/aixtoolbox/COMPILER/ ?
> It's a tar, not an rpm.
> 
> BTW, dear toolbox-team, a searchable inteface to the
> list archive would be very nice.
> 
> Regards, Ralf
> --=20
>         Ralf Utermann
> _____________________________________________________________________
>         Universit=E4t Augsburg, Institut f=FCr Physik   --   EDV-Betreuer
>         Universit=E4tsstr.1            =20
>         D-86135 Augsburg                     Phone:  +49-821-598-3231
>         SMTP: Ral...@Ph...         Fax: -3411
> _______________________________________________
> aixtoolbox-list mailing list
> aix...@os...
> http://oss.software.ibm.com/developerworks/opensource/mailman/listinfo/ai=
> xtoolbox-list
> 


-- 
Marc Stephenson		                          IBM Server Group - Austin, TX
Internet:  ma...@au...                          NOTES: ma...@us...
Phone:   512-327-5670                                              T/L 678-3189