Arch Linux User Repository

@everyone this package works again!

Adding sed -i 's/format(/boost\:\:format(/g' "${srcdir}/src/fatx.cpp" sed -i '184,927s/format(/boost\:\:format(/' "${srcdir}/src/fatx.hpp" to the PKGBUILD build() section, before the cmake commands allows this package to compile and install successfully.

@Halian - You say version 1.17 is outdated (I saw the email about you marking this package out of date), yet I can't find a download for 1.18 - yes, the page on sourceforge notes 1.18 was released, but there is no download for that version.

Also took notice you created a ticket on the project page on sourceforge. Post logs for me?

Throws a litany of “reference to ‘format’ is ambiguous” errors when attempting to build, because there are such-named functions in both std and boost.

Past week ended up getting slightly busy on my end, didn't forget about this.

So, I can replicate the issue with the cmake tests using "pkgctl build", yet if I disable the tests, it compiles as expected. It's definitely a weird issue, as installing the compiled binaries and running them, work as one would think.

I do notice however, there is decent change in file size, from compiling via pkgctl, versus compiling on my daily driver laptop. I'm a tiny bit stuck, as I have never troubleshot cmake tests or the like, letalone this is my first time working with pkgctl officially. If anyone has any input, I am all ears!

@katt - That being said, if you comment out the tests and compile, are you able to successfully use fatx?

@t3kk3n Sure, here's the output: https://gist.github.com/kattjevfel/39581c185f7d9a24ec634d48e5ace952

To try and cut down on any customization this was built with pkgctl build, which anyone with devtools can do.

Also given your responses thus far, do the tests work on your machine then?

@katt - Could you add the --verbose argument to ctest in the check function and rerun?

Side note - technically I could remove the check function, but would rather not.

@t3kk3n I am building for x86_64-v3 with aurutils in a chroot. Skipping the tests would obviously work since that's what's failing.

As for information that would help, build in a chroot I guess :P

katt - I'm unable to replicate what you are experiencing; What architecture are you compiling on? Have you tried compiling without running the tests? Any other information that could help?

Tests are failing:

24% tests passed, 16 tests failed out of 21

Total Test time (real) =   1.05 sec

The following tests FAILED:
          1 - Fuse_simple_file_creation (Failed)
          2 - Fuse_moving_file (Failed)
          3 - Fuse_removing_file (Failed)
          4 - Fuse_multiple_file_access (Failed)
          5 - Fuse_directory_copies (Failed)
          6 - Fuse_simultaneous_copies (Failed)
          7 - Fuse_directory_max_entries (Failed)
          8 - Fuse_recover_mode (Failed)
          9 - Fuse_FAT_stress (Failed)
         10 - Fuse_directory_entries_stress (Failed)
         11 - Fuse_simultaneous_creations (Failed)
         12 - Fuse_check_statfs (Failed)
         14 - Label_check_noname (Failed)
         18 - Unrm_remote_recovery (Failed)
         19 - Unrm_remote_dir_recovery (Failed)
         20 - Unrm_local_recovery (Failed)
Errors while running CTest
==> ERROR: A failure occurred in check().
    Aborting...
==> Removing chroot copy [/var/lib/aurbuild/x86_64/katt-229284]...done
==> ERROR: Build failed

@sl1pkn07 - Dang, you are fast haha. Was already working on that, thank you though.

Package is fully up to date and working as of now, cheers!