[Slackbuilds-users] wxcam compile errors on Slackware 15.0

Hello admins, wxcam-1.1 hasn't compiled (at leas not here) on Slackare for awhile and hasn't been updated upstream since 2011. Since I switched to guvcview, we can: 1. Drop it from SBo. 2. Put it up for grabs for someone to take over maintainership. -Ed

Re: [Slackbuilds-users] wxcam compile errors on Slackware 15.0

On 2/7/22 07:58, B Watson wrote: > On 2/6/22, King Beowulf wrote: > >> Sweet. Forgot about that one. My issue turn out to be the order of >> wxPython and wxGTK3 install and that stupid wx-config symlink. > > There are ways to write build scripts so they don't depe

Re: [Slackbuilds-users] wxcam compile errors on Slackware 15.0

On 2/5/22 22:37, Willy Sudiarto Raharjo wrote: >> wxcam-1.1 hasn't compiled (at leas not here) on Slackare for awhile and >> hasn't been updated upstream since 2011. Since I switched to guvcview, >> we can: >> >> 1. Drop it from SBo. >> 2. Put it up for grabs for someone to take over as

Re: [Slackbuilds-users] wxcam compile errors on Slackware 15.0

On 2/4/22 11:30, B Watson wrote: > On 2/4/22, King Beowulf wrote: >> (oops sent this via the wrong email address) >> >> Hello admins, >> >> wxcam-1.1 hasn't compiled (at leas not here) on Slackare for awhile and >> hasn't been updated upstream since 2011.

[Slackbuilds-users] wxcam compile errors on Slackware 15.0

(oops sent this via the wrong email address) Hello admins, wxcam-1.1 hasn't compiled (at leas not here) on Slackare for awhile and hasn't been updated upstream since 2011. Since I switched to guvcview, we can: 1. Drop it from SBo. 2. Put it up for grabs for someone to take over as maintainer.

Re: [Slackbuilds-users] Concerning 15.0 and 14.2

On 2/1/22 14:34, Arnaud via SlackBuilds-users wrote: > Well, Pat did write in this morning changelog « The cave is now closed ». > We are at 15.0 RC3. After that message there was "Hey, my shiny brass lamp is almost out of fuel!" Hopefully "real soon now!" -KB OpenPGP_signature Description:

Re: [Slackbuilds-users] Slacker reporting for duty

On 1/12/22 23:32, Roger Krowiak wrote: > Hi guys, > > I've never maintained any app, but I'm willing to help. So, do you have > any *easy going* app to maintain, which I can pick up? Also some > mentoring would be welcome. > > I've been using Slackware for a while and I've got moderate BASH

Re: [Slackbuilds-users] git access

On 10/13/21 12:21, Ruben Schuller wrote: > Hi list! > > I'm pretty sure it was already discussed here or I missed some > documentation, but what is the process to get git access to SBo? > It just would be easier to push updates to my SlackBuilds somewhere > instead of uploading a tarball, as i

Re: [Slackbuilds-users] Issue building qgis

On 10/1/21 08:14, Rich Shepard wrote: > Installed here is qt5-webkit-5.212.0_alpha4-x86_64-3_SBo. > > Building qgis fails with a qt5-webkit version error: > CMake Error at CMakeLists.txt:453 (find_package): >   Found package configuration file: > >    

Re: [Slackbuilds-users] foldingathome

On 9/26/21 10:34, Jude DaShiell wrote: > Would it be possible to get a foldingathome slackbuild script after > slackware 15.0 gets released? Many other distros have the capability to > build and contribute to this project but not so slackware yet at least > with slackbuilds. > We could set up a

[Slackbuilds-users] miniupnpc version bump

miniupnpc could use a version bump to 2.2.2 Works here RC1 updated today. -kb OpenPGP_signature Description: OpenPGP digital signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org

[Slackbuilds-users] audio/alsa-tools firmware update

It would be nice to have have alsa-tools firmware updated to 1.2.4 Seems to work ok here on both older and newer systems. cc: maintainer. -kb OpenPGP_signature Description: OpenPGP digital signature ___ SlackBuilds-users mailing list

[Slackbuilds-users] Version bump to miniupnpc 2.2.2 needed for SBo-pending ( Slackware-15 )

I received a notification of Gridcoin-Research-5.3.2 upgrade and noted that the build requirement is now minupnpc-2.2.2 (optional dep). Gridcoin-Research uses upstream code from bitcoin. miniupnpc-2.1 is still in master. cc: maintainer -kb OpenPGP_signature Description: OpenPGP digital

Re: [Slackbuilds-users] recent rc.murmur 'Create piddir during init' patch

