I clicked on "Reply" when I probably should have done "Reply All".
Below is my reponse.

-- Guy Shaw


John Sonnenschein wrote:
 > heya all.
 >
 > Problem here, trying to build psm & uts, fails because it can't find /
 > opt/onbld/usr/ccs/bin/ld
 >
 > problem being I'm not sure what that's actually supposed to be
 > pointing at.
 >
 > rev 97. POLARISgcc, POLARISbinutils, ppc-dev_tools_v3_pt1 and _pt2 ,
 > SUNWonbld-ppc-extra installed. amd64 build host.

I noticed that this message was addressed to me personally,
in addition to being posted to powerpc-discuss. It would
be reasonable to assume that, since I am working on a
development machine at Sun, I would have access to an
authoritative source for /opt/onbld and I would have
the knowledge to help you.

Sorry to disappoint you.

The creation and maintenance of the tools in /opt/onbld
is one of the few means of production that I have allowed
myself to leave to others. And, that was great while it
lasted. I have enjoyed not having to be responsible for
them. You are almost certainly ahead of me when it comes
to knowing where the tools came from and how one goes about
installing them. There must be many others who are in a
better postion to help you.

Tom Riddle did most of the work in setting up /opt/onbld
on the development machines we have been using.
I believe that the customizations to the GNU C compiler
needed for Polaris were done by Cyril Plisko.

Maybe they can help.

Lately, I have had reason to be concerned about how
well controlled my own /opt/onbld is. I recently
changed 'aw', and found out that the version that
was in /opt/onbld/bin/i386 was not built from
usr/src/tools in our source tree. There was not
enough self-describing information to tell me where
it came from. I had to nuke it and work on my own
recreation from the usr/src/tools source code.

I am sure it would be instructive for me to start with
a new computer and follow the recipe for creating
everything I need to do Polaris development. But,
I won't be taking the time to do that this month.

-- Guy Shaw


Reply via email to