Re: Want to patch gcc-3.0.4.

[Paul Johnson]

Marcus G. Daniels wrote:
> I don't know of any changes from the previous patch.
>
That's good to know.

I was having trouble compiling gcc-3.0.4 after applying your patch for 
3.0.1 and I initially suspected the patch.

But after some investigation, I learned that the updated 
autoconf/automake I had installed was responsible for the problem.

(In case readers have not been building Swarm during the last 6 months 
or so, in order to build swarm, these autoconf/automake updates are 
necessary. When I started using them I ran into various problems 
building rpms and automake had to be patched. Readers in the automake 
group quickly delivered a fixup for the problem. I believe they have 
been put into the automake CVS version, but as far as I know, they are 
not in any officially released version.)

Anyway, with the patched version of automake/autoconf I built (rpms for 
which I have available), gcc3.0.4 does not build.

In case other people try to build gcc3, and are using various updated 
editions of automake and autoconf, such as mine:

automake-1.5-1pj
autoconf-2.52-1pj

I want you to be warned about this.

When I tried to build gcc3 with those packages in my system, the first 
error I saw was:

./depcomp  not found

In the usenet I found lots of guys guys blaming that on some editions of 
automake-1.5. THey say the fix is to do in the affected directory.
$aclocal
$automake --add-mising

Doing that makes the build go much further, but then it ends with the error:

autoheader: No template for symbol `_POSIX_SOURCE'

Time to give up on that route, at least for me.

Since the RH engineers could build gcc3-3.0.4 on the stock system, my 
path of least resistance was to downgrade to

automake-1.4p5-2
autoconf-2.13-14

After installing those, I am able to rebuild the RedHat gcc3-3.0.4 rpm 
set, after patching with Marcus's gcc patch, a patch which 1) makes the 
annoying/harmless gcc warnings go away and 2) allows method functions or 
other magic I'm not qualified to describe but am aware of.

As evidence that this works and to help other RH users update gcc3 with 
the Swarm patches, in this directory:

http://lark.cc.ukans.edu/~pauljohn/software/gcc-upgrades/3.0.4RH72/

I offer these files.

The RPMS created by taking RH's update gcc3-3.0.4 SRPM and adding the 
objc patch:

gcc3-3.0.4-2pj.src.rpm
gcc3-3.0.4-2pj.i386.rpm
libgcc-3.0.4-2pj.i386.rpm
gcc3-c++-3.0.4-2pj.i386.rpm
libstdc++3-3.0.4-2pj.i386.rpm
libstdc++3-devel-3.0.4-2pj.i386.rpm
gcc3-objc-3.0.4-2pj.i386.rpm
gcc3-g77-3.0.4-2pj.i386.rpm
gcc3-java-3.0.4-2pj.i386.rpm
libgcj3-3.0.4-2pj.i386.rpm
libgcj3-devel-3.0.4-2pj.i386.rpm

Along with the SRPM  file my build created:

gcc3-3.0.4-2pj.src.rpm

The SPEC file

gcc3-3.0.4-2pj.src.rpm

and the patch that I used to fix up the objc part, which I got from 
Marcus Daniels back in the Stone Age period, around October, 2001.

Marcus_objc_gcc301.patch

I think if you are conservative, you could let the regular RH update 
install your gcc3-3.0.4 packages, and then just take my gcc3-objc and 
upgrade that.  Otherwise you can use the stock RH gcc3.

Also, please note, we are following along with the RH design to keep 
both gcc-2.96 and gcc3 in the same system, and several of their gcc3 
packages require you to have gcc-2.96 as well.  You need cpp from that 
older version, for example. According to their experts, the cpp's are 
interchangable.

---
Paul E. Johnson                       email: address@hidden
Dept. of Political Science            http://lark.cc.ku.edu/~pauljohn
University of Kansas                  Office: (785) 864-9086
Lawrence, Kansas 66045                FAX: (785) 864-5700



                 ==================================
  Swarm-Support is for discussion of the technical details of the day
  to day usage of Swarm.  For list administration needs (esp.
  [un]subscribing), please send a message to <address@hidden>
  with "help" in the body of the message.