Re: osxfuse @3.5.0 build error

[Ryan Schmidt]

> On Sep 24, 2016, at 11:18 AM, Davide Liessi  wrote:
> 
> :info:build dyld: Library not loaded: /opt/local/lib/libosxfuse.2.dylib
> :info:build   Referenced from:
> /Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/framework/OSXFUSE.framework/Versions/A/OSXFUSE
> :info:build   Reason: image not found
> :info:build Can't execute compiled C code... aborting

I've filed this as 

https://trac.macports.org/ticket/52435

It looks like it's specific to 32-bit Macs.

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: osxfuse @3.5.0 build error - fixed

[Ryan Schmidt]

> On Sep 28, 2016, at 10:14 AM, Ken Cunningham 
>  wrote:
> 
>> 
>> I notice in the development tree there is some activity on this file 2 days 
>> ago:
>> 
>> https://github.com/osxfuse/support/tree/support/osxfuse-3/mount_osxfuse.
>> 
>> mount_osxfuse.c  (mount_osxfuse) Fix build warning on Mac OS X 10.6
>> 
> 
> 
> So that fixed the osxfuse build on 10.6 for me this morning.
> 
> Just go get that file 
> 
> sudo port extract osxfuse
> 
> and replace the current one with the new one
> 
> sudo port build osxfuse
> 
> and the build goes through to completion, for me just now on 10.6

Thanks for verifying that works. Committed:

https://trac.macports.org/ticket/52426


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: osxfuse @3.5.0 build error - fixed

[Ken Cunningham]

> 
> I notice in the development tree there is some activity on this file 2 days 
> ago:
> 
> https://github.com/osxfuse/support/tree/support/osxfuse-3/mount_osxfuse.
> 
> mount_osxfuse.c   (mount_osxfuse) Fix build warning on Mac OS X 10.6
> 


So that fixed the osxfuse build on 10.6 for me this morning.

Just go get that file 

sudo port extract osxfuse

and replace the current one with the new one

sudo port build osxfuse

and the build goes through to completion, for me just now on 10.6

Best

K___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: osxfuse @3.5.0 build error

[Ken Cunningham]

> 
> cc1: warnings being treated as errors
> /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953/support/mount_osxfuse/mount_osxfuse.c:
>  In function 'send_fd':
> /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953/support/mount_osxfuse/mount_osxfuse.c:603:
>  warning: implicit conversion shortens 64-bit value into a 32-bit value
> 
> I'm not sure if that has anything to do with architecture mismatches; rather, 
> it sounds like a perfectly normal bug in handling numbers of different sizes, 
> that the developers of osxfuse should resolve.

It certainly seems very likely this is the error that needs to be fixed.


I notice in the development tree there is some activity on this file 2 days ago:

https://github.com/osxfuse/support/tree/support/osxfuse-3/mount_osxfuse.

mount_osxfuse.c 
<https://github.com/osxfuse/support/blob/support/osxfuse-3/mount_osxfuse/mount_osxfuse.c>
   (mount_osxfuse) Fix build warning on Mac OS X 10.6 
<https://github.com/osxfuse/support/commit/598c9bbca5fa99903fbf47035edc8e731124758d>

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: osxfuse @3.5.0 build error

[Ken Cunningham]

> 
> info:build pbxcp: mount_osxfuse: No such file or directory
> :info:build pbxcp: mount_osxfuse: No such file or directory
> :info:build CpResource

> :info:build The following build commands failed:
> :info:build mount_osxfuse:
> :info:build CompileC

> build/mount_osxfuse.build/Release/mount_osxfuse.build/Objects-normal/x86_64/mount_osxfuse.o
> /Volumes/MacPorts/hopeful/build/_opt_macports-git_trunk_dports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953/support/mount_osxfuse/mount_osxfuse.c
> normal x86_64 c com.apple.compilers.llvmgcc42


First of all, it’s a very different kind of port. It selects it’s own compilers 
(llvmgcc42), and has intricate links into the Xcode installation.

Most of the options I tried in the portfile that might have normally worked 
(supported_archs etc) have no effect at all on this build.

As you point out, the build fails when trying to build mount_osxfuse.o in 
architecture x86_64. The i386 build does seem to get built on my system.

I think you might make progress initially by trying to just build it yourself 
in the work directory, using the build script. 

The README.md says that you should just be able to run ./build.sh -t 
distribution from there (with sudo of course for the macports location) — but 
that fails with the error above.

Maybe it can be limited to a specific architecture?

The architectures are passed in via an array, and I tried a number of different 
versions of 

 ./build.sh -t distribution -a i386
 ./build.sh -t distribution -architecture i386
 ./build.sh -t distribution -architecture = i386

but so far haven’t divined the secret code.

Once you have it building in the work directory with the proper chord of 
options, translating that to the Portfile will be easier.


Or maybe we’ll just have to get the developer to tell us what we’re doing wrong 
here.


I hope this helps.

Ken



___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: osxfuse @3.5.0 build error

[listmember]

Am 24.09.2016 um 18:18 schrieb Davide Liessi:

> I'm trying to install osxfuse @3.5.0 on Mac OS X 10.6.

Same problem here, however it is built from default portfile. 

