View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001846 | FSSCP | --------- | public | 2008-12-14 07:31 | 2009-06-06 08:43 |
| Reporter | chief1983 | Assigned To | |||
| Priority | low | Severity | block | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 3.6.9 | ||||
| Summary | 0001846: Case Sensitive Mac Filesystem breaks Frameworks.tgz | ||||
| Description | Ok, I just installed Leopard recently, and had a couple of problems related to FS on it. One of them involved compiling. It seemed that some headers couldn't be found in the Frameworks area, they were looking for files in paths that didn't exist. I was able to fix it by creating symlinks, but was confused as to why only I had this problem. I reformatted again to try out a case-insensitive file system, to see if that helped. When I extracted the Frameworks tar, lo and behold, there were the symlinks I had to create by hand previously. I believe Ogg and Theora symlinks had to be created by hand, pointing to ../Headers (actually they seem to point to Versions/Current/whatever), for the compile to work. Why they weren't created for me on a case sensitive filesystem, I don't know. All I know is they weren't all there. It's even more bizarre that it was only some of them and not all of them. | ||||
| Additional Information | Just to clarify, it seems like inside the Theora.Framework and Ogg.Framework folders, there should be a Headers, Resources, and Theora/Ogg symlink, all of which point to something inside of Versions/Current. But the Theora and Ogg symlinks were gone, while the Headers and Resources were still there. And on Vorbis, all the symlinks were there (I think, it was two of those three that were gone, and the one that was there depended on the other two). | ||||
| Tags | No tags attached. | ||||
|
|
Really odd, I know I didn't have this problem when I was extracting the Frameworks.tgz on my system |
|
|
Do you have a case-sensitive mac filesystem? I changed that setting and now it's worked fine for me too. |
|
|
This seems to be resolved. Last update was 14/12/2008 (DD/MM/YYYY). Recommending this bug be closed. |
|
|
To my knowledge I'm the only one who has ever used a case sensitive OS X filesystem and managed to reproduce this. I doubt Echelon did. I know it works fine on a regular OS X case-insensitive setup. |
|
|
I was never able to reproduce (but then that's because of my setup - which is standard). I agree this can be closed. |
|
|
Well if you guys don't think anyone else will ever be running a case sensitive filesystem, I guess so. I just figured there might be one or two more others out there who have tried it, and it's probably still broken in that case. |
|
|
Closing: 1) Six months old 2) Problem resolved by reporter 3) Will be archived in Mantis if the problem occurs in future |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2008-12-14 07:31 | chief1983 | New Issue | |
| 2008-12-14 07:59 | Echelon9 | Note Added: 0010410 | |
| 2008-12-14 08:41 | chief1983 | Note Added: 0010412 | |
| 2009-06-06 06:20 | portej05 | Note Added: 0010947 | |
| 2009-06-06 06:20 | portej05 | Status | new => feedback |
| 2009-06-06 07:54 | chief1983 | Note Added: 0010948 | |
| 2009-06-06 08:12 | Echelon9 | Note Added: 0010949 | |
| 2009-06-06 08:14 | chief1983 | Note Added: 0010950 | |
| 2009-06-06 08:43 | portej05 | Status | feedback => closed |
| 2009-06-06 08:43 | portej05 | Note Added: 0010951 | |
| 2009-06-06 08:43 | portej05 | Resolution | open => no change required |
