#17966 closed defect (invalid)
Error compiling macfuse
Reported by: | linuxerianer@… | Owned by: | kballard (Lily Ballard) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.7.0 |
Keywords: | Cc: | ||
Port: | macfuse |
Description
I tried to compile macfuse when it came to the following error:
sudo port install macfuse Password: ---> Building macfuse Error: Target org.macports.build returned: shell command "cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_fuse_macfuse/work/macfuse-core && ./build_macfuse.sh | sed -ne '/^created: /h;p;${g;s/^created: // w ../dmgname }'; exit ${PIPESTATUS[0]}" returned error 1 Command output: setenv SYSTEM_DOCUMENTATION_DIR /Library/Documentation setenv SYSTEM_LIBRARY_DIR /System/Library setenv TARGETNAME All setenv TARGET_BUILD_DIR /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_fuse_macfuse/work/macfuse-core/10.5/fusefs/build/Release setenv TARGET_NAME All setenv TARGET_TEMP_DIR /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_fuse_macfuse/work/macfuse-core/10.5/fusefs/build/fusefs.build/Release/All.build setenv TEMP_DIR /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_fuse_macfuse/work/macfuse-core/10.5/fusefs/build/fusefs.build/Release/All.build setenv TEMP_FILES_DIR /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_fuse_macfuse/work/macfuse-core/10.5/fusefs/build/fusefs.build/Release/All.build setenv TEMP_FILE_DIR /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_fuse_macfuse/work/macfuse-core/10.5/fusefs/build/fusefs.build/Release/All.build setenv TEMP_ROOT /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_fuse_macfuse/work/macfuse-core/10.5/fusefs/build setenv UID 0 setenv UNSTRIPPED_PRODUCT NO setenv USER root setenv USER_APPS_DIR /var/root/Applications setenv USER_LIBRARY_DIR /var/root/Library setenv USE_DYNAMIC_NO_PIC YES setenv USE_HEADERMAP YES setenv USE_HEADER_SYMLINKS NO setenv VALID_ARCHS "i386 ppc ppc64 ppc7400 ppc970 x86_64" setenv VERBOSE_PBXCP NO setenv VERSION_INFO_BUILDER root setenv VERSION_INFO_FILE All_vers.c setenv VERSION_INFO_STRING "\"@(#)PROGRAM:All PROJECT:fusefs-\"" setenv XCODE_APP_SUPPORT_DIR /Developer/Library/Xcode setenv XCODE_VERSION_ACTUAL 0310 setenv XCODE_VERSION_MAJOR 0300 setenv YACC /Developer/usr/bin/yacc setenv ZERO_LINK NO /bin/sh -c /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_fuse_macfuse/work/macfuse-core/10.5/fusefs/build/fusefs.build/Release/All.build/Script-54C6DE950B5F7755002D9FD9.sh cp: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_fuse_macfuse/work/macfuse-core/10.5/fusefs/build/Release/load_fusefs: No such file or directory Error: Status 1 encountered during processing.
There seems to be a mismatch of paths when the script tries to copy the files load_fusefs and mount_fusefs. I found the files, e.g. load_fusefs in the following path:
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_fuse_macfuse/work/macfuse-core/10.5/fusefs/build/fusefs.build/Release/load_fusefs.build/Objects-normal/i386
Changing the paths for load_fusefs and mount_fusefs in the project file...
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_fuse_macfuse/work/macfuse-core/10.5/fusefs/fusefs.xcodeproj/project.pbxproj
... did't do the trick as the build then fails processing the ppc arch.
I searched a while in the other tickets but didn't find this problem yet.
Some additional information about my system: MacBook1.1, CoreDuo, 2Gb, Leopard 10.5.6
Thanks for helping in advance! Greetings, Roman
Change History (4)
comment:1 Changed 16 years ago by jmroot (Joshua Root)
Owner: | changed from macports-tickets@… to eridius@… |
---|
comment:2 Changed 16 years ago by linuxerianer@…
Oh no, I didn't recognize my outdated XCode 3.1.1. What a disgrace. ;) Everything is running fine! The ticket can safely be closed. Thank you very much. Greetings, Roman
comment:3 Changed 16 years ago by mf2k (Frank Schima)
Resolution: | → invalid |
---|---|
Status: | new → closed |
What version of XCode do you have?