On 7/17/21 8:23 PM, Robby Workman wrote: > On Sat, 17 Jul 2021 19:53:07 -0700 > King Beowulf wrote: > >> Hello >> >> the patch needs to not explicitly use the default murmur:murmur since >> this can be altered during build (see README) >> >> + chown

[Slackbuilds-users] recent rc.murmur 'Create piddir during init' patch

Hello the patch needs to not explicitly use the default murmur:murmur since this can be altered during build (see README) + chown murmur:murmur $(dirname $PIDFILE) to + chown @USER@:@GROUP@ $(dirname $PIDFILE) with corresponding added 'sed' and removal of '-e

[Slackbuilds-users] (no subject)

hello roccat-tools-5.9 does not detect 'lua' correctly. The stanza LUAVERSION="$( lua -e 'print(_VERSION)' | cut -d' ' -f2 )" LUA="-DWITH_LUA='$LUAVERSION' breaks with lua 5.2.x and lua 5.3.x since there is no 'lua' executable: # lua -e 'print(_VERSION)' -su: lua: command not found My

Re: [Slackbuilds-users] Moria

On 7/2/21 1:59 AM, David Chmelik wrote: > A SlackBuild I maintain, moria, no longer has a project/source_code > homepage; the maintainer's (David Grabiner) homepage disappeared.  I > think he's on LinkedIn.com in New York (and went to Brown University in > mathematics/computing) but it won't let

[Slackbuilds-users] Drop aqemu (GUI front end to qemu)

Although aqemu can be patched to build, numerous qemu CLI options have changed (deprecated, added, updated). Therefore, it is no longer viable. I don't have the time to fork and re-write, so I am dropping aqemu. I recommend Aqemu be dropped from 15.0. -Ed OpenPGP_signature Description:

Re: [Slackbuilds-users] Development Cycle Towards 15.0 Repository

On 4/16/21 3:27 AM, Willy Sudiarto Raharjo wrote: > Hi everyone > > As you may have heard that Patrick has declared -current into Beta > status, which means it's time for us to start working on our repository > which will lead to 15.0 repository in the future. It might take some > time until all

Re: [Slackbuilds-users] Warzone 2100 4.0.0 will have to wait.

On 4/10/21 1:15 PM, Dave Woodfall wrote: > Slackbuilds Users put forth the > proposition: >> Hi everybody, >> unfortunately 14.2 oldness striked again. >> This time it's SQLite that is too old for the brand new 4.0.0 version of >> Warzone >> 2100. > > Have you looked at the possibility of

[Slackbuilds-users] Gridcoin-Research EOL on Slackware-14.2

Hello, For 14.2 Gridcoin-Research-5.3.0.0 is the end unless openssl is upgraded. The next update 5.3.1.0 requires openssl-1.1.1j and 14.2 is currently at openssl-1.0.2u I'll post this on LQ as well for wider distribution. -Ed OpenPGP_signature Description: OpenPGP digital signature

Re: [Slackbuilds-users] mumble and murmur 1.3.4 update notes

On 4/3/21 6:58 PM, King Beowulf wrote: > In preparation for current, there's a slightly different buildscript > here: http://www.linuxgalaxy.org/files/sbo-testing/15.0/SBo-archives/ > since speechdispatcher etc is now included included. Here too, TTS is > not working in mumble, even

[Slackbuilds-users] mumble and murmur 1.3.4 update notes

Hello, Mumble and murmur 1.3.4 now requires protobuf3. This may cause an incompatibility for those who also need protobuf I was not able to test speech-dispatcher TTS integration. It "should" work, but I am unable to test in the qemu VM - no 14.2 running on hardware. I just upgraded my desktop

Re: [Slackbuilds-users] Updates - 20210403.1

On 4/2/21 7:24 PM, Willy Sudiarto Raharjo wrote: >> Whoops...just sent up mumble and murmur updates but I guess I was too slow! > > Hi Ed, > > can you rebase your branch against latest master branch? > > Thanks > I did last Saturday. I was a bit late pushing the updates Friday and so missed

Re: [Slackbuilds-users] Updates - 20210403.1

Whoops...just sent up mumble and murmur updates but I guess I was too slow! -Ed OpenPGP_signature Description: OpenPGP digital signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org

Re: [Slackbuilds-users] Updates - 20210313.1 SlackBuilds-users Digest, Vol 179, Issue 5

On 3/17/21 12:48 PM, B Watson wrote: > On 3/17/21, sborg63 via SlackBuilds-users > wrote: > >> Hi this version of refind (0.13.1) does not build on current. The >> latest (0.13.2) does... > > We don't actually support -current. Look in ponce's unofficial -current > repo to see if there's a

