Package Details: intiface-central 2.6.8-1

Git Clone URL: https://aur.archlinux.org/intiface-central.git (read-only, click to copy)
Package Base: intiface-central
Description: Intiface Central (Buttplug Frontend) Application for Desktop and Mobile
Upstream URL: https://intiface.com/central/
Licenses: GPL-3.0-only
Submitter: Bitals
Maintainer: Bitals
Last Packager: Bitals
Votes: 2
Popularity: 0.20
First Submitted: 2023-10-30 10:58 (UTC)
Last Updated: 2025-10-19 11:30 (UTC)

Latest Comments

TheNullPlayer commented on 2025-11-19 02:19 (UTC) (edited on 2025-11-19 04:31 (UTC) by TheNullPlayer)

There are some warnings that end up as errors so the issue lies in the CFLAGS environment variable. I was able to export the environment variable using:

'export CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe 
    -fno-plt -fexceptions
    -Wp,-D_FORTIFY_SOURCE=3 -Wformat
    -fstack-clash-protection -fcf-protection
    -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer 
    -g -ffile-prefix-map=$(pwd)=/usr/src/debug/${pkgname}";'

It should allow for warnings during compile time let me know if you narrow it down further. You can dump the build environment variables using the code below in the build function above the fix:

'env >> ENV.txt;'

Then read said file in the src directory for the CFLAGS environment variable and add arguments to the fix until it breaks.

TLDR: Basically there is a warning in version 2.6.8 and its being handled like an error.

maxyvisser commented on 2025-10-27 21:40 (UTC)

@Zsar Disabling lto in /etc/makepkg.conf solved this issue for me

Zsar commented on 2025-10-27 18:35 (UTC) (edited on 2025-10-27 18:37 (UTC) by Zsar)

All listed dependencies were provided as regular packages and are up-to-date.

Different error than the previous poster: libhidapi-0276261692855929.rlib: error adding symbols: file format not recognized

$ makepkg
[... usual first steps...]
==> Starting prepare()...

Completion files installed. To enable completion, run the following command in your shell:
source /home/Zsar/.bash_profile

[... Flutter SDK setup... ]
Setting up Flutter SDK: 3.27.1

Downloading Linux x64 Dart SDK from Flutter engine cb4b5fff73850b2e42bd4de7cb9a4310a78ac40d...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  212M  100  212M    0     0  9500k      0  0:00:22  0:00:22 --:--:-- 9261k
Building flutter tool...
Resolving dependencies... 
Downloading packages... (2.6s)
Got dependencies.
Flutter 3.27.1 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 17025dd882 (11 months ago) • 2024-12-17 03:23:09 +0900
Engine • revision cb4b5fff73
Tools • Dart 3.6.0 • DevTools 2.40.2

✓ Flutter SDK: SDK Version : 3.27.1 is setup
You should add the fvm version directory ".fvm/" to .gitignore.
[WARN] Skipping .gitignore confirmation because of --force flag detected
✓ Dependencies resolved. (22.7s)
✓ Project now uses Flutter SDK : SDK Version : 3.27.1
Setting "enable-linux-desktop" value to "true".

You may need to restart any open editors for them to read new settings.
==> Starting build()...
Downloading linux-x64-debug/linux-x64-flutter-gtk tools...          3.1s
Downloading linux-x64-profile/linux-x64-flutter-gtk tools...      1,482ms
Downloading linux-x64-release/linux-x64-flutter-gtk tools...      1,567ms

/home/Zsar/aur/intiface-central/src/intiface-central-2.6.8/build/linux/x64/release/_deps/sentry-native-src/external/crashpad/util/linux/thread_info.cc:22:10: warning: first argument in call to 'memset' is a pointer to non-trivially copyable type 'crashpad::ThreadContext' [-Wnontrivial-memcall]
/home/Zsar/aur/intiface-central/src/intiface-central-2.6.8/build/linux/x64/release/_deps/sentry-native-src/external/crashpad/util/linux/thread_info.cc:28:10: warning: first argument in call to 'memset' is a pointer to non-trivially copyable type 'crashpad::FloatContext' [-Wnontrivial-memcall]
    Updating crates.io index
     Locking 2 packages to latest compatible versions
    Updating buttplug v9.0.8 -> v9.0.9
    Updating intiface-engine v3.0.8 -> v3.0.9
 Downloading crates ...
[... library downloads...]
[... library compilations...]
   Compiling buttplug v9.0.9
error: linking with `/usr/bin/clang` failed: exit status: 1
  |
  = note: [... screen filling clang invocation...]
  = note: some arguments are omitted. use `--verbose` to show all linker arguments
  = note: /usr/bin/ld: /home/Zsar/aur/intiface-central/src/intiface-central-2.6.8/build/linux/x64/release/cargo/intiface-engine-flutter-bridge_ab181/x86_64-unknown-linux-gnu/release/deps/libhidapi-0276261692855929.rlib: error adding symbols: file format not recognized
          clang: error: linker command failed with exit code 1 (use -v to see invocation)


error: could not compile `buttplug` (lib) due to 1 previous error
/usr/bin/ld: warning: LLVM gold plugin: call to _curl_easy_setopt_err_long marked "dontcall-warn": curl_easy_setopt expects a long argument
Building Linux application...                                           
Build process failed
==> ERROR: A failure occurred in build().
    Aborting...

claymorwan commented on 2025-01-15 20:10 (UTC)

I get a massive error message followed by this

  = note: some `extern` functions couldn't be found; some native libraries may need to be installed or have their path specified
  = note: use the `-l` flag to specify native libraries to link
  = note: use the `cargo:rustc-link-lib` directive to specify the native libraries to link with Cargo (see https://doc.rust-lang.org/cargo/reference/build-scripts.html#rustc-link-lib)

warning: `intiface_engine_flutter_bridge` (lib) generated 6 warnings
error: could not compile `intiface_engine_flutter_bridge` (lib) due to 1 previous error; 6 warnings emitted
Building Linux application...
Build process failed
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'intiface-central-2.6.5-1':
error: packages failed to build: intiface-central-2.6

Bitals commented on 2024-06-13 12:03 (UTC) 

Target kernel_snapshot failed: Exception

Is NOT a packaging problem. It's an AUR/flutter problem. If you encounter this error, use a different flutter package, e.g. AUR/flutter-bin to build this and other flutter software.

Bitals commented on 2024-04-26 21:08 (UTC) (edited on 2024-04-26 21:10 (UTC) by Bitals)

Current workaround: build aur/flutter with aur/dart-sdk-dev as per the comment by @KI9N, than build this and other flutter projects. Added a corresponding error as a crutch to get user's attention for the time being.

Bitals commented on 2024-04-21 14:23 (UTC) (edited on 2024-04-22 09:24 (UTC) by Bitals)

Fails to compile with current (3.19.6-1) AUR Flutter packages, I've reported it, but for the time being nothing I can do.

I plan on not pushing 2.5.7 until this is resolved in order to avoid annoying users with an unbuildable update.

Bitals commented on 2023-10-30 11:12 (UTC) (edited on 2024-04-17 08:22 (UTC) by Bitals)

Before building flutter packages:

  1. Make sure the user making the package is in the flutterusers group;

  2. Flutter uses git under the hood to find out its own version, and git doesn't like that /opt/flutter is owned by root. So if you have any weird behavior, like getting the Flutter version of 0 while building, you also need to run: git config --global --add safe.directory /opt/flutter after installing flutter, or just build as root (not the best idea). This got fixed with the 2024-03-26 update to the flutter package (now actually pkgbase for a lot of split packages).