Re: [Slackbuilds-users] Jack-rack make failure
On 3/13/18, x80 wrote:
> Yes it's jack2.
> The Libs line in jack.pc looks like this:
>
> Libs: -L/usr/lib64 -ljack
>
> Seems it wasn't compiled with pthreads. I wonder if it's not a corrupt lib?
Eh, it probably isn't "corrupt", it's probably just that jack-rack
expects the .pc file for the jack library to always include -lpthread,
so doesn't include -lpthread explicitly.
You can use ldd on the jack library to find out whether or not it was
compiled with pthreads (I suspect it was), but whether or not jack2 was
built with pthreads, jack-rack has to be.
In jack-rack.SlackBuild, the configure command reads:
LDFLAGS="-lm -ldl" \
CFLAGS="$SLKCFLAGS" \
CXXFLAGS="$SLKCFLAGS" \
./configure \
--prefix=/usr \
--libdir=/usr/lib${LIBDIRSUFFIX} \
--sysconfdir=/etc \
--localstatedir=/var \
--mandir=/usr/man \
$LASH_OPT \
--disable-gnome \
--build=$ARCH-slackware-linux
Change the first line of that to read:
LDFLAGS="-lm -ldl -lpthread" \
...don't forget the trailing backslash!
Let me know whether or not that fixes the problem... and even if it
fixes this specific issue, there may be others.
If that fixes it, I'll probably just patch jack2's .pc file to include
-lpthread, since I suspect lots of other jack apps will have the same
problem when built with jack2.
Basically, jack2 on SBo is almost completely untested. Someone
submitted it a few years back and never updated it, and none of the
READMEs for any of the JACK-related stuff mentions it. They all list
jack-audio-connection-kit (AKA jack1) as a dependency in their .info
files, so that's what people end up using.
You're the first user I've met who has even tried jack2, so I'm very
interested to know what you've done with it. What SBo JACK stuff have
you installed, and how well do they work, that sort of thing.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Jack-rack make failure
On 03/13/2018 11:21 AM, B Watson wrote:
On 3/13/18, x80 wrote:
ld returns an odd error "jack_rack-midi.o: undefined reference to symbol
'pthread_create@@GLIBC_2.2.5'
/lib64/libpthread.so.0: error adding symbols: DSO missing from command
line"
This is on a fully updated 14.2 box. I see no errors in the configure
log and all lib paths are ok.
I'm not quite sure how to get past this one.
Hm. The 2nd error message usually means "-lpthread" is missing,
during linking.
It builds fine on my fully-updated 64-bit 14.2 box...
Check the file /usr/lib64/pkgconfig/jack.pc and see if has a line
like this:
Libs: -L${libdir} -ljack -lpthread
Also, it's just occurred to me... are you using jack-audio-connection-kit
(AKA jack-0.125.0), or jack2 (AKA jack2-1.9.10)? I just recently took
over maintenance of jack2, but haven't done anything with it yet.
Yes it's jack2.
The Libs line in jack.pc looks like this:
Libs: -L/usr/lib64 -ljack
Seems it wasn't compiled with pthreads. I wonder if it's not a corrupt lib?
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Jack-rack make failure
On 3/13/18, x80 wrote:
> ld returns an odd error "jack_rack-midi.o: undefined reference to symbol
> 'pthread_create@@GLIBC_2.2.5'
>
> /lib64/libpthread.so.0: error adding symbols: DSO missing from command
> line"
>
> This is on a fully updated 14.2 box. I see no errors in the configure
> log and all lib paths are ok.
>
> I'm not quite sure how to get past this one.
Hm. The 2nd error message usually means "-lpthread" is missing,
during linking.
It builds fine on my fully-updated 64-bit 14.2 box...
Check the file /usr/lib64/pkgconfig/jack.pc and see if has a line
like this:
Libs: -L${libdir} -ljack -lpthread
Also, it's just occurred to me... are you using jack-audio-connection-kit
(AKA jack-0.125.0), or jack2 (AKA jack2-1.9.10)? I just recently took
over maintenance of jack2, but haven't done anything with it yet.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] ffmpeg does not compile with opencv 3.4.1
On Tue, 13 Mar 2018 16:53:37 +0100 Frédéric Falsetti wrote: > On Tue, 13 Mar 2018 23:33:53 +1000 > Christoph Willing wrote: > > > > > > An interesting problem - opencv is optional for ffmpeg and ffmpeg is > > optional for opencv i.e. an optional circular dependency. > > > > to compile ffmpeg against I have to : to compile ffmpeg against CHROMAPRINT ;/ > 1) build ffmpeg without CHROMAPRINT, > 2) rebuild CHROMAPRINT, > 3) compile ffmpeg with CHROMAPRINT perhaps this can help for opencv ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] Jack-rack make failure
ld returns an odd error "jack_rack-midi.o: undefined reference to symbol 'pthread_create@@GLIBC_2.2.5' /lib64/libpthread.so.0: error adding symbols: DSO missing from command line" This is on a fully updated 14.2 box. I see no errors in the configure log and all lib paths are ok. I'm not quite sure how to get past this one. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] ffmpeg does not compile with opencv 3.4.1
On Tue, 13 Mar 2018 23:33:53 +1000 Christoph Willing wrote: > > An interesting problem - opencv is optional for ffmpeg and ffmpeg is > optional for opencv i.e. an optional circular dependency. > to compile ffmpeg against I have to : 1) build ffmpeg without CHROMAPRINT, 2) rebuild CHROMAPRINT, 3) compile ffmpeg with CHROMAPRINT ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] MasterPDFEditor on 32 bit
On Tue, 13 Mar 2018, Willy Sudiarto Raharjo wrote: Since there are some people who still use 32 bit, i'm going to keep providing Qt4 version in the repository. Thanks, Willy. Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] ffmpeg does not compile with opencv 3.4.1
> On 13/03/18 20:04, Ythogtha wrote: > > Hi everybody ! > > > > it seems that ffmpeg can't compile with opencv version 3.4.1, here is > > the message, it happens straight after the un-tar-ing of the source : > > > > > > [...] > > ffmpeg-3.4/COPYING.LGPLv2.1 > > ffmpeg-3.4/README.md > > ffmpeg-3.4/CONTRIBUTING.md > > ERROR: opencv not found > > > > If you think configure made a mistake, make sure you are using the latest > > version from Git. If the latest version fails, report the problem to the > > ffmpeg-u...@ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net. > > Include the log file "ffbuild/config.log" produced by configure as this will > > help solve the problem. > > > > > > Opencv 3.4.1 does seem to work on its own. > > ffmpeg compiles fine with OpenCV 3.4.0. > > ffmpeg does not work when compiled against OpenCV 3.4.0, if OpenCV is > > updated to 3.4.1 - but that was to be expected, ffmpeg is pretty touchy with > > specific versions of the libraries it uses. > > > > The error is the same if I try with ffmpeg 3.4.2 (the latest). > > > > I don't have a solution, and I just wanted to point that out, since I don't > > really use OpenCV, so I can compile my ffmpeg without it (or with the > > previous version). I just like my ffmpeg bloated with options ^^ > > > > An interesting problem - opencv is optional for ffmpeg and ffmpeg is > optional for opencv i.e. an optional circular dependency. > > chris Yep, that's pretty funny :) Though in the past it wasn't very difficult to handle. Opencv can be built against ffmpeg even if ffmpeg doesn't run because you just removed the opencv against which it was built, and rebuilding ffmpeg with the new opencv after that doesn't break opencv. (You follow me ? :)) So well usually, when one of them is updated, you just had to rebuild it, install it, then rebuild the other one. I haven't tested going at it from scratch on a clean 14.2 VM, but the error doesn't suggest there is a side effect of this circular dependency. Something changed in OpenCV 3.4.1, and ffmpeg can't find it anymore. And the git diff on opencv's slackbuild does not help me there either, it was a pretty simple version bump. -- Arnaud ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] MasterPDFEditor on 32 bit
>> Yes, I am, on two hosts: desktop and Dell Latitude 2100 with an Atom >> processor. Currently running MasterPDFEditor-4.3.82 with Qt4. > Hi Willy, > I also still using a 32 bits machine and MasterPDFEditor 4 + Qt4. But I > don't care if it is kept in version 4.3.82. That is, I don't need it to > be updated. > So, it is OK for me if you move to Qt5 version and for 64 bit only. Hi Fellype Upstream support both Qt4 and Qt5, but Qt5 is only for 64 bit architecture, so if i moved to Qt5, the Qt4 will no longer be available in the repository. That's why i need to ask whether there are users who still use 32 bit machines. Since there are some people who still use 32 bit, i'm going to keep providing Qt4 version in the repository. I will make a note in the README for those who wanted to use Qt5 version. -- Willy Sudiarto Raharjo signature.asc Description: OpenPGP digital signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] MasterPDFEditor on 32 bit
On 03/13/2018 09:45 AM, Rich Shepard wrote: On Tue, 13 Mar 2018, Willy Sudiarto Raharjo wrote: So, i need to ask the audience in this mailing list whether you are using MasterPDFEditor and still using 32 bit machine? Willy, Yes, I am, on two hosts: desktop and Dell Latitude 2100 with an Atom processor. Currently running MasterPDFEditor-4.3.82 with Qt4. Hi Willy, I also still using a 32 bits machine and MasterPDFEditor 4 + Qt4. But I don't care if it is kept in version 4.3.82. That is, I don't need it to be updated. So, it is OK for me if you move to Qt5 version and for 64 bit only. Fellype ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] ffmpeg does not compile with opencv 3.4.1
On 13/03/18 20:04, Ythogtha wrote: > Hi everybody ! > > it seems that ffmpeg can't compile with opencv version 3.4.1, here is > the message, it happens straight after the un-tar-ing of the source : > > > [...] > ffmpeg-3.4/COPYING.LGPLv2.1 > ffmpeg-3.4/README.md > ffmpeg-3.4/CONTRIBUTING.md > ERROR: opencv not found > > If you think configure made a mistake, make sure you are using the latest > version from Git. If the latest version fails, report the problem to the > ffmpeg-u...@ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net. > Include the log file "ffbuild/config.log" produced by configure as this will > help > solve the problem. > > > Opencv 3.4.1 does seem to work on its own. > ffmpeg compiles fine with OpenCV 3.4.0. > ffmpeg does not work when compiled against OpenCV 3.4.0, if OpenCV is updated > to > 3.4.1 - but that was to be expected, ffmpeg is pretty touchy with specific > versions of the libraries it uses. > > The error is the same if I try with ffmpeg 3.4.2 (the latest). > > I don't have a solution, and I just wanted to point that out, since I don't > really use OpenCV, so I can compile my ffmpeg without it (or with the previous > version). I just like my ffmpeg bloated with options ^^ > An interesting problem - opencv is optional for ffmpeg and ffmpeg is optional for opencv i.e. an optional circular dependency. chris ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] python-xlib
2018-03-13 6:23 GMT+01:00 or...@fredslev.dk : > Hi, > > I am maintaining the python3-xlib build script which when I first > submitted it was distinct from python-xlib which was already in the > repo. However at some point this changed and python3 support was added > to the main python-xlib upstream. Consequently my requirement for it in > pyewmh and caffeine-ng is now python-xlib rather than python3-xlib > which has not received any updates upstream since. > > The problem is that the python-xlib at SBo is rather out of date, lacks > python3 support and when I contacted the maintainer with the e-mail in > the .info file I received a mailer-daemon reply saying the address no > longer exists. > > If anyone knows how to contact the maintainer that would be helpful. If > needed I can take over python-xlib which should replace python3-xlib. IMHO it's perfectly fine for you to take over python-xlib as its maintainer is completely inactive since eight years. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] python-xlib
Hi, I am maintaining the python3-xlib build script which when I first submitted it was distinct from python-xlib which was already in the repo. However at some point this changed and python3 support was added to the main python-xlib upstream. Consequently my requirement for it in pyewmh and caffeine-ng is now python-xlib rather than python3-xlib which has not received any updates upstream since. The problem is that the python-xlib at SBo is rather out of date, lacks python3 support and when I contacted the maintainer with the e-mail in the .info file I received a mailer-daemon reply saying the address no longer exists. If anyone knows how to contact the maintainer that would be helpful. If needed I can take over python-xlib which should replace python3-xlib. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] MasterPDFEditor on 32 bit
On Tue, 13 Mar 2018, Willy Sudiarto Raharjo wrote: So, i need to ask the audience in this mailing list whether you are using MasterPDFEditor and still using 32 bit machine? Willy, Yes, I am, on two hosts: desktop and Dell Latitude 2100 with an Atom processor. Currently running MasterPDFEditor-4.3.82 with Qt4. Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Retroshare do not work Slackware.
2018-03-13 12:15 GMT+01:00 Christoph Willing : > On 13/03/18 20:33, Ozan Türkyılmaz wrote: >> I havent been able to compile retroshare but problem is not with libupnp >> right now. >> > > Yes, that patch is just a partial fix. > > The API for libupnp has changed in the new 1.8.x versions (SBo has > libupnp-1.8.3 at the moment). Retroshare devs will need to update their > code to utilize the new libupnp API. > > Without any indication of how long that might take, maybe we need a > libupnp-legacy SlackBuild with version capped at the latest in the 1.6.x > series so that retroshare can continue to be built. Otherwise we sit > tight with a SlackBuild that won't build until upstream updates their code. yes, I can confirm the issue seems still related to the newer libupnp https://pastebin.com/raw/Yk07FRuA ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Retroshare do not work Slackware.
On 13/03/18 20:33, Ozan Türkyılmaz wrote: > > 2018-03-13 15:28 GMT+05:00 Matteo Bernardini > mailto:matteo.bernard...@gmail.com>>: > > 2018-03-13 10:51 GMT+01:00 Ozan Türkyılmaz > mailto:ozan.turkyil...@gmail.com>>: > > I have updated libupnp script. I am still on vacation, though. > > I am attaching the file for testing. It looks OK from here but I need > better > > testing with other programs. > > thanks, I pushed it in my branch. > > > I havent been able to compile retroshare but problem is not with libupnp > right now. > Yes, that patch is just a partial fix. The API for libupnp has changed in the new 1.8.x versions (SBo has libupnp-1.8.3 at the moment). Retroshare devs will need to update their code to utilize the new libupnp API. Without any indication of how long that might take, maybe we need a libupnp-legacy SlackBuild with version capped at the latest in the 1.6.x series so that retroshare can continue to be built. Otherwise we sit tight with a SlackBuild that won't build until upstream updates their code. chris ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Retroshare do not work Slackware.
2018-03-13 15:28 GMT+05:00 Matteo Bernardini : > 2018-03-13 10:51 GMT+01:00 Ozan Türkyılmaz : > > I have updated libupnp script. I am still on vacation, though. > > I am attaching the file for testing. It looks OK from here but I need > better > > testing with other programs. > > thanks, I pushed it in my branch. > I havent been able to compile retroshare but problem is not with libupnp right now. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Retroshare do not work Slackware.
2018-03-13 10:51 GMT+01:00 Ozan Türkyılmaz : > I have updated libupnp script. I am still on vacation, though. > I am attaching the file for testing. It looks OK from here but I need better > testing with other programs. thanks, I pushed it in my branch. Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] ffmpeg does not compile with opencv 3.4.1
Hi everybody ! it seems that ffmpeg can't compile with opencv version 3.4.1, here is the message, it happens straight after the un-tar-ing of the source : [...] ffmpeg-3.4/COPYING.LGPLv2.1 ffmpeg-3.4/README.md ffmpeg-3.4/CONTRIBUTING.md ERROR: opencv not found If you think configure made a mistake, make sure you are using the latest version from Git. If the latest version fails, report the problem to the ffmpeg-u...@ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net. Include the log file "ffbuild/config.log" produced by configure as this will help solve the problem. Opencv 3.4.1 does seem to work on its own. ffmpeg compiles fine with OpenCV 3.4.0. ffmpeg does not work when compiled against OpenCV 3.4.0, if OpenCV is updated to 3.4.1 - but that was to be expected, ffmpeg is pretty touchy with specific versions of the libraries it uses. The error is the same if I try with ffmpeg 3.4.2 (the latest). I don't have a solution, and I just wanted to point that out, since I don't really use OpenCV, so I can compile my ffmpeg without it (or with the previous version). I just like my ffmpeg bloated with options ^^ -- Arnaud ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Retroshare do not work Slackware.
I have updated libupnp script. I am still on vacation, though. I am attaching the file for testing. It looks OK from here but I need better testing with other programs. 2018-02-28 22:59 GMT+05:00 Matteo Bernardini : > 2018-02-28 17:40 GMT+01:00 radio radio : > > I opened a post in linuxquestions.org slackware forum, about "Retroshare > > 6.0.3" slackbuild. > > > > https://www.linuxquestions.org/questions/showthread.php? > p=5825342#post5825342 > > > > Ponce suspect an issue with the newer " libupnp ". > > I'll try to clarify a little: retroshare.SlackBuild lacks a "set -e" > line so a package is created also if build breaks and this might have > lead into the belief that compiling had been succesful. > > the error is this: > > g++ -c -pipe -Wno-deprecated -Wno-deprecated-declarations -Wno-cpp > -std=c++0x -Wall -D_FILE_OFFSET_BITS=64 -O2 -pthread -fPIC -Wall -W > -DRS_ENABLE_GXS -DENABLE_WEBUI -DRS_NO_WARN_DEPRECATED > -DRS_NO_WARN_CPP -DRS_GXS_TRANS -DRS_USE_BITDHT -DPATCHED_LIBUPNP > -DPLUGIN_DIR="\"/usr/lib64/retroshare/extensions6\"" > -DDATA_DIR="\"/usr/share/retroshare\"" -DRS_USE_LIBUPNP > -DSQLITE_HAS_CODEC -DGXS_ENABLE_SYNC_MSGS > -I/usr/lib64/qt/mkspecs/linux-g++ -I. -I. -I../../libbitdht/src > -I../../openpgpsdk/src -I/usr/include/upnp -o > temp/linux-g++/obj/rsinit.o rsserver/rsinit.cc > In file included from ./upnp/UPnPBase.h:35:0, > from ./upnp/upnphandler_linux.h:13, > from rsserver/rsinit.cc:805: > /usr/include/upnp/upnpdebug.h:40:24: fatal error: ThreadPool.h: No > such file or directory > compilation terminated. > Makefile.libretroshare:5411: recipe for target > 'temp/linux-g++/obj/rsinit.o' failed > make[1]: *** [temp/linux-g++/obj/rsinit.o] Error 1 > make[1]: Leaving directory '/tmp/SBo/RetroShare-0.6.3/libretroshare/src' > Makefile:90: recipe for target > 'sub-libretroshare-src-libretroshare-pro-make_default' failed > make: *** [sub-libretroshare-src-libretroshare-pro-make_default] Error 2 > > Matteo > ___ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -- Ozan, BSc, BEng libupnp.tar.gz Description: application/gzip ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] MasterPDFEditor on 32 bit
Hi all, I got a report that MasterPDFeditor has an OCR issue when using the Qt4 version and upstream recommended to use Qt5 version. Unfortunately, the Qt5 version is only available for 64 bit architecture, leaving users who are still using 32 bit at lost. So, i need to ask the audience in this mailing list whether you are using MasterPDFEditor and still using 32 bit machine? I will wait until the end of this month. If there's no one matches the above criteria, i'm happy to move to Qt5 version and only for 64 bit architecture. Thanks -- Willy Sudiarto Raharjo signature.asc Description: OpenPGP digital signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
