Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't compile on Fedora 39 #1061

Closed
ivanaraolaza opened this issue Mar 31, 2024 · 2 comments
Closed

Can't compile on Fedora 39 #1061

ivanaraolaza opened this issue Mar 31, 2024 · 2 comments

Comments

@ivanaraolaza
Copy link

I'm running Fedora 39 on Wayland Hyprland.
This is the output when I try to run cargo build --release --no-default-features --features=wayland

   Compiling gio-sys v0.17.10
   Compiling pango-sys v0.17.10
   Compiling atk-sys v0.17.0
   Compiling dbusmenu-glib-sys v0.1.0
   Compiling time v0.3.34
   Compiling chrono v0.4.26
   Compiling zvariant v3.15.0
   Compiling rand_chacha v0.3.1
The following warnings were emitted during compilation:

warning: dbusmenu-glib-sys@0.1.0: `PKG_CONFIG_ALLOW_SYSTEM_CFLAGS="1" "pkg-config" "--libs" "--cflags" "dbusmenu-glib-0.4" "dbusmenu-glib-0.4 >= 16"` did not exit successfully: exit status: 1

error: failed to run custom build command for `dbusmenu-glib-sys v0.1.0`

Caused by:
  process didn't exit successfully: `/home/ivoo/eww/target/release/build/dbusmenu-glib-sys-1622441d7b728c53/build-script-build` (exit status: 1)
  --- stdout
  cargo:rerun-if-env-changed=DBUSMENU_GLIB_0.4_NO_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
  cargo:warning=`PKG_CONFIG_ALLOW_SYSTEM_CFLAGS="1" "pkg-config" "--libs" "--cflags" "dbusmenu-glib-0.4" "dbusmenu-glib-0.4 >= 16"` did not exit successfully: exit status: 1
  error: could not find system library 'dbusmenu-glib-0.4' required by the 'dbusmenu-glib-sys' crate

  --- stderr
  Package dbusmenu-glib-0.4 was not found in the pkg-config search path.
  Perhaps you should add the directory containing `dbusmenu-glib-0.4.pc'
  to the PKG_CONFIG_PATH environment variable
  Package 'dbusmenu-glib-0.4', required by 'virtual:world', not found
  Package 'dbusmenu-glib-0.4', required by 'virtual:world', not found

warning: build failed, waiting for other jobs to finish...

The packages that provide dbusmenu-glib on Fedora are actually dbus-glib and dbus-glib-devel

I'm pretty new to Rust, so how can I make the necessary modifications to make eww compile?

@itsjunetime
Copy link
Contributor

I had to install libdbusmenu-gtk3-devel on fedora 39 to get past this error, personally. Hope that does the trick for you

@ivanaraolaza
Copy link
Author

Yes, definitely solved the issue. Many thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants