Opened 8 weeks ago

Last modified 2 days ago

#59316 assigned defect

osxfuse @3.8.3: Build fails with SIGTERM

Reported by: andrey-popov (Andrey Popov) Owned by: drkp (Dan Ports)
Priority: Normal Milestone:
Component: ports Version: 2.6.1
Keywords: catalina Cc: svalgaard (Jens Svalgaard Kohrt), michaellass (Michael Lass)
Port: osxfuse

Description

Build of osxfuse @3.8.3 fails by SIGTERM on macOS 10.15 with Xcode 11.1. Here is the (somewhat?) relevant part from the log:

:info:build ^[[1;31mAssertion 'common_is_variable DEFAULT_SDK_10_15_ARCHITECURES' failed^[[0m
:info:build ^[[1;31mat common_variable_clone (./build.d/lib/common.sh, line 501)^[[0m
:info:build ^[[1;31mat common_variable_clone (./build.d/lib/common.sh, line 514)^[[0m
:info:build ^[[1;31mat build_target_invoke (./build.sh, line 657)^[[0m
:info:build ^[[1;31mat build_main (./build.sh, line 943)^[[0m
:info:build ^[[1;31mat main (./build.sh, line 951)^[[0m
:info:build ^GTerminated: 15
:info:build ^[[0;37mReceived signal: SIGTERM^[[0m
: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-48bc246"    && ./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 Killed by signal: 15
:error:build Failed to build osxfuse: command execution failed

I'm attaching the full log. This doesn't seem to be the same problem as in #54939 as the log doesn't mention LoadError.

Attachments (3)

main.log (300.0 KB) - added by andrey-popov (Andrey Popov) 8 weeks ago.
main.2.log (311.0 KB) - added by knightjp 8 weeks ago.
Main - 2
Screen Shot 2019-10-14 at 9.31.25 PM.png (427.9 KB) - added by knightjp 8 weeks ago.
FUSE not getting detected as installed

Download all attachments as: .zip

Change History (21)

Changed 8 weeks ago by andrey-popov (Andrey Popov)

Attachment: main.log added

comment:1 Changed 8 weeks ago by mf2k (Frank Schima)

Cc: drkp removed
Owner: set to drkp
Status: newassigned

Changed 8 weeks ago by knightjp

Attachment: main.2.log added

Main - 2

comment:2 Changed 8 weeks ago by knightjp

I am facing issues in getting osxfuse installed. The package I was hoping to install is ntfs-3g and osxfuse is a vital dependency.

Of course I'm not a developer, but if I were to think about it, I am guessing the change to zsh by Catalina does have an effect on the current scripts.

comment:3 Changed 8 weeks ago by yan12125 (Chih-Hsuan Yen)

Keywords: catalina added

Per https://github.com/osxfuse/osxfuse/releases, Catalina support is available since 3.10.0, while the one in MacPorts is kept at 3.8.x as osxfuse is no longer an open source project since version 3.9.0 (1).

(1) https://github.com/osxfuse/osxfuse/issues/590.

comment:4 in reply to:  3 Changed 8 weeks ago by knightjp

Replying to yan12125:

Per https://github.com/osxfuse/osxfuse/releases, Catalina support is available since 3.10.0, while the one in MacPorts is kept at 3.8.x as osxfuse is no longer an open source project since version 3.9.0 (1).

(1) https://github.com/osxfuse/osxfuse/issues/590.

Why doesn't my current install of Macports detect that I have FUSE installed?

Changed 8 weeks ago by knightjp

FUSE not getting detected as installed

comment:5 Changed 8 weeks ago by pmininni (Pablo Mininni)

I was able to build ntfs-3g in Catalina by installing the latest version of OSXFuse (3.10.3) from https://github.com/osxfuse/osxfuse/releases, and then doing:

sudo ln -s /usr/local/lib/pkgconfig/fuse.pc /opt/local/lib/pkgconfig/fuse.pc
sudo port install ntfs-3g

The ntfs-3g port doesn't require OSXFuse from Macports to build, just the fuse.pc file. I was able to build and install the ntfs-3g port, and it seems to work fine. Maybe the portfile can be modified to look for fuse.pc in /usr/local/lib/pkgconfig, where the recent version of OSXFuse (needed for Catalina) places this file.

Last edited 8 weeks ago by pmininni (Pablo Mininni) (previous) (diff)

comment:6 in reply to:  5 ; Changed 8 weeks ago by knightjp

Replying to pmininni:

I was able to build ntfs-3g in Catalina by installing the latest version of OSXFuse (3.10.3) from The ntfs-3g port doesn't require OSXFuse from Macports to build, just the fuse.pc file. I was able to build and install the ntfs-3g port, and it seems to work fine. Maybe the portfile can be modified to look for fuse.pc in /usr/local/lib/pkgconfig, where the recent version of OSXFuse (needed for Catalina) places this file.

If you installed ntfs-3g, how did you get around perl5.28? I understand that it has issues as well.

comment:7 in reply to:  6 ; Changed 8 weeks ago by pmininni (Pablo Mininni)

Replying to knightjp:

If you installed ntfs-3g, how did you get around perl5.28? I understand that it has issues as well.

I had no problem with perl5.28 (@5.28.2_0). From what I can see, the latest Portfile already has implemented the "use_parallel_build no" fix reported in #59207. Try cleaning the port and reinstalling.

comment:8 in reply to:  5 Changed 8 weeks ago by knightjp

Replying to pmininni:

I was able to build ntfs-3g in Catalina by installing the latest version of OSXFuse (3.10.3) from https://github.com/osxfuse/osxfuse/releases, and then doing:

sudo ln -s /usr/local/lib/pkgconfig/fuse.pc /opt/local/lib/pkgconfig/fuse.pc
sudo port install ntfs-3g

I have FUSE (3.10.3) installed. I tried the command that you mentioned. It doesn't work. All I get is

ln: /opt/local/lib/pkgconfig/fuse.pc: No such file or directory

Any ideas?

comment:9 in reply to:  7 ; Changed 7 weeks ago by knightjp

Replying to pmininni:

Replying to knightjp:

If you installed ntfs-3g, how did you get around perl5.28? I understand that it has issues as well.

I had no problem with perl5.28 (@5.28.2_0). From what I can see, the latest Portfile already has implemented the "use_parallel_build no" fix reported in #59207. Try cleaning the port and reinstalling.

After installing ntfs, I have another issue with using the commands on this link.

wiki:howto/Ntfs3gFinder

When I use this command,

sudo mv /sbin/mount_ntfs /sbin/mount_ntfs.orig

I get this error.

mv: rename /sbin/mount_ntfs to /sbin/mount_ntfs.orig: Read-only file system
Last edited 5 weeks ago by ryandesign (Ryan Schmidt) (previous) (diff)

comment:10 in reply to:  9 Changed 7 weeks ago by pmininni (Pablo Mininni)

Replying to knightjp:

After installing ntfs, I have another issue with using the commands on this link.

wiki:howto/Ntfs3gFinder

When I use this command,

sudo mv /sbin/mount_ntfs /sbin/mount_ntfs.orig

I get this error.

mv: rename /sbin/mount_ntfs to /sbin/mount_ntfs.orig: Read-only file system

This is caused by the security changes in Catalina. The system is now in a read-only file system. You can manually mount NTFS filesystems from the command line. Or, if you want to have NTFS filesystems showing up automatically in Finder (with write permission), you have to do some extra work. Besides disabling (temporarily) SIP with the command "csrutil disable", you also have to unlock the volume so you can write to it. The following link explains how to do it:

https://github.com/osxfuse/osxfuse/wiki/NTFS-3G#auto-mount-ntfs-volumes-in-read-write-mode-on-macos-1015-catalina

I haven't tried it yet, but I would follow these instructions only to enable writing to the filesystem (i.e., disabling SIP, unlocking the volume, and re-enabling SIP). I would not do a symbolic link ("ln -s") as suggested there, as linking to a file outside /sbin can create a security issue. Instead, I will do what is suggested in wiki:howto/Ntfs3gFinder: You back-up /sbin/mount_ntfs and then create a new /sbin/mount_ntfs with the script provided in wiki:howto/Ntfs3gFinder.

Last edited 5 weeks ago by ryandesign (Ryan Schmidt) (previous) (diff)

comment:11 Changed 7 weeks ago by raulofpandora

Same happens here trying to install encfs using macports, it needs osxfuse, but doesn't compile.

I installed FUSE for macOS 3.10.3 from its page, created the suggested soft links, but encfs doesn't detect it and macports try to compile osxfuse unsuccessfully.

Any thoughts?

comment:12 in reply to:  3 Changed 5 weeks ago by ryandesign (Ryan Schmidt)

Replying to yan12125:

Per https://github.com/osxfuse/osxfuse/releases, Catalina support is available since 3.10.0, while the one in MacPorts is kept at 3.8.x as osxfuse is no longer an open source project since version 3.9.0 (1).

(1) https://github.com/osxfuse/osxfuse/issues/590.

This does not seem to be a valid justification to avoid updating the port in MacPorts. On Mavericks and later, we already download and install the signed binary from the developer, and don't build from source. There's no reason why we can't update to the latest version and continue to do that for Mavericks and later (or whatever minimum OS versions the latest release supports) and change the license to "Restrictive", while perhaps continuing to use the older BSD/APSL-licensed release for older macOS versions if needed.

comment:13 Changed 4 weeks ago by mike-kfed (Michael Kefeder)

I found a mailinglist post with a hint how to fix the build

  1. run port install osxfuse (it will fail)
  2. open the file build.d/defaults.sh in your temporary build-dir e.g. sudo vim /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work/osxfuse-osxfuse-48bc246//build.d/defaults.sh
  1. copy the 10.14 declarations and change to 10.15
    declare -ra DEFAULT_SDK_10_15_ARCHITECURES=("i386" "x86_64")
    declare -r  DEFAULT_SDK_10_15_COMPILER="com.apple.compilers.llvm.clang.1_0"
    
    declare -ra DEFAULT_SDK_SUPPORTED=("10.9" "10.10" "10.11" "10.12" "10.13" "10.15")
    
  1. save the file and
  2. run port install osxfuse again

comment:14 in reply to:  13 Changed 4 weeks ago by mike-kfed (Michael Kefeder)

Replying to mike-kfed: side note: I only needed it to install at all to build encfs (to have headers and stuff of osxfuse on my system). I uninstalled macports osxfuse and used their v3.10 binary provided at https://osxfuse.github.io/ for my catalina system. macports should provide a osxfuse-3.10 port

comment:15 Changed 4 weeks ago by andrey-popov (Andrey Popov)

Cc: andrey-popov added

comment:16 Changed 4 weeks ago by andrey-popov (Andrey Popov)

Cc: andrey-popov removed

comment:17 Changed 3 weeks ago by svalgaard (Jens Svalgaard Kohrt)

Cc: svalgaard added

comment:18 Changed 2 days ago by michaellass (Michael Lass)

Cc: michaellass added
Note: See TracTickets for help on using tickets.