Re: [Slackbuilds-users] Add Autodetect to ffmpeg for Optional Dependencies

On 12/13/20 3:42 AM, Heinz Wiesinger wrote: > On Sunday, 25 October 2020 02:02:55 CET Jeremy Hansen wrote: >> Heinz, >> >> I'm a bit frustrated that the developers of ffmpeg don't have autodetect in >> their ./configure. Your script has definitely helped improve building >> ffmpeg, but even with

Re: [Slackbuilds-users] bluefish: version number mismatch

On 12/6/20 1:56 PM, Robby Workman wrote: > On Sun, 6 Dec 2020 18:36:57 -0300 > Eduardo Sanchez wrote: > ... >> Problem: there's a mismatch in bluefish version numbers. >> ... > > commit 5ff4dbba5481ce4816aba19b3c6517ed0fa81a8d (HEAD -> rworkman, > origin/rworkman) > Author: rworkman > Date:

[Slackbuilds-users] qemu feature freeze for 14.2

Hello, I'm going to freeze to qemu-4.1.1 for 14.2 since the gtk3, glib (and some other stuff) is too old to use newer versions. If PV bumps glib to 2.48, we can update to qemu-4.2.1. -Ed OpenPGP_signature Description: OpenPGP digital signature ___

Re: [Slackbuilds-users] [Slackbuilds-user] Teamviewer3 EULA bypass

On 10/27/20 10:16 PM, B Watson wrote: > On 10/21/20, King Beowulf wrote: >> >> Teamviewer3 will run the EULA acceptance no matter what - there doesn't >> seem to me a command line option to automatically accept. > > Is this network/TeamSpeak3? I don't see a Teamviewer3

Re: [Slackbuilds-users] [Slackbuilds-user] Teamviewer3 EULA bypass

On 10/24/20 1:13 AM, Matteo Bernardini wrote: > As for me I agree with your points and with your proposed solution. > > Il sab 24 ott 2020, 01:30 Dave Woodfall > ha scritto: > > > I must admit that I'm a bit uncomfortable with this, and I wouldn't > want

Re: [Slackbuilds-users] [Slackbuilds-user] Teamviewer3 EULA bypass

On 10/21/20 4:01 PM, Rich Shepard wrote: > On Wed, 21 Oct 2020, King Beowulf wrote: > >> Teamviewer3 will run the EULA acceptance no matter what - there doesn't >> seem to me a command line option to automatically accept. as a result, >> any >> automated SBo build to

[Slackbuilds-users] [Slackbuilds-user] Teamviewer3 EULA bypass

Hello Teamviewer3 will run the EULA acceptance no matter what - there doesn't seem to me a command line option to automatically accept. as a result, any automated SBo build tools get "stuck." As my bash-fu is rudimentary, anyone know a good bashism to allow for automatic acceptance? Thanks.

Re: [Slackbuilds-users] Updates - 20200912.1