from main.log
[…]
> :debug:build Environment: 
> CC_PRINT_OPTIONS='YES'
> CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work/.CC_PRINT_OPTIONS'
> MACOSX_DEPLOYMENT_TARGET='10.6'
> :debug:build Assembled command: 'cd 
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953"
>  && ./build.sh -t packagemanager -a build -v 5 
> --build-directory="/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work"
>  -- -a x86_64 --framework-prefix="/opt/local" --fsbundle-prefix="/opt/local" 
> --library-prefix="/opt/local"'
> :debug:build Executing command line:  cd 
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953"
>  && ./build.sh -t packagemanager -a build -v 5 
> --build-directory="/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work"
>  -- -a x86_64 --framework-prefix="/opt/local" --fsbundle-prefix="/opt/local" 
> --library-prefix="/opt/local" 
> :info:build DEFAULT_BUILD_CONFIGURATION=Release
> :info:build DEFAULT_BUILD_DIRECTORY=/tmp/osxfuse
> :info:build DEFAULT_LOG_VERBOSE=2
> :info:build DEFAULT_PREFIX=''
> :info:build DEFAULT_SDK=10.6
> :info:build DEFAULT_SDK_10_10_ARCHITECURES=([0]=i386 [1]=x86_64)
> :info:build 
> DEFAULT_SDK_10_10_COMPILER=com.apple.compilers.llvm.clang.1_0
> :info:build DEFAULT_SDK_10_11_ARCHITECURES=([0]=i386 [1]=x86_64)
> :info:build 
> DEFAULT_SDK_10_11_COMPILER=com.apple.compilers.llvm.clang.1_0
> :info:build DEFAULT_SDK_10_12_ARCHITECURES=([0]=i386 [1]=x86_64)
> :info:build 
> DEFAULT_SDK_10_12_COMPILER=com.apple.compilers.llvm.clang.1_0
> :info:build DEFAULT_SDK_10_5_ARCHITECURES=([0]=ppc [1]=ppc64 [2]=i386 
> [3]=x86_64)
> :info:build DEFAULT_SDK_10_5_COMPILER=4.2
> :info:build DEFAULT_SDK_10_6_ARCHITECURES=([0]=i386 [1]=x86_64)
> :info:build DEFAULT_SDK_10_6_COMPILER=com.apple.compilers.llvmgcc42
> :info:build DEFAULT_SDK_10_7_ARCHITECURES=([0]=i386 [1]=x86_64)
> :info:build DEFAULT_SDK_10_7_COMPILER=com.apple.compilers.llvmgcc42
> :info:build DEFAULT_SDK_10_8_ARCHITECURES=([0]=i386 [1]=x86_64)
> :info:build 
> DEFAULT_SDK_10_8_COMPILER=com.apple.compilers.llvm.clang.1_0
> :info:build DEFAULT_SDK_10_9_ARCHITECURES=([0]=i386 [1]=x86_64)
> :info:build 
> DEFAULT_SDK_10_9_COMPILER=com.apple.compilers.llvm.clang.1_0
> :info:build DEFAULT_SDK_SUPPORTED=([0]=10.5 [1]=10.6 [2]=10.7 [3]=10.8 
> [4]=10.9 [5]=10.10 [6]=10.11 [7]=10.12)
> :info:build 
> DEFAULT_SOURCE_DIRECTORY=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953
> :info:build 
> BUILD_SOURCE_DIRECTORY=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953
> :info:build 
> BUILD_BUILD_DIRECTORY=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work
> :info:build Search for Xcode
> :info:build 2016-09-28 10:51:52.782 xcodebuild[60139:80b] Error loading 
> /Developer/Library/Xcode/Plug-ins/XdesignCompilerPlugin.xcplugin/Contents/MacOS/XdesignCompilerPlugin:
>   
> dlopen(/Developer/Library/Xcode/Plug-ins/XdesignCompilerPlugin.xcplugin/Contents/MacOS/XdesignCompilerPlugin,
>  265): no suitable image found.  Did find:
> :info:build   
> /Developer/Library/Xcode/Plug-ins/XdesignCompilerPlugin.xcplugin/Contents/MacOS/XdesignCompilerPlugin:
>  no matching architecture in universal wrapper
[…]

