James Cornell wrote: > michael schuster wrote: >> Laszlo (Laca) Peter wrote: >> >>> On Sat, 2008-06-28 at 21:38 +0200, Lukas Oboril wrote: >>> >>>>> pkgbuild: /bin/bash ../libtool --mode=compile >>>>> /ws/onnv-tools/SUNWspro/SS12/bin/cc >>>>> >>>>> and while /ws/onnv-tools is indeed a valid path to an SS12 compiler, I'm >>>>> not sure it's patched the way we require it to be (this is auto-mounted >>>>> from the nevada build tools on SWAN), whereas the one locally installed >>>>> *is*. >>>>> >>> Michael, >>> >>> /ws/onnv-tools is the location of the Solaris CBE (on the Sun internal >>> network). The compiler you find there is what all projects delivering >>> into Solaris are supposed to use. If you guys need additional patches >>> for KDE, we can ask the CBE team to install them. >>> >> wow! that's an offer! >> >> Laca: in your opinion, would it work better if we (as in Stefan, Ade ...) >> came up with a "definitive" list once KDE builds, or should we give you all >> we know now and add to that list when we find/fix new stuff? >> >> Michael >> > Yay for lack of transparency. Everywhere I go I hit the sun wall, you > need to be inside Sun's internal network... meh.
I think your comment is beside the point - all laca is telling me, I think, is that if I get bad results with /ws/onnv-tools in my path, the choice of compiler I'm offered isn't wrong, but that it needs to be patched to not deliver bad results. Nowhere does he say or imply that /ws/onnv-tools *must* be in your path. please read again: "The compiler you find there is what all projects delivering into Solaris are supposed to use" To me, that means "you should be able to use those compilers to build your successfully", and not "you must use ..." btw: the list of necessary patches is documented on techbase, IIRC. Michael -- Michael Schuster http://blogs.sun.com/recursion Recursion, n.: see 'Recursion'
