This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc with binutils-2.11.2 on solaris
- From: Dan Nicolaescu <dann at godzilla dot ICS dot UCI dot EDU>
- To: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 18 Apr 2002 16:08:13 -0700
- Subject: Re: gcc with binutils-2.11.2 on solaris
- References: <Pine.BSF.4.44.0204181253370.77741-100000@naos.dbai.tuwien.ac.at>
Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> writes:
> On Thu, 18 Apr 2002, Dan Nicolaescu wrote:
> > So should we add a note in the installation instructions saying that
> > it's preferable to use binutils on solaris ?
>
> It might be useful to mention that binaries generated when using binutils
> are smaller, yes. If you have a patch, I'll apply it for you...
How does this sound?
*** install.texi.~1.101.~ Thu Apr 18 13:42:36 2002
--- install.texi Thu Apr 18 15:33:50 2002
***************
*** 3443,3448 ****
--- 3443,3453 ----
@end html
@heading @anchor{sparc-sun-solaris2*}sparc-sun-solaris2*
+ When GCC is configured to use binutils-2.11.2 or later the binaries
+ produced are smaller than the ones produced when using Sun's native
+ tools, the difference is quite significant for binaries containing
+ debugging information.
+
Sun @command{as} 4.x is broken in that it cannot cope with long symbol names.
A typical error message might look similar to the following: