nofuse.patch is working incorrectly. It still relies on old code in "configure.ac".
Search Criteria
Package Details: exfat-utils-nofuse 1.4.0-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/exfat-utils-nofuse.git (read-only, click to copy) |
---|---|
Package Base: | exfat-utils-nofuse |
Description: | Utilities for the exFAT file system without fuse (to prefer exfat kernel module over fuse) |
Upstream URL: | https://github.com/relan/exfat |
Licenses: | GPL2 |
Conflicts: | exfat-utils, fuse-exfat |
Provides: | exfat-utils |
Submitter: | freswa |
Maintainer: | freswa |
Last Packager: | freswa |
Votes: | 31 |
Popularity: | 0.000000 |
First Submitted: | 2017-01-12 22:36 (UTC) |
Last Updated: | 2023-03-04 22:21 (UTC) |
Dependencies (1)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR, glibc-eac-binAUR, glibc-eac-rocoAUR)
Required by (6)
- gparted-git (requires exfat-utils) (optional)
- icedisk (requires exfat-utils)
- kpmcore-git (requires exfat-utils) (optional)
- montirovka (requires exfat-utils)
- usbmaker (requires exfat-utils) (optional)
- usbmaker-git (requires exfat-utils) (optional)
Sources (2)
sirHermit commented on 2023-03-04 07:40 (UTC) (edited on 2023-03-04 07:41 (UTC) by sirHermit)
MegaDeKay commented on 2020-02-24 02:36 (UTC)
Could you update this package to include this fix now committed to master. https://github.com/relan/exfat/commit/75f28b558a1a86b45308a3e7d0af222624bc2c61
This is a fix for a timezone bug that is currently breaking rsync to an external exFAT drive. Discussion here:
yan12125 commented on 2019-03-25 01:02 (UTC)
Wow, thanks for the ultra fast update!
yan12125 commented on 2019-03-23 06:17 (UTC)
Could you remove the 'replaces=' line from PKGBUILD? This field is for replacing obsolete packages [1], but exfat-utils is not obsolete.
tbk commented on 2019-03-10 12:38 (UTC)
Fuse is not needed as a dependency - https://github.com/relan/exfat/search?utf8=%E2%9C%93&q=fuse&type=
remove-fuse-module.patch
--- a/Makefile.am
+++ b/Makefile.am
@@ -20,4 +20,4 @@
# 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
#
-SUBDIRS = libexfat dump fsck fuse label mkfs
+SUBDIRS = libexfat dump fsck label mkfs
--- a/configure.ac
+++ b/configure.ac
@@ -37,13 +37,11 @@
AC_DEFINE([USE_UBLIO], [1],
[Define if block devices are not supported.])
], [:])
-PKG_CHECK_MODULES([FUSE], [fuse])
AC_CONFIG_HEADERS([libexfat/config.h])
AC_CONFIG_FILES([
libexfat/Makefile
dump/Makefile
fsck/Makefile
- fuse/Makefile
label/Makefile
mkfs/Makefile
Makefile])
polyzen commented on 2018-12-30 19:13 (UTC) (edited on 2018-12-30 19:14 (UTC) by polyzen)
Please bring this package to par with the exfat-utils
package: using prepare()
, respecting CPPFLAGS
, and installing the manuals.
https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/exfat-utils
bezirg commented on 2018-08-07 19:31 (UTC)
Shouldn't the fuse
package be a build dependency?
==> Starting build()...
...omitted...
checking for FUSE... no
configure: error: Package requirements (fuse) were not met:
Package 'fuse', required by 'virtual:world', not found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables FUSE_CFLAGS
and FUSE_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
==> ERROR: A failure occurred in build().
Aborting...
Medved commented on 2018-01-14 04:06 (UTC) (edited on 2018-01-14 04:07 (UTC) by Medved)
Build on a Raspberry Pi (Archlinux ARM distribution). Had to install "fuse" before - it has a build dependency, and added more architecture to the supported string:
arch=('i686' 'x86_64' 'mips64el' 'armv6h' 'armv7h' 'arm' 'aarch64')
makedepends=('fuse')
I guess you can include these into the PKGBUILD. There is no technical reason why it should not work on other architectures.
Pinned Comments
freswa commented on 2017-01-14 00:37 (UTC) (edited on 2017-01-14 00:37 (UTC) by freswa)