Sean McBride wrote:
On 2007-02-06 13:00, Bill Hoffman said:
I have no idea, someone else did it, I think they just clicked on get
software updates.
Ah, it was probably François actually, he mentioned doing a swupdate on
the vtk-dev list. So in a way it's my fault because he did the u
On 2007-02-06 13:00, Bill Hoffman said:
>I have no idea, someone else did it, I think they just clicked on get
>software updates.
Ah, it was probably François actually, he mentioned doing a swupdate on
the vtk-dev list. So in a way it's my fault because he did the update
to try and fix this:
Sean McBride wrote:
On 2007-02-06 10:39, Bill Hoffman said:
So, the mac we run our cmake dashboards was "updated". This caused the
cmake dashboard to start to fail. The problem seems to be a change in
the behavior of the lipo command. Note, Xcode was not updated
I'm curious, what w
On 2007-02-06 10:39, Bill Hoffman said:
>So, the mac we run our cmake dashboards was "updated". This caused the
>cmake dashboard to start to fail. The problem seems to be a change in
>the behavior of the lipo command. Note, Xcode was not updated
I'm curious, what was updated?
I keep my 2 cmake
Mike Jackson wrote:
On Feb 6, 2007, at 10:39 AM, Bill Hoffman wrote:
Hi,
So, the mac we run our cmake dashboards was "updated". This caused
the cmake dashboard to start to fail. The problem seems to be a
change in the behavior of the lipo command. Note, Xcode was not updated
I think th
On Feb 6, 2007, at 10:39 AM, Bill Hoffman wrote:
Hi,
So, the mac we run our cmake dashboards was "updated". This caused
the cmake dashboard to start to fail. The problem seems to be a
change in the behavior of the lipo command. Note, Xcode was not
updated
I think that this bug may h
Hi,
So, the mac we run our cmake dashboards was "updated". This caused the
cmake dashboard to start to fail. The problem seems to be a change in
the behavior of the lipo command. Note, Xcode was not updated
I think that this bug may have been fixed:
http://lists.apple.com/archives/xcode-us