Excerpts from Brian Tingle's message of Fri May 28 14:18:37 -0400 2010: Hi Brian,
> Do I need to manually build all the packages I would get with > CSWgardevel into my /app/opt/csw directory (or at least any that > are not already in my build environment) to bootstrap the world? I think you should be able to alter GAR to use a PATH that would allow it to find all of the tools it needs. As long as nothing in GAR is using a full path, it'd be fine...and if it is using a fully qualified path, it's likely a bug that should be corrected. The replacement tools need to be close enough in versions that all options used by GAR are supported too. The file gar.conf.mk contains the setting for PATH, so this is where your tweaks would occur. Some of the hash-bang lines for tools in gar/bin will need a twiddle too. > I have /opt/SUNWspro/bin/cc will that work or will I need to get > SOS? This can be tweaked also, but may require more work. Again, I think the required changes are mostly contained in gar.conf.mk. You might find it easier to add a new GARCOMPILER option by adding variables to handle the needs of your situation instead of modifying an existing compiler option set. Have a look for things like _CC_HOME, etc to see what I'm referring to here. > Any advice on how to use GAR in this mode, or am I barking up the > wrong tree? I'm not sure it's the right tree, but I'm interested in your experiences. You may find other CSW-specific things buried in the GAR code, so expect to spend a bit of time futzing. Any instances of things that could be made generic without negatively impacting the default csw builds would likely be rolled in to the code if you submit patches... Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 _______________________________________________ users mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/users
