Lately I've been getting a "crashed with status 127" error message with this package. Thanks.
Search Criteria
Package Details: electricsheep-git 3.0.2.git.20221208.37ba0fd-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/electricsheep-git.git (read-only, click to copy) |
---|---|
Package Base: | electricsheep-git |
Description: | Electric Sheep is a collaborative abstract artwork founded by Scott Draves. (gold sheep supported!) |
Upstream URL: | http://gold.electricsheep.org/about |
Licenses: | GPL |
Conflicts: | electricsheep, electricsheep-svn |
Provides: | electricsheep |
Submitter: | bramswenson |
Maintainer: | EndlessEden |
Last Packager: | EndlessEden |
Votes: | 20 |
Popularity: | 0.000000 |
First Submitted: | 2017-12-16 00:44 (UTC) |
Last Updated: | 2022-12-07 14:16 (UTC) |
Dependencies (15)
- boost-libs (boost-libs-gitAUR)
- curl (curl-quiche-gitAUR, curl-gitAUR, curl-http3-ngtcp2AUR, curl-c-aresAUR)
- ffmpeg (ffmpeg-intel-full-gitAUR, ffmpeg-nvcodec-11-1-gitAUR, ffmpeg-gitAUR, ffmpeg-cudaAUR, ffmpeg-decklinkAUR, ffmpeg-amd-fullAUR, ffmpeg-libfdk_aacAUR, ffmpeg-full-gitAUR, ffmpeg-nocudaAUR, ffmpeg-ffplayoutAUR, ffmpeg-obsAUR, ffmpeg-amd-full-gitAUR, ffmpeg-fullAUR, ffmpeg-headlessAUR)
- flam3AUR
- freeglut (freeglut-x11-gitAUR, freeglut-wayland-gitAUR)
- gleeAUR (glee-svnAUR)
- libgtop
- lua51
- wxgtk3 (wxwidgets-gtk3)
- boost (boost-gitAUR) (make)
- git (git-gitAUR) (make)
- glu (glu-gitAUR) (make)
- mesa (mesa-nightly-nvk-rusticl-intelrt-gitAUR, amdonly-gaming-mesa-gitAUR, mesa-minimal-gitAUR, mesa-gitAUR, mesa-amber) (make)
- tinyxml (tinyxml-gitAUR) (make)
- xscreensaver (xscreensaver-xmatrix-colorAUR, xscreensaver-arch-logoAUR) (optional) – to use electricsheep with xscreensaver
Required by (0)
Sources (1)
whatshisname commented on 2023-03-18 22:58 (UTC)
EndlessEden commented on 2022-12-07 14:24 (UTC)
(temporarily?) took this over.
Fixed the pkgbuild so it actually builds, added some build-flags for compatibility, swapped wxgtk from wxgtk2 to wxgtk3 (they are compatible), slightly altered the versioning string to include data (Emulating the Official PPA's versioning string) and (temporarily) swapped source for ffmpeg5 patch thats been in the pull-requests since may-2022.
Should also heavily note: Upstream look incredibly inactive. I dont see anything going on in the repo (from the maintainers) since 2018/2019. So i would expect some server-side bugs and possible runtime bugs. | please share any info.
haawda commented on 2022-09-09 17:18 (UTC)
Upstreams seems to use git as version control system now.
electricprism commented on 2021-09-15 22:39 (UTC)
Seems like this information may be helpful:
https://github.com/scottdraves/electricsheep/wiki/Compiling
I also see Ubuntu packages here: electricsheep 3.0.2-git20191005-1ppa1~hirsute Ichthyostega (2021-04-23)
Cebtenzzre commented on 2019-06-26 18:12 (UTC) (edited on 2019-06-26 18:12 (UTC) by Cebtenzzre)
This does not compile for me, whereas the package 'electricsheep' builds just fine.
g++ -DPACKAGE_NAME=\"electricsheep\" -DPACKAGE_TARNAME=\"electricsheep\" -DPACKAGE_VERSION=\"2.7b33-svn\" -DPACKAGE_STRING=\"electricsheep\ 2.7b33-svn\" -DPACKAGE_BUGREPORT=\"http://code.google.com/p/electricsheep/issues/list\" -DPACKAGE_URL=\"\" -DPACKAGE=\"electricsheep\" -DVERSION=\"2.7b33-svn\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -D__EXTENSIONS__=1 -D_ALL_SOURCE=1 -D_GNU_SOURCE=1 -D_POSIX_PTHREAD_SEMANTICS=1 -D_TANDEM_SOURCE=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DSTDC_HEADERS=1 -DUSE_NEW_FFMPEG_API=1 -DHAVE_GLEE_H=1 -DHAVE_LIBBOOST_THREAD=1 -DHAVE_LIBBOOST_FILESYSTEM=1 -DHAVE_LIBBOOST_SYSTEM=1 -DHAVE_LIBTINYXML=1 -DHAVE_LIBGLUT=1 -DHAVE_LIBGL=1 -DHAVE_LIBRT=1 -I. -DPACKAGE_DATA_DIR=\""/usr/share"\" -DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" -I .. -iquote ../DisplayOutput/OpenGL -I ../Common -I ../DisplayOutput -I ../DisplayOutput/Renderer -I ../Common/Math -I ../ContentDecoder -I ../TupleStorage -I ../ContentDownloader -I ../lua5.1/src -I ../Client -I ../Networking -I ../tinyXml -D_FORTIFY_SOURCE=2 -DLINUX_GNU=1 -DSHAREDIR=\"/usr/share/electricsheep/\" -I/usr/include/libgtop-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/lua5.1 -I/usr/include/libpng16 -I/usr/include/lua5.1 -lrt -lz -lGL -D__STDC_CONSTANT_MACROS -Wno-write-strings -DHAVE_AVC_VID2=1 -march=native -O3 -pipe -fstack-protector-strong -fno-plt -MT Texture.o -MD -MP -MF .deps/Texture.Tpo -c -o Texture.o `test -f '../DisplayOutput/Renderer/Texture.cpp' || echo './'`../DisplayOutput/Renderer/Texture.cpp
../DisplayOutput/OpenGL/TextureFlatGL.cpp: In member function ‘virtual bool DisplayOutput::CTextureFlatGL::Upload(DisplayOutput::spCImage)’:
../DisplayOutput/OpenGL/TextureFlatGL.cpp:186:4: error: ‘glCompressedTexImage2DARB’ was not declared in this scope; did you mean ‘glCompressedTexImage2D’?
186 | glCompressedTexImage2DARB( m_TexTarget, mipMapLevel, internalFormat, _spImage->GetWidth( mipMapLevel ), _spImage->GetHeight( mipMapLevel ), 0, _spImage->getMipMappedSize( mipMapLevel, 1 ), pSrc );
| ^~~~~~~~~~~~~~~~~~~~~~~~~
| glCompressedTexImage2D
make[1]: *** [Makefile:790: TextureFlatGL.o] Error 1
Rogach commented on 2018-06-16 12:50 (UTC)
This currently fails during linking:
/usr/bin/ld: Voting.o: undefined reference to symbol 'pthread_condattr_setclock@@GLIBC_2.3.3'
/usr/lib/libpthread.so.0: error adding symbols: DSO missing from command line
Adding adding -lpthread to CXXFLAGS fixes the build:
make CXXFLAGS+="-DUSE_NEW_FFMPEG_API=1 -lpthread" GLEE_LIBS="-lGLee"
Pinned Comments
EndlessEden commented on 2022-12-07 14:24 (UTC)
(temporarily?) took this over.
Fixed the pkgbuild so it actually builds, added some build-flags for compatibility, swapped wxgtk from wxgtk2 to wxgtk3 (they are compatible), slightly altered the versioning string to include data (Emulating the Official PPA's versioning string) and (temporarily) swapped source for ffmpeg5 patch thats been in the pull-requests since may-2022.
Should also heavily note: Upstream look incredibly inactive. I dont see anything going on in the repo (from the maintainers) since 2018/2019. So i would expect some server-side bugs and possible runtime bugs. | please share any info.