On May 7, 2007, at 01:35, Jyrki Wahlstedt wrote:
there seems to be one small problem with the package. It does not
build on case-sensitive filesystems! It failed in my home laptop,
though there were no problems in my work laptop. The main
difference between the units is the filesystem, at work I didn't
install the system and the filesystem is the default, at home I use
the case-sensitive variant (having a still longer UNIX than Mac
background).
I looked at the fusefs package and there is an include (in
fuse_ipc.c):
#include <UserNotification/kUNCUserNotifications.h>
the file is actually:
/System/Library/Frameworks/Kernel.framework/Versions/A/Headers/
UserNotification/KUNCUserNotifications.h
I couldn't yet check whether that fixes the problem, but it seems
promising.
Sounds like this problem is not specific to MacPorts, and that it
should be reported to the upstream maintainers of fusefs.
Every port should build on case-sensitive filesystems, too!!!
Perhaps. But note that Apple used to specifically tell you not to use
case-sensitive HFS+ for your boot volume in the 10.3 days. See the
first paragraph:
http://docs.info.apple.com/article.html?artnum=107863
I can find virtually no other information in the knowledge base about
case-sensitive HFS+, including whether or not that directive still
applies to 10.4 and later.
Note also that probably none of the MacPorts contributors have case-
sensitive HFS+ setups, so probably nobody other than you will
discover or be affected by such problems. While I would expect such
problems to be rare, they would be nonexistent if you used the normal
case-insensitive HFS+.
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-users
