Roland Mainz writes: > Is it possible that the bugster gateway for external email addresses is > defunct ? The bugster email contains only the "Synopsis" and no body... > ;-(
I think the problem is actually that this is in the "nws_san_foundation_kit" product, not the "solaris" product. I filed it there because it seemed semi-appropriate, and because I don't know any better. :-/ In any event, here's a copy of the Description field from the CR (there's not much else to it yet): An OpenSolaris contributor noticed that "make setup" in $SRC failed down in $SRC/cmd/avs/errgen, while attempting to compile something, because $SRC/tools wasn't yet built. Looking at the top-level $SRC/Makefile, "setup" depends on "bldtools" which then depends on "sgs". "sgs" then depends on "libheaders", which descends into $SRC/lib and builds "install_h". This is all done before the tools are built, because (as we expect) you shouldn't need any of the local tools in order to do a simple "install_h." Unfortunately, libunistat breaks this design. The install_h target builds something called $(MACH)/spcs_errors.h by going into the $(MACH) directory and issuing a bare "make" (not $(MAKE) ... sigh). That includes $SRC/lib/libunistat/Makefile.com, which has a reach-around for $(ERRGEN), which is $SRC/cmd/avs/errgen. This needs help on multiple fronts: - Because 'errgen' is run on the build machine rather than the target, it should be built using NATIVE_CC. It's not. There's no telling what'll happen if symbols get renamed or versioned in libc (it'll probably cause the whole build to fail). - Because it's used as part of installing header files, it should probably just be included in SUNWonbld. It doesn't make sense to deliver this thing to $ROOT/usr/bin, and then have to exclude it away in exception_list_$(MACH). -- James Carlson, Solaris Networking <james.d.carl...@sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org