On 9/12/20 9:58 AM, Willy Sudiarto Raharjo wrote: > system/wesnoth: Updated to version 1.14.13 wesnoth should be in category "games" which, according to my local updates branch (I haven't pulled updated master yet), it still sits. Thus, I wasn't me, I swear! -Ed signature.asc Description:

Re: [Slackbuilds-users] [Slackbuild-users] SDL2_gfx category

On 9/12/20 11:43 AM, B Watson wrote: > On 9/11/20, King Beowulf wrote: > >> SDL2_gfx is in development, is a library, and all other SDL2_* are in >> libraries (as is SDL-*). > > If it's up for vote, I vote for moving it to libraries. > >> Would i

[Slackbuilds-users] [Slackbuild-users] SDL2_gfx category

Hello, SDL2_gfx is in development, is a library, and all other SDL2_* are in libraries (as is SDL-*). Would it not be prudent to move SDL2_gfx to the development category? -Ed signature.asc Description: OpenPGP digital signature ___

Re: [Slackbuilds-users] SBo service migration #1 complete

On 7/2/20 6:06 AM, Robby Workman wrote: > TLDR: Migration #1 complete > > > We are investigating options for collecting > needed funds for hosting (about $1500 per year), but we'll be > in touch with our historically awesome community once we settle > on how we want to pursue that. Yes, we

[Slackbuilds-users] Multimedia > xvidcore (1.3.5) update

Hello xvidcore-1.3.7 builds and appears to work on both 14.2 and current. -Ed signature.asc Description: OpenPGP digital signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org

Re: [Slackbuilds-users] build errors with libquicktime

On 4/28/20 1:38 PM, Christopher L Duston via SlackBuilds-users wrote: > I am having some trouble building libquicktime, errors are below. I > naively believe this might be because I'm running multilib, but that > section of the script already includes what I would have added to try > and fix that:

Re: [Slackbuilds-users] build errors with libquicktime

On 4/28/20 1:38 PM, Christopher L Duston via SlackBuilds-users wrote: > I am having some trouble building libquicktime, errors are below. I > naively believe this might be because I'm running multilib, but that > section of the script already includes what I would have added to try > and fix that:

Re: [Slackbuilds-users] Development/jdk download URL points to a login page

On 4/23/20 7:13 PM, Dave Woodfall wrote: > On 2020-04-23 19:10, > King Beowulf put forth the proposition: >> Getting directed to a login page is HIGHLY annoying, as many you may agree. >> >> more "direct" downloads are here: >> >> https://www.ja

Re: [Slackbuilds-users] Development/jdk download URL points to a login page

On 4/23/20 7:13 PM, Dave Woodfall wrote: > On 2020-04-23 19:10, > King Beowulf put forth the proposition: >> Getting directed to a login page is HIGHLY annoying, as many you may agree. >> >> more "direct" downloads are here: >> >> https://www.ja

[Slackbuilds-users] Development/jdk download URL points to a login page

Getting directed to a login page is HIGHLY annoying, as many you may agree. more "direct" downloads are here: https://www.java.com/en/download/linux_manual.jsp Some of the links appear to be wget compatible (?). -Ed signature.asc Description: OpenPGP digital signature

Re: [Slackbuilds-users] Updates - 20200424.1

On 4/23/20 6:39 PM, Willy Sudiarto Raharjo wrote: > Hi all > > Forgive me to send the public update one day ahead of normal public > update on weekend. I was lost in time and was thinking that today is > Saturday. > Well...since I was in the process of doing updates this evening, on a THURSDAY!

Re: [Slackbuilds-users] intel-microcode

On 4/1/20 11:17 AM, Andrzej Telszewski wrote: > >> But I agree, cc:ing the maintainer seems like a good idea. >> > > Indeed. :-D > > I'll take a look as soon as I can. > I've noted that newer microcodes do not have support for older intel CPUs. For example, I'm still using

Re: [Slackbuilds-users] nvidia-driver-440.64 submitted

On 3/25/20 10:32 AM, Lenard Spencer wrote: > If nobody else wants it I'll take it. > > Approved. A bit earlier than had I planned, but it is definitely better to have a maintainer that can run the nvidia-driver on actual hardware. All hail the newly anointed nvidia high priest! -Ed

Re: [Slackbuilds-users] nvidia-driver-440.64 submitted

On 3/28/20 2:50 AM, Lyonel S wrote: > Hello > > Thank you very much for you hard work. > > I just noted a glitch in the last SBo update for nvidia-driver.info > : md5sum are those of 440.64 but the > filenames are still 440.59 (beware of a "59" in one of the md5sum >

Re: [Slackbuilds-users] nvidia-driver-440.64 submitted

On 3/25/20 10:32 AM, Lenard Spencer wrote: > If nobody else wants it I'll take it. > > > On Wed, Mar 25, 2020, 01:32 King Beowulf <mailto:kingbeow...@gmail.com>> wrote: > > Hello, everyone. > > I hope everyone is surviving the Viral Apocalypse

[Slackbuilds-users] nvidia-driver-440.64 submitted

Hello, everyone. I hope everyone is surviving the Viral Apocalypse in good health and spirits. I just posted updates to the Long Lived Branch nvidia-440.64 driver, compatible, hopefully, with both 14.2 and current. This will be my last 14.2 release, except for bug fixes, until 15.0. I will then

[Slackbuilds-users] qemu-4.1.0 is final SBo 14.2 version

Hello all, qemu-4.2.0 requires glib >= 2.48. Thus, qemu-4.1.0 is the final SBo version for Slackware-14.2. Also, for qemu-14.2, if you use '-display gtk' and have a nonfunctional monitor window, use '-display sdl' and invoke the monitor window with CTRL-ALT-2 (see docs). I haven't been able to

Re: [Slackbuilds-users] Packaging questions

On 3/20/20 2:36 PM, Didier Spaier wrote: > Le 20/03/2020 à 21:25, B Watson a écrit : >> On 3/20/20, Didier Spaier wrote: >>> Hi, >>> >>> I intend to upgrade espeakup, dynamically linked to espeak-ng not >>> espeak, as speech is then way better (tested by Slint users). >>> >>> Indeed I will

Re: [Slackbuilds-users] Updates - 20200215.1

On 2/15/20 10:25 AM, Dominik Drobek wrote: > Hi, > > I noticed some problems today: > --- > > network/TeamSpeak3: > MD5 sums for 32- and 64-bit downloads are swapped. > > Well...heck...I wonder how long THAT'S been going on? Fixed in my branch. Thanks Ed signature.asc Description:

[Slackbuilds-users] STATUS: nvidia-driver; nvidia-kernel and legacy

Hello All, I've marked nvidia-legacy304 as nvidia-legacy304-driver system ff162200b unmaintained nvidia-legacy304-kernel system 5d028b8f7 unmaintained I no longer have the hardware to test this driver series. Thus, it is up for grabs. Please be aware that Nvidia

Re: [Slackbuilds-users] Updates - 20200208.1

On 2/8/20 7:50 AM, Dominik Drobek wrote: > > development/bluefish: > https://www.bennewitz.com/bluefish/stable/source/bluefish-2.2.11.tar.bz2 > expected: dbe8aa956ca396830ee4f76598b1c63c > actual: 8c08aebcb7eaeccfebcaf467983733eb > Thanks. Fixed in my branch. -Ed signature.asc

Re: [Slackbuilds-users] Updates - 20200208.1

On 2/8/20 4:41 AM, Alexander Verbovetsky wrote: > Hello, > >> misc/vdpauinfo: updated for version 1.3 > > This gives: > - > configure: error: Package requirements (x11 vdpau >= 1.3) were not met: > > Requested 'vdpau >= 1.3' but version of VDPAU is 1.1.1 > - > whoops! my bad. seems

Re: [Slackbuilds-users] Qt5 Update to 5.12

On 1/25/20 7:47 AM, Dave Woodfall wrote: > To the maintainers of build scripts that depend on Qt5. > > I've been testing Qt5 LTS version 5.12, and everything seems to build > apart from the following applications: > Dave, Finally got around to checking out qt5-5.12.6 from your SBo

Re: [Slackbuilds-users] wine README fix; and wine-5.0 released

On 1/22/20 10:26 PM, Dave Woodfall wrote: > On 2020-01-22 18:35, > King Beowulf put forth the proposition: >... >> >> Also, wine-5.0 stable was just released: >> >> https://www.winehq.org/announce/5.0 >> >> Looks like the winhlp32/flex workarou

[Slackbuilds-users] wine README fix; and wine-5.0 released

FYI, In the wine README this NOTE does not make much sense: --- NOTE: you can increase buildtime passing some like that to the SlackBuild script: Perhaps this is better: NOTE: you can decrease build time by passing something like this to the SlackBuild script:

[Slackbuilds-users] phoronix-test-suite 9.2.1 can't find GD Library

Hello I rarely play with PHP and so am sometimes (often?) late to the party in addressing fixes. In case this was not yet discussed, PTS kicks a warning about missing the GD library. To fix, edit php.ini or better, create an entry in /etc/php.d: /etc/php.d/extensions.ini with the line:

Re: [Slackbuilds-users] Kdenlive roadmap and new maintainer

On 1/2/20 8:55 PM, King Beowulf wrote: > Hello. > > Copying old maintainer in case he has any input or desire to respond. > > Currently, SBo has kdenlive-0.9.10 which is a quite old release, and is > based in KDE4. Upstream has refactored for KDE5 as of version 15.x . >

[Slackbuilds-users] Kdenlive roadmap and new maintainer

Hello. Copying old maintainer in case he has any input or desire to respond. Currently, SBo has kdenlive-0.9.10 which is a quite old release, and is based in KDE4. Upstream has refactored for KDE5 as of version 15.x . Therefore, the latest and greatest version will need to wait for KDE5

Re: [Slackbuilds-users] Unmaintained builds - want any of these?

On 1/2/20 12:41 AM, Robby Workman wrote: > Hello all, > > TL;DR version: if you would like to see any of the scripts on the > following list stay around, please step up to maintain them. > > https://slackbuilds.org/DeadSBoBuilds > I'll take multimedia/kdenlive since I already have mlt (dep)

[Slackbuilds-users] ANNOUNCE: new nvidia buildscripts

Hello all, For those that use the SBo scripts for Nvidia, new buildscripts for 440.36 are now in pending. These scripts work on both 14.2 (stable) and 15.0 (current); for current you will need kernel-5.4.0 from /testing in order to successfully compile the kernel module interface. Hightlights:

[Slackbuilds-users] libgaminggear udev patch for non default GROUP

Hello Gerardo Since you have libgaminggear buildscript with the line GROUP=${GROUP:-uinput-users} resulting in some users assuming that they can use a different GROUP. I suggest applying the edit from the patch below to adjust 90-uiput.rules to allow for a different group. Thanks.

[Slackbuilds-users] Nvidia-legacy drivers EOL

Hello Everybody, Mats reminded me of a Nvidia post from 2018 for Nvidia driver end-of-life schedule: https://nvidia.custhelp.com/app/answers/detail/a_id/3142 In summary: nvidia-legacy304 304.137 EOL 2017 no further updates nvidia-legacy340 340.107 EOL 2019 in pending nvidia-legacy390

Re: [Slackbuilds-users] nvidia-legacy340-kernel needs to be patched for kernel 4.4.190

On 9/11/19 2:01 AM, Mats Bertil Tegner wrote: > Hello everyone, > Since Pat V has upgraded the kernel on -stable to 4.4.190 the > nvidia-legacy340 kernel modules needs the following patch to build on > kernels 4.4.168 and above. May I also suggest to update to nVidia driver > 340.107? > >

Re: [Slackbuilds-users] Google Earth Pro crashing

On 9/5/19 12:43 PM, Rich Shepard wrote: > I've the latest available GoogleEarth Pro (64-bit) from SBo installed, > along > with the 4.4.190 kernel. Sometimes it works and too often it shuts down > when > I try to zoom in to a location. Has anyone else experienced this? > > When this happend

Re: [Slackbuilds-users] Google Earth Pro crashing

On 9/6/19 12:12 PM, Rich Shepard wrote: > On Fri, 6 Sep 2019, Erich Ritz via SlackBuilds-users wrote: > >> No, that doesn't count. > > Erich, > > Didn't think so. > >> Run >> glxinfo | grep -i opengl > > $ glxinfo | grep -i opengl > OpenGL vendor string: VMware, Inc. > OpenGL renderer string:

Re: [Slackbuilds-users] Google Earth Pro crashing

On 9/6/19 6:38 AM, Willy Sudiarto Raharjo wrote: >> I thought that I had, but I don't. Looking on the SBo web site I find a >> PyOpenGL but not OpenGL. Am I looking in the wrong place? >> >> Also, X is not crashing, only the GE instance. > > OpenGL is not provided by SBo, but rather from your GPU

Re: [Slackbuilds-users] Qemu-4.1.0

On 8/23/19 9:03 PM, John Yost wrote: > The slackbuild fails for me with: >... > > contrib/vhost-user-gpu/vugbm.c:162:28: error: > 'GBM_BO_TRANSFER_READ_WRITE' undeclared (first use in this function) > GBM_BO_TRANSFER_READ_WRITE, , > ^

Re: [Slackbuilds-users] Qemu-4.1.0

On 8/24/19 7:14 AM, MyRequiem wrote: ... > > The 'virglrenderer' is to blame for everything (building quemu with > spice without any problems). If you build without spice, then we > can’t use the spice graphics either: > "spice graphics are not supported with this QEMU" Thanks for the testing.

Re: [Slackbuilds-users] nvidia-{driver;kernel}-430.40 upate posted

On 8/17/19 8:05 AM, Jheengut Pritvi wrote: > > > On Fri, 16 Aug 2019 at 21:22, King Beowulf <mailto:kingbeow...@gmail.com>> wrote: > > On 8/16/19 12:35 AM, Jheengut Pritvi wrote: > > Hi, > > > > Do you mean changes abou

Re: [Slackbuilds-users] nvidia-{driver;kernel}-430.40 upate posted

On 8/16/19 12:35 AM, Jheengut Pritvi wrote: > Hi, > > Do you mean changes about dropping support for non-GLVND libraries! > > https://devtalk.nvidia.com/default/topic/1060977 > > My NVIDIA GPU's might be a bit old too, GTX840m. > > Cheers > Pritvi > Yes, that was the announcement for the new

[Slackbuilds-users] nvidia-{driver;kernel}-430.40 upate posted

Hello all Nvidia is getting ready to drop non-GLVND libraries. This is my first pass to refactor the SBo scripts and get ready for 15.0 "real soon now." 430.40 mainly adds support for RTX 2080 Super cards and some minor bug fixes. These WILL NOT work on -current, at all, as of yet, since I

Re: [Slackbuilds-users] nvidia-{kernel,driver} roadmap

On 7/12/19 7:05 PM, flinchx via SlackBuilds-users wrote: > Which legacy drivers will be available for 15.0? Are all of them compiling > fine with -current kernels? Thanks. > That will depend on which kernel current will end up using and whether Nvidia provides updates for newer kernels and

[Slackbuilds-users] nvidia-{kernel,driver} roadmap

Hello all I'll be posting a refresh if the Nvidia 430.xx long term driver "soon." The last few updates since 430.14 have just added new GPU support. So let me know if anyone needs the latest (expensive) RTX 2xxx support. To get ready for 15.0 ("real soon now") I will be dropping the non-glvnd

Re: [Slackbuilds-users] mumble

On 5/10/19 5:56 AM, Didier Spaier wrote: > Hello, > > Making mumble accessible with speech needs to upgrade it to 1.3.0rc1, > that relies on qt5 and else needs avahi, at least as a build dependency, > and of course on speech-dispatcher and at least one TTS engine and > the Orca screen reader. >

Re: [Slackbuilds-users] ETA for next Slackware release?

On 5/4/19 1:40 PM, Ruben Schuller wrote: > Hi, > > is there any ETA for the next Slackware release? I'd like to update > Gajim, but this needs a newer gtk3 version (>=3.22). Everything else > seems to be present here :) > > Kind Regards > Ruben LET THE GAMES BEGIN! Place your bets!

[Slackbuilds-users] cherrytree moved download link

FYI The d/l link http://www.giuspen.com/software/cherrytree-0.38.6.tar.xz is 404 due to new version that is available. http://www.giuspen.com/software/cherrytree-0.38.8.tar.xz The old version is on github: https://github.com/giuspen/cherrytree/archive/0.38.6.tar.gz -Ed

Re: [Slackbuilds-users] Slackware and SlackBuilds.org cited in a scientific publication

On 3/15/19 8:44 AM, Petar Petrov wrote: > Dear All, > > I am happy to let you know Slackware and SlackBuilds.org were cited in > the most recent publication of our group. The paper is called > "Computational analysis of the evolutionarily conserved Missing In > Metastasis/Metastasis Suppressor 1

[Slackbuilds-users] OT: open access publication (WAS: Re: Slackware and SlackBuilds.org cited in a scientific publication)

On 3/16/19 7:29 AM, Alexander Verbovetsky wrote: >> This is true for those journals that charged for subscriptions to >> their dead tree versions. Others are strictly on-line and have no >> author charges. > > The journal "Scientific Reports" we are discussing is pure online. "Open > access"

Re: [Slackbuilds-users] qemu and capstone

On 2/25/19 5:19 AM, Matteo Bernardini wrote: > I think the build system detects the external capstone and then > wrongly tries to use the internal capstone headers in ./include/disas/ > instead of the system's ones: there's a related discussion on the qemu > mailing list > >

Re: [Slackbuilds-users] Can't build nvidia-kernel-410.78 with kernel 4.4.172

On 2/1/19 4:40 PM, Willy Sudiarto Raharjo wrote: >> Has anyone tried to build the NVIDIA proprietary kernel module for the >> most recent kernel (4.4.172) on Slackware-14.2? I'm getting the >> following error: > > The maintainer is aware of this issue and will soon fix it. >

[Slackbuilds-users] Suggestion: Change download order on script pages

Hello, Recently I've helped new Slackware users with SBo. I noticed that they have a hard time figuring out what to download in order to run the buildscript. Yes, there is a HOW-TO...don't go there... I suggest the following order on the script pages: - Download SlackBuild:

Re: [Slackbuilds-users] calibre does not start

On 12/2/18 1:41 PM, Petar Petrov wrote: > hi all, > > calibre does not start. It shows this in the terminal: > > Failed to run pipe worker with command: from calibre.utils.ipc.pool > import run_main, worker_main; run_main(worker_main) > Traceback (most recent call last): > File

Re: [Slackbuilds-users] Nvidia-390 now legacy; nvidia-410.xx is x86_64 only

On 11/9/18 2:31 PM, andrew wrote: > On Fri, Nov 09, 2018 at 02:09:53PM -0800, King Beowulf wrote: > >> Going forward, nvidia-{driver,kernel} will now be on the 4xx-series LLB >> branch which is x86_64 only. > > Does that mean that NVidia 410.73 is in /pending at the momen

[Slackbuilds-users] Nvidia-390 now legacy; nvidia-410.xx is x86_64 only

Hello everybody! nvidia-{driver,kernel} is now nvidia-legacy390-{driver,kernel} since Nvidia has dropped 32-bit support. Going forward, nvidia-{driver,kernel} will now be on the 4xx-series LLB branch which is x86_64 only. YES, COMPAT32 is still available as before, but you will need to be

[Slackbuilds-users] Nvidia drops 32-bit support after 390 series

Nvidia has released the 410 drivers for x86_64. 32-bit is deprecated - no driver after the 390 series. The 410 series x86_64 driver will continue to have 32-bit libraries for multilib. I do not plane at this time to support a legacy-390 script, For those with 32-bit systems running Nvidia GPU,

[Slackbuilds-users] compiling mlt-6.10 with qt5-5.7.1 SBo version

Hello! The details are here: https://www.linuxquestions.org/questions/slackware-14/can%27t-compile-mlt-6-10-0-on-stable-4175636167/#post5890571 If you need to compile mlt with QT5 support, QT5 must be compile with C++11, and mlt needs added flag to tell configure about c++11. Otherwise

[Slackbuilds-users] CONFIRMED: mlt with qt5 requires C++11 (was: Updates - 20180811.1)

All: If one uses Alien Bob's QT5-5.7.1 package, the mlt build defaults to QT4. To use QT5, you need to compile the SBo QT5 with c++11 and then compile mlt with c++11 This was a requirement since mlt-6.6.0 but I never noticed during testing - because I never built with QT5. This is a moot point

Re: [Slackbuilds-users] Updates - 20180811.1

On 08/12/2018 10:46 PM, David Woodfall wrote: > On Sunday 12 August 2018 16:08, > 414N <4...@slacky.it> put forth the proposition: >> Hi, >> >> I have problems upgrading mlt and rust. >> >> mlt seems to require a forced 'std-c++11' gcc flag (haven't tried it >> yet) to successfully compile now: >>

[Slackbuilds-users] Error in wxGTK3 buildscript

When creating the /usr/bin/wx-config symlink, code needs to be added in case the user compiles with STATIC=yes -8<-- --- /data/slackware/builds/libraries/wxGTK3/wxGTK3.SlackBuild 2018-03-24 17:19:40.661155000 -0700 +++ /tmp/medit-1-tmpdir-2d497bf8/tmpfile-0012018-08-12

Re: [Slackbuilds-users] Updates - 20180811.1

On 08/12/2018 07:08 AM, 414N wrote: > Hi, > > I have problems upgrading mlt and rust. > > mlt seems to require a forced 'std-c++11' gcc flag (haven't tried it > yet) to successfully compile now: > > In file included from /usr/include/qt5/QtCore/qglobal.h:83:0, > from

[Slackbuilds-users] Smath Studio source archive (ponce.cc)

The older archives are graciously hosted at ponce.cc and if he would be so kind as to grab the new Smath Studio "source": https://smath.info/file/BaH5L/SMathStudioDesktop.0_99_6671.Mono.tar.gz so that wget can get the file and we can avoid the asshattery of the smath web site download. Thanks

Re: [Slackbuilds-users] sage up for grabs UNMAINTAINED

On 08/09/2018 07:37 AM, Fellype do Nascimento wrote: ..snip... > Just a tip for anyone interested in take over maintenance for sage: > The AUR guys have made efforts to get the latest version (git) working > on Arch Linux (https://aur.archlinux.org/packages/sagemath-git/). > Well... there are up

[Slackbuilds-users] sage up for grabs UNMAINTAINED

All Anyone who wants to maintain SAGE can have it. I've tried to get a new version working for months. 1. Upstream does not want you to compile as root 2. All modules paths are hard coded during compile 3. relocatable package impossible? - I can't get it to work The devs want the end user to

Re: [Slackbuilds-users] qemu-2.12 README update: optional libseccomp

On 06/10/2018 10:36 AM, Andrzej Telszewski wrote: > On 10/06/18 19:30, B Watson wrote: >> On 6/10/18, Andrzej Telszewski  wrote: >> >>> 2018-06-10T11:27:22.810078Z qemu-kvm: -sandbox >>> on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny: >>> seccomp support is disabled >>

[Slackbuilds-users] qemu-2.12 README update: optional libseccomp

I don't use libvirt, but Andrzej reported that qemu needs to be compiled against libseccomp for newer (?) libvirt otherwise the qemu VM will not start. The diff from git master is: -8<-- diff --git a/system/qemu/README b/system/qemu/README index

Re: [Slackbuilds-users] Build failure: gnucash 2.6.19

On 03/31/2018 09:47 PM, David O'Shaughnessy wrote: > I'm having trouble building the latest gnucash 2.6.19. The last bit of > error output is: > Did you first remove/uninstall the older version? Seems gnucash compile can fail otherwise. This was mentioned in this list a year or so ago. -Ed

[Slackbuilds-users] nvidia-driver-390-42 symlink blunder

Admins Just noticed - that it came up just now and not earlier? - that the GLVND GL library is now libGL.so.1.7.0 and not libGL.so.1.0.0. This was not noted in Nvidia's README.txt so I didn't notice until I tried to compile wine-3.5. Weird that a few steam games didn't care... This patch to

  1   2   3   4   5   6   >