Re: Problem with '-static' in 3.0 release on AIX

[David Edelsohn <dje at watson dot ibm dot com>]

>>>>> Matt Conway writes:

Matt> After performing a manual bootstrap like David suggested, my problems with 
Matt> "-static" went away.  Thanks to David for being so patient in explaining 
Matt> to me how to do a manual boostrap.

	Great.  Glad that the tedious process worked.  Hopefully we can
fix these build issues for gcc-3.0.1.

Matt> Unfortunately, I now I have another problem with gcc3.0 on AIX 4.3.3.  The 
Matt> following code compiles ok, but causes a SIGABRT when throwing the 
Matt> exception.  Anyone have any ideas?  Code similar to this was working on 
Matt> 3.0 branch snapshots up to a couple of weeks prior to release, so it must
Matt> be one of the more recent changes that is the culprit.

	I tried your exception handling example which is failing for you,
but it is working okay for me.

	Did you ever install the broken build of the compiler?  Did you
run any applications with the shared libraries that you built earlier?

	I think that you may be seeing another "feature" of AIX: caching
of shared libraries.  By default, AIX caches shared libraries in the
public shared library segment, unless the shared library file permissions
are set to not-readable by other (e.g., chmod o-r libgcc_s.a libstdc++.a).
If the permissions do not allow the shared library to be read by everyone,
the shared library is placed in the process private segment.

	What this means is that your application may be using a stale copy
of the shared library instead of the current file that you rebuilt.  You
need to run the AIX /usr/sbin/slibclean command (which only can be run by
root) to remove the stale copies of the library from the shared library
segment.

	Try that and see if your problem still is present.

David