Hi Ben,
thx for sharing, a few comments:
Ben Taylor wrote:
> On Sat, Jun 28, 2008 at 12:56 PM, michael schuster
> <Michael.Schuster at sun.com> wrote:
>> Lukas et. al.
>>
>> I was just about to write an email about a compilation failure I'm seeing
>> with CBE & FOSS when I saw this line in the log file:
>>
>> pkgbuild: /bin/bash ../libtool --mode=compile
>> /ws/onnv-tools/SUNWspro/SS12/bin/cc
>
> looks like a pathing issue. mine picked up all the places I have
> cc hiding.
so did mine - the "interesting" thing is that I don't have anything apart
from /usr/bin in the path before I source the env. file.
>> 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*.
>
> cbe-install asked me if I wanted to chose my compiler...
>
>> how do I correctly setup CBE or use the env. file to make sure it uses
>> /usr/bin/cc or /opt/SUNWspro/...? (I'm fairly sure I didn't botch the
>> selection of compilers when CBE asked me).
>
> not sure what to tell you. Mine picked up the right stuff. Maybe
> removing the /ws/onnv-tools from your path before rerunning
> cbe-install.
>
> I also found that our libtool hardcodes SDE=/opt/kdebld/bin/sed,
yes, that's what I stumbled over ("compilation failure" in my first email).
> which doesn't exist if we have cbe installed and not kde. I wrote
> a short conditional around if [ -x /opt/kdebld/bin/sed ];.... else
> if [ -x /opt/dtbld/bin/sed ]; which seemed to work.
where did you put that conditional? libtool?
Michael
--
Michael Schuster http://blogs.sun.com/recursion
Recursion, n.: see 'Recursion'