later in the main.log i found a strange reference to 10.3.9 SDK:
[…]
> :info:build Assertion 'common_variable_is_legal_name 
> XCODE_SDK_10_3.9_XCODE' failed
> :info:build at array_create (./build.d/lib/array.sh, line 47)
> :info:build at xcode_find_sdk_add (./build.d/lib

Re: osxfuse @3.5.0 build error

[Ryan Schmidt]

In addition to the other replies, another reason is dependencies. There are 
over a dozen ports that depend on osxfuse, so we need to offer osxfuse itself 
in MacPorts to be able to offer those other ports. 

> On Sep 24, 2016, at 20:18, Al Varnell  wrote:
> 
> Sorry for my ignorance here, but why do we need MacPorts to maintain a port 
> when there is are perfectly good installers available on GitHub 
> <https://osxfuse.github.io> including a developer release of version 3.5.1 
> posted close to a week ago?
> 
> -Al-
> 
>> On Sat, Sep 24, 2016 at 11:45 AM, Ryan Schmidt wrote:
>> 
>>> On Sep 24, 2016, at 1:37 PM, Davide Liessi  wrote:
>>> 
>>> 2016-09-24 20:17 GMT+02:00 Ryan Schmidt :
>>>> I'm not sure if that has anything to do with architecture mismatches; 
>>>> rather, it sounds like a perfectly normal bug in handling numbers of 
>>>> different sizes, that the developers of osxfuse should resolve.
>>> 
>>> But with my change the warning disappears,
>> 
>> In any case, it's a bug in osxfuse; please report the problem to the 
>> developers of osxfuse so they can fix it.
>> 
>> https://github.com/osxfuse/osxfuse/issues
>> 
>> 
>>> and the error for osxfuse
>>> @2.8.0 was directly related to the architecture mismatch (although I
>>> don't remember exactly what it was).
>>> So I think the error is somehow related to the architecture mismatch.
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: osxfuse @3.5.0 build error

[Brandon Allbery]

On Sat, Sep 24, 2016 at 9:35 PM, David Liontooth 
wrote:

> There are lots of other advantages to MacPorts than the ease of finding
> the software -- for instance, we have a unified framework for uninstalling
> and upgrading


I had intended to mention the "and keeping it up to date" aspect; if it
were a one time thing, it wouldn't matter so much.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: osxfuse @3.5.0 build error

[David Liontooth]

  
  
On 9/24/16 6:22 PM, Brandon Allbery
  wrote:


  

  On Sat, Sep 24, 2016 at 9:18 PM, Al
Varnell 
wrote:

  Sorry
for my ignorance here, but why do we need MacPorts to
maintain a port when there is are perfectly good
installers available on GitHub  including a developer release of version 3.5.1
posted close to a week ago?

  
  
  The same can be said for a fair chunk of the software in
  MacPorts. Some of us prefer not to have to chase down and
  (possibly build and) install every single piece of software
  ourselves. That's the *point* of MacPorts.

  


There are lots of other advantages to MacPorts than the ease of
finding the software -- for instance, we have a unified framework
for uninstalling and upgrading, keeping your system up to date and
free of cruft, and a system of dependencies. it's great that an
application has a good installer; MacPorts takes the perspective of
thousands of applications interacting over time.


  

  
  
  -- 
  

  brandon s allbery kf8nh                              
sine nomine associates
  allber...@gmail.com
                                 ballb...@sinenomine.net
  unix, openafs, kerberos, infrastructure, xmonad      
 http://sinenomine.net

  

  
  
  
  
  ___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users




  

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: osxfuse @3.5.0 build error

[Ken Cunningham]

and sometimes because of the tremendous support by people like jeremy and many 
others, macports can build things that don’t exist out there in the world — 
like a current version of OpenSCAD or Widelands that runs on 10.6, for example.

or versions of software you can customize to your liking, using the basic 
macports port file as a template.

Ken




> On Sep 24, 2016, at 6:22 PM, Brandon Allbery  wrote:
> 
> 
> On Sat, Sep 24, 2016 at 9:18 PM, Al Varnell  > wrote:
> Sorry for my ignorance here, but why do we need MacPorts to maintain a port 
> when there is are perfectly good installers available on GitHub 
>  > including a 
> developer release of version 3.5.1 posted close to a week ago?
> 
> The same can be said for a fair chunk of the software in MacPorts. Some of us 
> prefer not to have to chase down and (possibly build and) install every 
> single piece of software ourselves. That's the *point* of MacPorts.
> 
> -- 
> brandon s allbery kf8nh   sine nomine associates
> allber...@gmail.com   
> ballb...@sinenomine.net 
> unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net 
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: osxfuse @3.5.0 build error

[Brandon Allbery]

On Sat, Sep 24, 2016 at 9:18 PM, Al Varnell  wrote:

> Sorry for my ignorance here, but why do we need MacPorts to maintain a
> port when there is are perfectly good installers available on GitHub <
> https://osxfuse.github.io
>
> > including a developer release of version 3.5.1 posted close to a week
> ago?
>

The same can be said for a fair chunk of the software in MacPorts. Some of
us prefer not to have to chase down and (possibly build and) install every
single piece of software ourselves. That's the *point* of MacPorts.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: osxfuse @3.5.0 build error

[Al Varnell]

Sorry for my ignorance here, but why do we need MacPorts to maintain a port 
when there is are perfectly good installers available on GitHub 
<https://osxfuse.github.io> including a developer release of version 3.5.1 
posted close to a week ago?

-Al-

On Sat, Sep 24, 2016 at 11:45 AM, Ryan Schmidt wrote:
> 
>> On Sep 24, 2016, at 1:37 PM, Davide Liessi  wrote:
>> 
>> 2016-09-24 20:17 GMT+02:00 Ryan Schmidt :
>>> I'm not sure if that has anything to do with architecture mismatches; 
>>> rather, it sounds like a perfectly normal bug in handling numbers of 
>>> different sizes, that the developers of osxfuse should resolve.
>> 
>> But with my change the warning disappears,
> 
> In any case, it's a bug in osxfuse; please report the problem to the 
> developers of osxfuse so they can fix it.
> 
> https://github.com/osxfuse/osxfuse/issues
> 
> 
>> and the error for osxfuse
>> @2.8.0 was directly related to the architecture mismatch (although I
>> don't remember exactly what it was).
>> So I think the error is somehow related to the architecture mismatch.


smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: osxfuse @3.5.0 build error

[Ryan Schmidt]

> On Sep 24, 2016, at 1:37 PM, Davide Liessi  wrote:
> 
> 2016-09-24 20:17 GMT+02:00 Ryan Schmidt :
>> I'm not sure if that has anything to do with architecture mismatches; 
>> rather, it sounds like a perfectly normal bug in handling numbers of 
>> different sizes, that the developers of osxfuse should resolve.
> 
> But with my change the warning disappears,

In any case, it's a bug in osxfuse; please report the problem to the developers 
of osxfuse so they can fix it.

https://github.com/osxfuse/osxfuse/issues


> and the error for osxfuse
> @2.8.0 was directly related to the architecture mismatch (although I
> don't remember exactly what it was).
> So I think the error is somehow related to the architecture mismatch.

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: osxfuse @3.5.0 build error

[Davide Liessi]

2016-09-24 20:17 GMT+02:00 Ryan Schmidt :
> I'm not sure if that has anything to do with architecture mismatches; rather, 
> it sounds like a perfectly normal bug in handling numbers of different sizes, 
> that the developers of osxfuse should resolve.

But with my change the warning disappears, and the error for osxfuse
@2.8.0 was directly related to the architecture mismatch (although I
don't remember exactly what it was).
So I think the error is somehow related to the architecture mismatch.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: osxfuse @3.5.0 build error

[Ryan Schmidt]

> On Sep 24, 2016, at 1:08 PM, Davide Liessi  wrote:
> 
> 2016-09-24 19:13 GMT+02:00 Ryan Schmidt :
>> The intention of the portfile is explained in the comments:
>> 
>> # We will build user-space components for the specified arch, and
>> # kernel modules for the kernel arch.
>> 
>> It sounds like your changes will cause it to build the user-space components 
>> for the kernel arch as well, which was not the intention.
> 
> Yes, but without my changes (both for @3.5.0 and @2.8.0) it tries to
> build also the kernel extension with the user-space architecture.
> My change to @2.8.0 was the only way I could get a working osxfuse on
> my machine.
> 
>> I'm not certain how to tell the build system what arch to build the kernel 
>> extension for. It would make sense that it would be able to figure it out on 
>> its own, but I don't know if it does.
> 
> Apparently it does not.
> 
> I copy the relevant part of main.log for the original Portfile without
> my change at the end of the message.
> You can find the same error on the 10.6 buildbot and a very similar
> one on the 10.7 buildbot:
> https://build.macports.org/builders/ports-10.6_x86_64_legacy-builder/builds/5740
> https://build.macports.org/builders/ports-10.7_x86_64_legacy-builder/builds/10188

Those logs say the error is:

cc1: warnings being treated as errors
/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953/support/mount_osxfuse/mount_osxfuse.c:
 In function 'send_fd':
/opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953/support/mount_osxfuse/mount_osxfuse.c:603:
 warning: implicit conversion shortens 64-bit value into a 32-bit value

I'm not sure if that has anything to do with architecture mismatches; rather, 
it sounds like a perfectly normal bug in handling numbers of different sizes, 
that the developers of osxfuse should resolve.

The 10.6 log then follows this with:

pbxcp: mount_osxfuse: No such file or directory
pbxcp: mount_osxfuse: No such file or directory


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: osxfuse @3.5.0 build error

[Davide Liessi]

2016-09-24 19:13 GMT+02:00 Ryan Schmidt :
> The intention of the portfile is explained in the comments:
>
> # We will build user-space components for the specified arch, and
> # kernel modules for the kernel arch.
>
> It sounds like your changes will cause it to build the user-space components 
> for the kernel arch as well, which was not the intention.

Yes, but without my changes (both for @3.5.0 and @2.8.0) it tries to
build also the kernel extension with the user-space architecture.
My change to @2.8.0 was the only way I could get a working osxfuse on
my machine.

> I'm not certain how to tell the build system what arch to build the kernel 
> extension for. It would make sense that it would be able to figure it out on 
> its own, but I don't know if it does.

Apparently it does not.

I copy the relevant part of main.log for the original Portfile without
my change at the end of the message.
You can find the same error on the 10.6 buildbot and a very similar
one on the 10.7 buildbot:
https://build.macports.org/builders/ports-10.6_x86_64_legacy-builder/builds/5740
https://build.macports.org/builders/ports-10.7_x86_64_legacy-builder/builds/10188

> osxfuse is not the only port that install a kernel extension. Maybe the 
> handling of whether to build from source (the knowledge of which kernel archs 
> our buildworkers use), and how to determine the kernel arch, should be moved 
> into a portgroup, so as to avoid duplication of effort.

I do agree.

> Is your MacPorts prefix /opt/local?

Yes.

> Does /opt/local/lib/libosxfuse.2.dylib exist?

No.
I deactivated the previous version of osxfuse (@2.8.0 + my changes)
before attempting to build @3.5.0 (both without and with my changes).

> What's /Volumes/MacPorts/hopeful?

A location where I symlinked the build and log directories.

$ ls -l /opt/local/var/macports/{build,logs}
lrwxr-xr-x  1 root  admin  31  9 Giu 18:26
/opt/local/var/macports/build -> /Volumes/MacPorts/hopeful/build
lrwxr-xr-x  1 root  admin  30  9 Giu 18:26
/opt/local/var/macports/logs -> /Volumes/MacPorts/hopeful/logs

> What's /Users/davide/ports-substitution?

The local ports tree where I put the modified Portfile for osxfuse; it
contains also two unrelated ports.

I forgot to mention that I'm building with trace mode on.

Best wishes.
Davide


>From main.log for attempted build with the unmodified Portfile:
```
:info:build === BUILD NATIVE TARGET mount_osxfuse OF PROJECT
mount_osxfuse WITH CONFIGURATION Release ===
:info:build Check dependencies
:info:build CompileC
build/mount_osxfuse.build/Release/mount_osxfuse.build/Objects-normal/x86_64/getmntopts.o
mount_osxfuse/getmntopts.c normal x86_64 c
com.apple.compilers.llvmgcc42
:info:build     cd
/Volumes/MacPorts/hopeful/build/_opt_macports-git_trunk_dports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953/support
:info:build setenv LANG en_US.US-ASCII
:info:build /Developer/usr/bin/llvm-gcc-4.2 -x c -arch x86_64
-fmessage-length=0 -pipe -std=c99 -Wno-trigraphs -fpascal-strings
-fasm-blocks -Os -mdynamic-no-pic -Werror -Wmissing-prototypes
-Werror-implicit-function-declaration -Wreturn-type -Wmissing-braces
-Wparentheses -Wswitch -Wunused-function -Wunused-label
-Wunused-parameter -Wunused-variable -Wunused-value -Wuninitialized
-Wunknown-pragmas -pedantic -Wshadow -Wfour-char-constants
-Wsign-compare -Wnewline-eof -Wshorten-64-to-32
-DOSXFUSE_ENABLE_MACFUSE_MODE=0
-DOSXFUSE_BUNDLE_PREFIX_LITERAL=/opt/local -isysroot
/Developer/SDKs/MacOSX10.6.sdk -fvisibility=hidden
-mmacosx-version-min=10.6
-I/Volumes/MacPorts/hopeful/build/_opt_macports-git_trunk_dports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953/support/build/mount_osxfuse.build/Release/mount_osxfuse.build/mount_osxfuse.hmap
-F/Volumes/MacPorts/hopeful/build/_opt_macports-git_trunk_dports_fuse_osxfuse/osxfuse/work/fsbundle
-I/Volumes/MacPorts/hopeful/build/_opt_macports-git_trunk_dports_fuse_osxfuse/osxfuse/work/fsbundle/include
-I/Volumes/MacPorts/hopeful/build/_opt_macports-git_trunk_dports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953/support/build/mount_osxfuse.build/Release/mount_osxfuse.build/DerivedSources/x86_64
-I/Volumes/MacPorts/hopeful/build/_opt_macports-git_trunk_dports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953/support/build/mount_osxfuse.build/Release/mount_osxfuse.build/DerivedSources
-c 
/Volumes/MacPorts/hopeful/build/_opt_macports-git_trunk_dports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953/support/mount_osxfuse/getmntopts.c
-o 
/Volumes/MacPorts/hopeful/build/_opt_macports-git_trunk_dports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953/support/build/mount_osxfuse.build/Release/mount_osxfuse.build/Objects-normal/x86_64/getmntopts.o
:info:build
:info:build CompileC
build/mount_osxfuse.build/Release/mount_osxfuse.build/Objects-normal/x86_64/mount_osxfuse.o
mount_osxfuse/mount_osxfuse.c normal x86_64 c
com.apple.compilers.llvmgcc42
:info:build     cd

Re: osxfuse @3.5.0 build error

[Ryan Schmidt]

> On Sep 24, 2016, at 11:18 AM, Davide Liessi  wrote:
> 
> I'm trying to install osxfuse @3.5.0 on Mac OS X 10.6.
> 
> I first got an error due to the fact that on my system the kernel is
> 32 bit, but MacPorts tries to build osxfuse 64 bit.
> Indeed on my system `uname -m` outputs `i386`, while
> `get_canonical_archs` returns `x86_64`.
> (The error is the same as in the 10.6 and 10.7 buildbots, thus I
> suspect the same architecture mismatch happens.)
> 
> I then changed line 130 of the Portfile from
> `-a [join [get_canonical_archs] " -a "] \`
> to `-a ${kernel_archs} \`.
> (I had to do something similar also with @2.8.0, namely I had to add
> `configure.build_arch ${kernel_arch}`.)

The intention of the portfile is explained in the comments:

# We will build user-space components for the specified arch, and
# kernel modules for the kernel arch.

It sounds like your changes will cause it to build the user-space components 
for the kernel arch as well, which was not the intention.

I'm not certain how to tell the build system what arch to build the kernel 
extension for. It would make sense that it would be able to figure it out on 
its own, but I don't know if it does.

There is one bug I see in the portfile though:

> # If building for different kernel arch than our buildslaves use, force a 
> build
> # from source. The binary package IDs don't encode the kernel arch.
> if {${kernel_arch} ne "x86_64"} {
> archive_sites
> }

This assumes all of our buildbot workers have 64-bit kernels, which is not 
correct. Specifically, the Snow Leopard and earlier workers have 32-bit 
kernels; I was not able to get VMware to use a 64-bit kernel for Snow Leopard. 
And the Leopard worker is a Power Mac G5, on which `uname -m` returns "Power 
Macintosh".

osxfuse is not the only port that install a kernel extension. Maybe the 
handling of whether to build from source (the knowledge of which kernel archs 
our buildworkers use), and how to determine the kernel arch, should be moved 
into a portgroup, so as to avoid duplication of effort.


> The build got further, but I got another error: I copy the relevant
> part of main.log below.
> Do you have any idea how to solve the problem?
> 
> Best wishes.
> Davide
> 
> 
> From main.log:
> ```
> [...]
> :info:build === BUILD NATIVE TARGET OSXFUSE OF PROJECT OSXFUSE WITH
> CONFIGURATION Release ===
> [...]
> :info:build PhaseScriptExecution "BridgeSupport Metadata"
> build/OSXFUSE.build/Release/OSXFUSE.build/Script-28D525C40EA8076400B7CF7B.sh
> :info:build cd
> /Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953/framework
> :info:build /bin/sh -c
> /Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953/framework/build/OSXFUSE.build/Release/OSXFUSE.build/Script-28D525C40EA8076400B7CF7B.sh
> :info:build
> :info:build dyld: Library not loaded: /opt/local/lib/libosxfuse.2.dylib
> :info:build   Referenced from:
> /Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/framework/OSXFUSE.framework/Versions/A/OSXFUSE
> :info:build   Reason: image not found
> :info:build Can't execute compiled C code... aborting

Is your MacPorts prefix /opt/local?

Does /opt/local/lib/libosxfuse.2.dylib exist? I'm surprised it's looking for 
that while building osxfuse, since it sounds like something that would be 
installed by osxfuse.

What's /Volumes/MacPorts/hopeful?

What's /Users/davide/ports-substitution?


> :info:build line was:
> DYLD_FRAMEWORK_PATH="/Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/framework"
> /Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/.tmp/bin-0-81104
> :info:build binary is
> /Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/.tmp/bin-0-81104
> :info:build Usage: gen_bridge_metadata [options] 
> :info:build Use the `-h' flag or consult gen_bridge_metadata(1) for help.
> :info:build Command /bin/sh failed with exit code 1
> :info:build Command /bin/sh failed with exit code 1
> :info:build Touch
> /Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/framework/OSXFUSE.framework
> :info:build cd
> /Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953/framework
> :info:build /usr/bin/touch -c
> /Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/framework/OSXFUSE.framework
> :info:build
> :info:build Strip
> /Volumes/MacPorts/hopeful/build/_

osxfuse @3.5.0 build error

[Davide Liessi]

I'm trying to install osxfuse @3.5.0 on Mac OS X 10.6.

I first got an error due to the fact that on my system the kernel is
32 bit, but MacPorts tries to build osxfuse 64 bit.
Indeed on my system `uname -m` outputs `i386`, while
`get_canonical_archs` returns `x86_64`.
(The error is the same as in the 10.6 and 10.7 buildbots, thus I
suspect the same architecture mismatch happens.)

I then changed line 130 of the Portfile from
`-a [join [get_canonical_archs] " -a "] \`
to `-a ${kernel_archs} \`.
(I had to do something similar also with @2.8.0, namely I had to add
`configure.build_arch ${kernel_arch}`.)

The build got further, but I got another error: I copy the relevant
part of main.log below.
Do you have any idea how to solve the problem?

Best wishes.
Davide


>From main.log:
```
[...]
:info:build === BUILD NATIVE TARGET OSXFUSE OF PROJECT OSXFUSE WITH
CONFIGURATION Release ===
[...]
:info:build PhaseScriptExecution "BridgeSupport Metadata"
build/OSXFUSE.build/Release/OSXFUSE.build/Script-28D525C40EA8076400B7CF7B.sh
:info:build cd
/Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953/framework
:info:build /bin/sh -c
/Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953/framework/build/OSXFUSE.build/Release/OSXFUSE.build/Script-28D525C40EA8076400B7CF7B.sh
:info:build
:info:build dyld: Library not loaded: /opt/local/lib/libosxfuse.2.dylib
:info:build   Referenced from:
/Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/framework/OSXFUSE.framework/Versions/A/OSXFUSE
:info:build   Reason: image not found
:info:build Can't execute compiled C code... aborting
:info:build line was:
DYLD_FRAMEWORK_PATH="/Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/framework"
/Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/.tmp/bin-0-81104
:info:build binary is
/Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/.tmp/bin-0-81104
:info:build Usage: gen_bridge_metadata [options] 
:info:build Use the `-h' flag or consult gen_bridge_metadata(1) for help.
:info:build Command /bin/sh failed with exit code 1
:info:build Command /bin/sh failed with exit code 1
:info:build Touch
/Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/framework/OSXFUSE.framework
:info:build cd
/Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953/framework
:info:build /usr/bin/touch -c
/Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/framework/OSXFUSE.framework
:info:build
:info:build Strip
/Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/framework/OSXFUSE.framework/Versions/A/OSXFUSE
:info:build cd
/Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953/framework
:info:build /Developer/usr/bin/strip -x
/Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/framework/OSXFUSE.framework/Versions/A/OSXFUSE
:info:build
:info:build ** BUILD FAILED **
:info:build
:info:build
:info:build The following build commands failed:
:info:build OSXFUSE:
:info:build PhaseScriptExecution "BridgeSupport Metadata"
/Volumes/MacPorts/hopeful/build/_Users_davide_ports-substitution_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-cc7d953/framework/build/OSXFUSE.build/Release/OSXFUSE.build/Script-28D525C40EA8076400B7CF7B.sh
:info:build (1 failure)
```
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: osxfuse

[Dan Ports]

I just committed an upgrade to osxfuse 3.5.0 which should fix building
on Sierra.

Dan

On Fri, Sep 23, 2016 at 09:57:17PM +0200, Raoul MEGELAS wrote:
> Hello all,
> 
> osxfuse does not build.
> I reinstalled macports after 
> upgrading to 10.12.0.
> 
> trying to build opencv, i get this:
> 
> 
> …
> :debug:build Executing org.macports.build (osxfuse)
> :debug:build Environment: 
> CC_PRINT_OPTIONS='YES'
> CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work/.CC_PRINT_OPTIONS'
> CPATH='/opt/local/include'
> LIBRARY_PATH='/opt/local/lib'
> MACOSX_DEPLOYMENT_TARGET='10.12'
> :debug:build Assembled command: 'cd 
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-bf71481"
>  && ./build.sh -t homebrew -f /opt/local'
> :debug:build Executing command line:  cd 
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-bf71481"
>  && ./build.sh -t homebrew -f /opt/local 
> :info:build OSXFUSEBuildTool(): supported platforms: 10.11
> :info:build OSXFUSEBuildTool(): building OSXFUSE kernel extension 
> and tools
> :info:build xcrun: error: missing DEVELOPER_DIR path: 
> :info:build OSXFUSEBuildTool() failed: xcodebuild cannot build configuration 
> Release.
> :info:build Command failed:  cd 
> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-bf71481"
>  && ./build.sh -t homebrew -f /opt/local 
> :info:build Exit code: 1
> :error:build org.macports.build for port osxfuse returned: command execution 
> failed
> :debug:build Error code: CHILDSTATUS 48607 1
> :debug:build Backtrace: command execution failed
> while executing
> "system -nice 0 $fullcmdstring"
> ("eval" body line 1)
> invoked from within
> "eval system $notty $nice \$fullcmdstring"
> invoked from within
> "command_exec build"
> (procedure "portbuild::build_main" line 8)
> invoked from within
> "portbuild::build_main org.macports.build"
> ("eval" body line 1)
> invoked from within
> "eval $procedure $targetname"
> :info:build Warning: targets not executed for osxfuse: org.macports.activate 
> org.macports.build org.macports.destroot org.macports.install
> 
> any idea?
> 
> thanks in advance.
> 
> Raoul
> 
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users

-- 
Dan R. K. PortsUW CSEhttp://drkp.net/
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: osxfuse

[Raoul MEGELAS]

> On 23 Sep 2016, at 22:12, Ken Cunningham  
> wrote:
> 
> 
> On 2016-09-23, at 12:57 PM, Raoul MEGELAS wrote:
> 
>> info:build OSXFUSEBuildTool()    : building OSXFUSE kernel extension 
>> and tools
>> :info:build xcrun: error: missing DEVELOPER_DIR path: 
>> :info:build OSXFUSEBuildTool() failed: xcodebuild cannot build configuration 
>> Release.
> 
> Looks like a cmake issue. 
> 
> xcrun is gone, so there is no Developer_Dir found
> 
> if you edit the script (look into similar errors in qt5) to change xcrun to 
> xcodebuild you might get somewhere.
> 
> check this <https://trac.macports.org/ticket/52310 
> <https://trac.macports.org/ticket/52310>>
> 
> K
> 
> 
Hi, 

Thanks, for your reply,  i will  explore that.

Raoul
rm...@orange.fr <mailto:rm...@orange.fr>


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: osxfuse

[Raoul MEGELAS]

Thanks  i  will  see that.

Raoul

> On 23 Sep 2016, at 22:05, Brandon Allbery  wrote:
> 
> 
> On Fri, Sep 23, 2016 at 3:57 PM, Raoul MEGELAS  > wrote:
> :info:build OSXFUSEBuildTool(): supported platforms: 10.11
> 
> If there is an upstream update for Sierra then you can file a ticket to 
> update to it. If not, MacPorts cannot port the kernel module to the new 
> kernel for you.
> 
> -- 
> brandon s allbery kf8nh   sine nomine associates
> allber...@gmail.com   
> ballb...@sinenomine.net 
> unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net 
> 
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: osxfuse

[Ken Cunningham]

On 2016-09-23, at 12:57 PM, Raoul MEGELAS wrote:

> info:build OSXFUSEBuildTool(): building OSXFUSE kernel extension 
> and tools
> :info:build xcrun: error: missing DEVELOPER_DIR path: 
> :info:build OSXFUSEBuildTool() failed: xcodebuild cannot build configuration 
> Release.

Looks like a cmake issue. 

xcrun is gone, so there is no Developer_Dir found

if you edit the script (look into similar errors in qt5) to change xcrun to 
xcodebuild you might get somewhere.

check this <https://trac.macports.org/ticket/52310>

K


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: osxfuse

[Brandon Allbery]

On Fri, Sep 23, 2016 at 3:57 PM, Raoul MEGELAS  wrote:

> :info:build OSXFUSEBuildTool(): supported platforms: 10.11


If there is an upstream update for Sierra then you can file a ticket to
update to it. If not, MacPorts cannot port the kernel module to the new
kernel for you.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

osxfuse

[Raoul MEGELAS]

Hello all,

osxfuse does not build.
I reinstalled macports after 
upgrading to 10.12.0.

trying to build opencv, i get this:


…
:debug:build Executing org.macports.build (osxfuse)
:debug:build Environment: 
CC_PRINT_OPTIONS='YES'
CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work/.CC_PRINT_OPTIONS'
CPATH='/opt/local/include'
LIBRARY_PATH='/opt/local/lib'
MACOSX_DEPLOYMENT_TARGET='10.12'
:debug:build Assembled command: 'cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-bf71481"
 && ./build.sh -t homebrew -f /opt/local'
:debug:build Executing command line:  cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-bf71481"
 && ./build.sh -t homebrew -f /opt/local 
:info:build OSXFUSEBuildTool()    : supported platforms: 10.11
:info:build OSXFUSEBuildTool(): building OSXFUSE kernel extension 
and tools
:info:build xcrun: error: missing DEVELOPER_DIR path: 
:info:build OSXFUSEBuildTool() failed: xcodebuild cannot build configuration 
Release.
:info:build Command failed:  cd 
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-bf71481"
 && ./build.sh -t homebrew -f /opt/local 
:info:build Exit code: 1
:error:build org.macports.build for port osxfuse returned: command execution 
failed
:debug:build Error code: CHILDSTATUS 48607 1
:debug:build Backtrace: command execution failed
while executing
"system -nice 0 $fullcmdstring"
("eval" body line 1)
invoked from within
"eval system $notty $nice \$fullcmdstring"
invoked from within
"command_exec build"
(procedure "portbuild::build_main" line 8)
invoked from within
"portbuild::build_main org.macports.build"
("eval" body line 1)
invoked from within
"eval $procedure $targetname"
:info:build Warning: targets not executed for osxfuse: org.macports.activate 
org.macports.build org.macports.destroot org.macports.install

any idea?

thanks in advance.

Raoul

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Does osxfuse require Xcode.app to be in top-level /Applications?

[Ryan Schmidt]

On Sep 9, 2015, at 12:15 AM, Art McGee wrote:

> My setup:
> 
> xcode-select -p
> /Applications/Xcode/Xcode.app/Contents/Developer
> 
> xcrun -f xcodebuild
> /Applications/Xcode/Xcode.app/Contents/Developer/usr/bin/xcodebuild
> 
> xcodebuild -version
> Xcode 6.4
> Build version 6E35b
> 
> xcrun -f clang
> /Applications/Xcode/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang
> 
> I wasn't sure, but had read assumptions that osxfuse needs Xcode.app to be in 
> top-level /Applications and no where else. Is that correct?

My reading of the osxfuse build.sh script is that yes, it is looking for Xcode 
to be directly in the /Applications folder. It can have any name you want, but 
must be directly in that folder, not a subfolder.

This is clearly dumb and you should file a bug report about it.

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Does osxfuse require Xcode.app to be in top-level /Applications?

[Art McGee]

After the MacPorts update to osxfuse 2.8.0, I get this on 10.10.5:

:notice:build --->  Building osxfuse

:debug:build Executing org.macports.build (osxfuse)

:debug:build Environment:
CC_PRINT_OPTIONS='YES'
CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work/.CC_PRINT_OPTIONS'
CPATH='/opt/local/include'
LIBRARY_PATH='/opt/local/lib'
MACOSX_DEPLOYMENT_TARGET='10.10'

:debug:build Assembled command: 'cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-6a1e779"
&& ./build.sh -t homebrew -f /opt/local'

:debug:build Executing command line:  cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-6a1e779"
&& ./build.sh -t homebrew -f /opt/local

:info:build OSXFUSEBuildTool() failed: no supported version of Xcode found.

:info:build Command failed:  cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-6a1e779"
&& ./build.sh -t homebrew -f /opt/local

:info:build Exit code: 1

:error:build org.macports.build for port osxfuse returned: command
execution failed

My setup:

xcode-select -p
/Applications/Xcode/Xcode.app/Contents/Developer

xcrun -f xcodebuild
/Applications/Xcode/Xcode.app/Contents/Developer/usr/bin/xcodebuild

xcodebuild -version
Xcode 6.4
Build version 6E35b

xcrun -f clang
/Applications/Xcode/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang

I wasn't sure, but had read assumptions that osxfuse needs Xcode.app to be
in top-level /Applications and no where else. Is that correct?

Art
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: osxfuse i386 blocks ntfs3g x86_64

[Ryan Schmidt]

On Apr 18, 2014, at 09:46, Alexey Luchko wrote:

> just for information
> 
> $ sudo port uninstall fuse4x fuse4x-kext ntfs-3g testdisk
> $ sudo port install testdisk
> --->  Computing dependencies for testdisk
> Error: Cannot install ntfs-3g for the arch(s) 'x86_64' because
> Error: its dependency osxfuse only supports the arch(s) 'i386'.
> Error: Unable to execute port: architecture mismatch
> 
> $ port version
> Version: 2.2.1
> 
> $ uname -mprsv
> Darwin 11.4.2 Darwin Kernel Version 11.4.2: Thu Aug 23 16:26:45 PDT
> 2012; root:xnu-1699.32.7~1/RELEASE_I386 i386 i386
> 
> About This Mac tells 10.7.5.

You should file bug reports in the issue tracker.



___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

osxfuse i386 blocks ntfs3g x86_64

[Alexey Luchko]

just for information

$ sudo port uninstall fuse4x fuse4x-kext ntfs-3g testdisk
$ sudo port install testdisk
--->  Computing dependencies for testdisk
Error: Cannot install ntfs-3g for the arch(s) 'x86_64' because
Error: its dependency osxfuse only supports the arch(s) 'i386'.
Error: Unable to execute port: architecture mismatch

$ port version
Version: 2.2.1

$ uname -mprsv
Darwin 11.4.2 Darwin Kernel Version 11.4.2: Thu Aug 23 16:26:45 PDT
2012; root:xnu-1699.32.7~1/RELEASE_I386 i386 i386

About This Mac tells 10.7.5.

--
Regards
Alex
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users