Re: bad gcc/libstdc++-v3 build on Solaris 7

[Phil Edwards <pedwards at disaster dot jaj dot com>]

On Mon, Mar 05, 2001 at 09:24:44AM -0500, Stephen Webb wrote:
> Yeah, this took me a long time to figure out.  My first success was to
> treat a Solaris build like a native cross-compiler (??) by merging the
> binutils source into the gcc source and building everything at once. A
> whole lot of manual labour.   Then I found the better way.

A merged or unified tree is certainly one way to do it.  It's actually
really easy once you discover the symlink-tree script in the toplevel
source directory.  Until then unifying trees is a true PITA.

Or you can use the --with-as=/ab/c/ --with-ld=/a/b/c method already posted.
This is quite confusing, but is apparently by design:

    --with-foo=/path-to/foo is what is used to specify a particular tool

    --with-gnu-foo does not specify the location of a tool (how could it),
       but rather tells the compiler to emit code that can take advantage
       of GNU extensions

Under Solaris (and probably others), you must use them both if you aren't
building from a unified source tree.  The issue comes up on Solaris more
often than others because of the issues with the native linker.  I use a
unified tree, CVS GCC and CVS binutils, under Solaris 8, so I only need to
use the --with-gnu-* options.  And no preinstallation of tools needed.  :-)

Also, BTW, --with-gnu-binutils isn't used by anything anymore.


> I imagine someone should fix this some day....

Except that it's not broken.  :-|  Freakishly confusing, but not broken.
Fortunately, the only people who usually have to worry about these things
are the developers like you and me, and the system integrators.  Ye Olde
Ende User shouldn't ever see this stuff.


Phil

-- 
pedwards at disaster dot jaj dot com  |  pme at sources dot redhat dot com
devphil at several other less interesting addresses in various dot domains
The gods do not protect fools.  Fools are protected by more capable fools.