# Broken Ruby framework symlinks in Leopard SDK?

**URL:** <https://www.ruby-forum.com/t/broken-ruby-framework-symlinks-in-leopard-sdk/129218>\
**Category:** Ruby\
**Created:** [February 15, 2008, 3:20pm UTC](https://www.ruby-forum.com/t/broken-ruby-framework-symlinks-in-leopard-sdk/129218 "2008-02-15T15:20:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![has](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/da6949/32.png) [@has](https://www.ruby-forum.com/u/has)\
**Post date:** [February 15, 2008, 3:20pm UTC](https://www.ruby-forum.com/t/broken-ruby-framework-symlinks-in-leopard-sdk/129218/1 "2008-02-15T15:20:47Z")

</div>

Hi all,

Been trying to embed Ruby.framework in an application and after  
scratching my head a bit at gcc/Xcode build errors discovered that all  
of the header/dylib symlinks under /Developer/SDKs/MacOSX10.5.sdk/  
System/Library/Frameworks/Ruby.framework were broken. Anyone else want  
to confirm this problem before I file a bug report with Apple, or is  
it just my system that’s wonky?

Ta,

has

---

<div class="post-metadata">

**Author:** ![has](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/da6949/32.png) [@has](https://www.ruby-forum.com/u/has)\
**Post date:** [February 15, 2008, 8:44pm UTC](https://www.ruby-forum.com/t/broken-ruby-framework-symlinks-in-leopard-sdk/129218/2 "2008-02-15T20:44:14Z")

</div>

It’s unfortunately a well-known issue, the SDK team is aware of it.  
Feel free to file a bug report if you want to track this problem and  
receive a notification when it will be fixed.

Laurent

---

<div class="post-metadata">

**Author:** ![has](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/da6949/32.png) [@has](https://www.ruby-forum.com/u/has)\
**Post date:** [February 16, 2008, 2:55pm UTC](https://www.ruby-forum.com/t/broken-ruby-framework-symlinks-in-leopard-sdk/129218/3 "2008-02-16T14:55:34Z")

</div>

On 15 Feb, 19:43, Laurent S. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
wrote:

> It’s unfortunately a well-known issue, the SDK team is aware of it.

OK, thanks.
