Package Details: polybar 3.1.0-4

Git Clone URL: https://aur.archlinux.org/polybar.git (read-only)
Package Base: polybar
Description: A fast and easy-to-use status bar
Upstream URL: https://github.com/jaagr/polybar
Keywords: bar bspwm i3 lemonbar lemonbuddy polybar
Licenses: MIT
Conflicts: polybar-git
Submitter: jaagr
Maintainer: jaagr (NBonaparte, patrick96)
Last Packager: NBonaparte
Votes: 96
Popularity: 10.654778
First Submitted: 2016-11-19 05:09
Last Updated: 2018-03-21 01:03

Dependencies (18)

Required by (0)

Sources (1)

Latest Comments

friday13 commented on 2018-04-11 14:41

@patrick96 i installed depenciedies one by one and work fk this shit.. cairo libxcb xcb-proto xcb-util-image xcb-util-wm xcb-util-xrm

friday13 commented on 2018-04-11 14:35

@patrick96 yes installed but contunie problem :(

patrick96 commented on 2018-04-11 14:28

@friday13 do you have xcb-util-cursor or any of the xcb-util-* dependencies installed?

friday13 commented on 2018-04-11 14:19

@patrick96 yep i try but my problem continues CMake Error at lib/xpp/CMakeLists.txt:55 (message): Missing required python module: xcbgen

-- Configuring incomplete, errors occurred! See also "/home/friday/polybar/build/CMakeFiles/CMakeOutput.log". See also "/home/friday/polybar/build/CMakeFiles/CMakeError.log".

cmake.error log

Determining if the pthread_create exist failed with the following output: Change Dir: /home/friday/polybar/build/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_0d242/fast" /usr/bin/make -f CMakeFiles/cmTC_0d242.dir/build.make CMakeFiles/cmTC_0d242.dir/build make[1]: Entering directory '/home/friday/polybar/build/CMakeFiles/CMakeTmp' Building C object CMakeFiles/cmTC_0d242.dir/CheckSymbolExists.c.o /usr/bin/cc -o CMakeFiles/cmTC_0d242.dir/CheckSymbolExists.c.o -c /home/friday/polybar/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c Linking C executable cmTC_0d242 /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_0d242.dir/link.txt --verbose=1 /usr/bin/cc -rdynamic CMakeFiles/cmTC_0d242.dir/CheckSymbolExists.c.o -o cmTC_0d242 CMakeFiles/cmTC_0d242.dir/CheckSymbolExists.c.o: In function main': CheckSymbolExists.c:(.text+0x1b): undefined reference topthread_create' collect2: error: ld returned 1 exit status make[1]: [CMakeFiles/cmTC_0d242.dir/build.make:98: cmTC_0d242] Error 1 make[1]: Leaving directory '/home/friday/polybar/build/CMakeFiles/CMakeTmp' make: [Makefile:126: cmTC_0d242/fast] Error 2

File /home/friday/polybar/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c: / /

include <pthread.h></pthread.h>

int main(int argc, char** argv) { (void)argv;

ifndef pthread_create

return ((int*)(&pthread_create))[argc];

else

(void)argc; return 0;

endif

}

patrick96 commented on 2018-04-11 12:01

@friday13 Do you also have this problem when you manually download the PKGBUILD and build it?

friday13 commented on 2018-04-11 11:37

-- Configuring incomplete, errors occurred! See also "/tmp/yaourt-tmp-friday/aur-polybar-

Determining if the pthread_create exist failed with the following output: Change Dir: /home/friday13/polybar/build/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_85dd6/fast" /usr/bin/make -f CMakeFiles/cmTC_85dd6.dir/build.make CMakeFiles/cmTC_85dd6.dir/build make[1]: Entering directory '/home/friday13/polybar/build/CMakeFiles/CMakeTmp' Building C object CMakeFiles/cmTC_85dd6.dir/CheckSymbolExists.c.o /usr/bin/cc -o CMakeFiles/cmTC_85dd6.dir/CheckSymbolExists.c.o -c /home/friday13/polybar/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c Linking C executable cmTC_85dd6 /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_85dd6.dir/link.txt --verbose=1 /usr/bin/cc -rdynamic CMakeFiles/cmTC_85dd6.dir/CheckSymbolExists.c.o -o cmTC_85dd6 CMakeFiles/cmTC_85dd6.dir/CheckSymbolExists.c.o: In function main': CheckSymbolExists.c:(.text+0x1b): undefined reference topthread_create' collect2: error: ld returned 1 exit status make[1]: [CMakeFiles/cmTC_85dd6.dir/build.make:98: cmTC_85dd6] Error 1 make[1]: Leaving directory '/home/friday13/polybar/build/CMakeFiles/CMakeTmp' make: [Makefile:126: cmTC_85dd6/fast] Error 2

File /home/friday13/polybar/build/CMakeFiles/CMakeTmp/CheckSymbolExists.c: / /

include <pthread.h></pthread.h>

int main(int argc, char** argv) { (void)argv;

ifndef pthread_create

return ((int*)(&pthread_create))[argc];

else

(void)argc; return 0;

endif

}

patrick96 commented on 2018-03-19 12:25

@Chais Maybe you can configure your build system to have i3 and the other dependencies installed before it builds polybar.

Ah yes, that note is kind of useless, since i3 support is automatically enabled, if possible. I have changed it to somerthing more meaningful. It probably couldn't find ipc.h, which is a header file provided by the i3-wm package

Chais commented on 2018-03-19 03:10

@patrick96 Right, I forgot about that. Seems I'll have to keep editing the PKGBUILD then :/ or autopatch it. I added -DENABLE_I3=ON because (the polybar wiki)[https://github.com/jaagr/polybar/wiki/Module:-i3] suggested to do so and added the checkout because cmake complained it couldn't find ipc.cpp. But if it works without those steps as long as i3-wm and jsoncpp are installed at compile time, that's fine.

patrick96 commented on 2018-03-18 23:59

@Chais Alright, that's great, it was probably caused by an unsuccessful pull in the AUR repo or something like this. For the makdepends, if you uninstall the optdepends after the build, polybar will refuse to run, because it can't load the shared libraries it was compiled against provided by these packages. The only package where this doesn't happen, is i3-wm, since only the i3 executable and one header file (w/o shared library) is needed, I will open a PR to update the PKGBUILDs for that.

In your PKGBUILD, I don't see why you explicitly add the -DENABLE_I3=ON flag, since i3 support is enabled automatically, if the i3 executable is found. Also you don't need to checkout the i3ipcpp submodule manually, this is also already done, by git -C "${pkgname}" submodule update --init --recursive

Chais commented on 2018-03-18 23:30

@patrick96 it seems to have been a particular version of polybar or aurutils. It works now. And no, it wouldn't make them hard dependencies. I agree that the combination of optdepend and makedepend for the same package is somewhat unusual, but building with makepkg -r will remove the packages after the build.

In other news the polybar packages was restructured in a way that necessitates further changes to the PKGBUILD. i3ipc++ is now a submodule that needs to be checked out and the i3 module now also depends on i3-wm. Also a compile option was added for the i3 module to be built.

Here's a PKGBUILD that reflects all those changes: https://gist.github.com/3b28f4502af892c0f764d86a85339c93

All comments