>From gmarler at gmarler.com Tue Aug 21 20:24:50 2007
>Looks like you've found the source of the problem (I was reading the end
>of a very long dmake log that mentioned /usr/local/bin, which is why I
>got it wrong - I needed to look at the beginning of the problem as you
>did):
It helps a lot to just go build the affected thing by hand too.
Sometimes that's much much easier than deciphering the log.
>2) The build really shouldn't require that anyway
Ideally, but sometimes there's no helping it. I seem to remember
that it needs at least gsed which is only available on the ccd.
There could be more, as I think there are other things that
might behave like top and test for needed libraries only
in /opt/sfw and not the proto area. top had an easy fix,
but other things may not.
There is also a limit as to how far one should go to make it self-contained,
particularly with open source bits that may require major surgery
to deal with being built and installed into a proto area rather than
just onto the same machine. I'd rather err on the side of easy
(just install SXDE, Studio 11, and recent ccd bits) than complicate the build
process too much to compensate for folks that may not have installed
everything. Or even to try to minimize the set of packages you
need to install from the ccd (a list that could change quite
frequently and would likely be wrong more often than not).
>In essence, I was trying to build the entire CCD package set, so I
>*could* install them (and thus create /opt/sfw in the process). That
>case needs to be covered by the build too, you would think.
I think the docs say to download recent bits first. If not, they should.
>I'll try svn update'ing and see if the changes you've inserted helps
>things out.
They are not there, I think steve will be looking at doing that soon.
They really should be code reviewed and all first, I didn't even
do a full build or anything.
>I also notice a couple of odd things in usr/src/tools:
>
>The cc file defaults cc to be /ws/onnv-tools/SUNWspro/SS11/bin/cc - an
>odd setting, since SPRO_ROOT isn't set by default in the
>freeware-developer.sh file
It is set to that by default in Makefile.master. Internally, it
was never intended that anyone have to set SPRO_ROOT or any other
variable to use the right compilers. Externally of course you have to.
But perhaps SPRO_ROOT should be set to the normally installed
location in the example env file.
>The CC file gets even weirder: even if you set SPRO_ROOT, CC gets set to
>$SPRO_ROOT/SS11/bin/CC. That SS11 seems like it should at least be
>inside the closing brace as it is in the cc file.
yeah they should match. But also note that CC would not work
anyway if you intended to use SS11. sfw has the same problem.
The cc/CC scripts were an attempt to make it easier to sneak
options and such in for configure to pick up. However I'm not
sure they're really that useful anymore (or that folks even
noticed they were there).
>Easily worked around, but makes it a bit hard for someone new to get
>going with the CCD.
Not the CC script though, look at it carefully :)
Mike
