Re: DarwinPorts (MacPorts) Advisory: Stay with at least Xcode 2.2.1 on Intel (if not PPC)

On 8/26/06, Timothy J. Wood <[email protected]> wrote:
>
>
> On Aug 26, 2006, at 11:10 PM, Tabitha McNerney wrote:
> > I therefore highly encourage current DarwinPorts (MacPorts) users
> > to stick
> > with 2.2.1 (unless Xcode 2.3 is fine but I have not tested it).
>
>    Xcode 2.3 was working fine for me, though I only use a few ports.
>
>    In general, though, I'd think that a call to stay with a
> particular version of Xcode is unlikely to work.  Instead, the
> problem needs to be identified, either with the port or Xcode.
>
> -tim


Tim you may be on to something and have a good point. I thought for sure I
was on the right track by switching back to Xcode 2.2.1 but sure enough, the
xrender port from MacPorts (DarwinPorts) 1.3.2 with Xcode 2.2.1 on Intel (
10.4.7) failed. However, unlike when using Xcode 2.4, when attempting to
build xrender, when it failed I was able to capture the output to standard
out without the machine freezing up (in other words, with Xcode
2.4attempting to build xrender from DP
1.3.2 caused a kernel panic and the entire Mac Mini Intel froze up).

I allow for the possibility that there might be a problem with UFS volumes
on an Intel machine. I will also toggle back to DP 1.3.1 (with Xcode 2.2.1)
to see if that makes a difference or not.

I guess these are the growing pains that Apple and its loosely coupled open
source community is going to endure during the Intel transition. I'm happy
to help and test to make a contribution to MacPorts.

Best regards,

T.