# XCode / SDCC Intel-Mac issue **URL:** \ **Category:** GNU Radio\ **Created:** [October 11, 2006, 3:49am UTC](https://www.ruby-forum.com/t/xcode-sdcc-intel-mac-issue/71736 "2006-10-11T03:49:29Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![mdeering](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/278dde/32.png) [@mdeering](https://www.ruby-forum.com/u/mdeering)\ **Post date:** [October 11, 2006, 3:49am UTC](https://www.ruby-forum.com/t/xcode-sdcc-intel-mac-issue/71736/1 "2006-10-11T03:49:29Z")
I made enough progress on this issue to know there is a problem, but that it’s beyond what I can investigate further until I have more time. What I’m doing instead is making the compiled and ready to install SDCC 2.4 for Intel-Darwin available for anyone to download and install. That way folks can keep using GNU Radio from the current SVN repository, and at some time in the future maybe SDCC will get fixed, or Apple’s GCC will get fixed, or whatever the problem(s) is (are) will get fixed. While XCode certainly seems suspicious, and most fingers point to it being the issue, some fingers don’t point there (they just don’t point, since those data points don’t fit into any pattern I’ve tested). I’ve updated the “MacInstall” Wiki page with this info \< http:// [gnuradio.org/trac/wiki/MacInstall](http://gnuradio.org/trac/wiki/MacInstall) \>. I’m also updating my install guide with the same info. I would certainly appreciate knowing that this work around does really work for (some, all, many) Intel-Mac users. I know that it works for me. - MLD ---
**Author:** ![mdeering](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/278dde/32.png) [@mdeering](https://www.ruby-forum.com/u/mdeering)\ **Post date:** [October 18, 2006, 10:40am UTC](https://www.ruby-forum.com/t/xcode-sdcc-intel-mac-issue/71736/2 "2006-10-18T10:40:07Z")
Michael, thank you for doing an excellent piece of detective work to get to the source of this issue! Well done! I’ll be at ND for “The Game” next weekend, and if you happen to go there too, I’d like to buy you a hot dog! I have another surprising data point to add to this whole thing: I just updated all the darwinports stuff on my wife’s Macbook Pro. I rebuilt the world, and guess what, the USRP code builds and runs just fine on that machine with SDCC 2.6! This is with XCode 2.2.1. I seem to have gotten the lucky release. Maybe not all the 2.2.1s are the same (different gcc builds or something)? Mine came from the DVD in the box. Anyway, thanks for all the time you sank into this. At least now everybody should be able to build a working USRP image on any of the Intel Macs, and that’s what matters. Cheers, Jan ---
**Author:** ![mdeering](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/278dde/32.png) [@mdeering](https://www.ruby-forum.com/u/mdeering)\ **Post date:** [October 18, 2006, 10:40am UTC](https://www.ruby-forum.com/t/xcode-sdcc-intel-mac-issue/71736/3 "2006-10-18T10:40:55Z")
> I have another surprising data point to add to this whole thing: I > just updated all the darwinports stuff on my wife’s Macbook Pro. I > rebuilt the world, and guess what, the USRP code builds and runs > just fine on that machine with SDCC 2.6! This is with XCode 2.2.1. > I seem to have gotten the lucky release. Maybe not all the 2.2.1s > are the same (different gcc builds or something)? Mine came from > the DVD in the box. Fascinating. Maybe 2.2.1 was what was running on the MBP from which I retrieved the “good” SDCC 2.4.0. I will have to revert back the MBP (from 2.4 to 2.2.1) and the Intel-iMac further (from 2.3 to 2.2.1) and see if that makes any difference - hopefully Monday (Oct 16). I was able to boil down the runtime error in SDCC 2.6.0 (i.e. compiling C code into FPGA code using SDCC) using about 30 lines of GR code. I’ve submitted the various findings including that code (with FSF header) to the DarwinPorts folks, who seem intrigued. > Anyway, thanks for all the time you sank into this. At least now > everybody should be able to build a working USRP image on any of > the Intel Macs, and that’s what matters. You and the general GR community (esp OSX users) are welcome; it continues to be a goal of mine to maintain functionality on OSX. Sometimes that means going on these wild goose chases, and finding a work-around but not a solution. Given the time-constraints in my life, I’m OK with that. - MLD