Fink + Leopard Potpourri

Just wanted to give a quick update on a mix of Fink and Leopard issues.

First of all, if you get the error, “Failed: Can't fix GCC after Repair Permissions” it’s because the XCode installer decided not to bother erasing your /usr/sbin/gcc_select even though it shouldn’t be there anymore. It should be safe to erase it, but if that scares you, you can upgrade to 0.27.8 and your problem should go away as well… (Fink does not use gcc_select anymore on 10.5 as of 0.27.8.)

Also, people have been coming out of the woodwork hitting the OpenGL bug (“ld: cycle in dylib re-exports with /usr/X11R6/lib/libGL.dylib”) so I want to mention it here specifically for search engines to make it easier for people to find the fix.

The fix is to add the following line to your linker command: -Wl,-dylib_file,/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib:/System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib

It should be a perfectly safe no-op on older Mac OS X releases, but makes sure that the XCode 3.0 linker doesn’t get confused and try to be too smart about finding the correct libGL.dylib.

I’ve also been trying to solve a new-on-leopard issue where they no longer allow CoreFoundation code to be called across a fork (presumably mach port messiness). The error is:

The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec(). Break on
__THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.

…it seems to hit KUniqueApplications specifically. The fix is most likely to re-exec after kdeinit does it’s thing, using execve() but I’m not entirely sure. I need to play around with it some more first. If anyone has any ideas, please let me know. 😉

Also, I updated fontconfig2-dev — it’s at 2.4.1 in 10.4 now, and no longer has conflicting configuration stuff that expects Apple’s to be there. On 10.5, it’s a dummy package that symlinks into the fontconfig 2.4.1 in /usr/X11, so there’s no issues of conflicts on leopard.

On an unrelated note, yes I am working on a new KDE/Mac snapshot, and have been making good progress on it. I’d say I’m probably 95% of the way through a full clean build working. Of course, KDE/Mac on Leopard has the same problem that KDE/X11 does, so whatever I solve in one will need to be ported to the other. Whee.

I think that’s it… If you have any questions, as always, let me know. I’m trying to work my way through everything, but there’s lots of stuff to fix still.

Share on Facebook

Comments are closed.