Re: [Slackbuilds-users] Season's Greetings
On Fri, Dec 23, 2011 at 11:10 AM, Matteo Bernardini matteo.bernard...@gmail.com wrote: Thanks Chris, best wishes and happy holidays to you and to all the other slackers too :) I'll second that. I much appreciate the quality of the work by Robby and the rest of the Slackbuilds crew. /Don Allen ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Why Might a SBo Application Look in /usr/local?
The output of On Mon, Aug 29, 2011 at 7:28 PM, Rich Shepard rshep...@appl-ecosys.com wrote: I've been running R-2.13.0 and decided to upgrade to -2.13.1. I downloaded the new scripts and source, built and upgraded the package. When I try to invoke it I see: [rshepard@salmo ~]$ R -bash: /usr/local/bin/R: No such file or directory I've no idea where to look to see where the shell is getting the wrong location. I've been using the SlackBuild packages for several versions now and haven't before come across this issue. It's a bit difficult to help with so few details about your system and what you did to build the new R. I can tell you that I did this same upgrade today on a Slackware 13.37 x86_64 system, downloading and building the package from slackbuilds.org with sbopkg, and R 2.13.1 works fine, and the R executable is in /usr/bin, where you'd expect it to be. Any ideas- To try to help you, I'd be interested in knowing the architecture and version of the Slackware system you are running and seeing the result of ls -l /var/adm/packages/R* cat /var/adm/packages/R-2.13.1* hash and echo $PATH from the instance of bash giving you the error would be useful. /Don Allen Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Why Might a SBo Application Look in /usr/local? [SOLVED]
On Mon, Aug 29, 2011 at 10:34 PM, Rich Shepard rshep...@appl-ecosys.com wrote: On Mon, 29 Aug 2011, Rich Shepard wrote: I've no idea where to look to see where the shell is getting the wrong location. I've been using the SlackBuild packages for several versions now and haven't before come across this issue. Well, I came up with the right idea and looked in ~/.bash_profile. For some reason I aliased R to look in /usr/local/bin. Since I installed R from the SBo packages over the past few years I've no idea why I did this nor do I know why R ran (from /usr/bin) until today. I am suitably embarrassed. Well, you should be; no one else has ever done anything that dumb before, certainly not me :-) (Believe me, I really am kidding!) For years, I've talked about writing a book about the various strange and wonderful ways we screw ourselves with computers (not a particularly original idea). If you can stand a war story, 35+ years ago, I worked on and later ran the Tenex project at BBN. BBN was one of the key companies that built the ARPAnet (the predecessor of the Internet) and Tenex, an operating system developed by us for the DEC PDP-10, was the most common host OS on the network. One of the guys in the Tenex group wrote a backup and archiving system. The first time he ran it in production, it archived its own executable and source files. Archived files could only be read by the archiving program. Me: So should be no problem -- you have a copy of all that stuff on DECTape, right? Him: Um, no. /Don Mea culpa! Rich ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Fwd: yajl source link broken
On Sun, Aug 28, 2011 at 5:18 PM, Niels Horn niels.h...@gmail.com wrote: On Sun, Aug 28, 2011 at 4:09 PM, Donald Allen donaldcal...@gmail.com wrote: This is still broken. -- Forwarded message -- From: Donald Allen donaldcal...@gmail.com Date: Wed, Aug 3, 2011 at 8:41 AM Subject: yajl source link broken To: slackbuilds-users@slackbuilds.org, easu...@gmail.com Following the link to the source file on the page http://slackbuilds.org/repository/13.37/libraries/yajl/ results in a 404 Not Found error. /Don Allen Indeed it is and I could not find a working direct link to the tarball. It can be found on github though. Yes -- I found it there, too, and was able to get the package built. I'm copying the maintainer - maybe he knows a better link to the tarball. Why can't the link on http://slackbuilds.org/repository/13.37/libraries/yajl/ simply be changed to point to http://github.com/lloyd/yajl/tarball/2.0.1/lloyd-yajl-2.0.1-0-gf4b2b1a.tar.gz ?? That's the file I downloaded. Works fine. /Don -- Niels Horn ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Installing gnucash 2.4.5----
2011/8/8 Ozan Türkyılmaz ozan.turkyil...@gmail.com remove old version and re try the build. It's a known problem without a real solution. Yes, that's certainly good advice. I think this is inherent in the extremely complex method used to build gnucash from source. I ran into similar problems trying to build one of the 2.4 series from source with 2.2.9 installed. The advice I got from Derek Atkins, one of the gnucash gurus, was to either remove the old version or configure with a --prefix != /usr/local. The former would seem to apply in this case. 2011/8/8 jamesgilmour jh-gilm...@bigpond.com: Hi, I'm trying to install gnucash but it doesn't get past the bottom of this page. I had no problem with gnucash 2.2.9 and then tried the upgrade. I followed the dependency compilation instructions without apparent difficulty and elected to include 'webkit' and libdb, also ok. Here is the last screen of the 'gnucash'build process before it stops. Can you help? after-statement -O2 -march=i486 -mtune=i686 -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wno-unused -o gnucash gnucash-bin.o ../../src/libqof/qof/libgnc-qof.la ../../src/core-utils/ libgnc-core-utils.la ../../src/engine/libgncmod-engine.la ../../src/gnome/ libgnc-gnome.la ../../src/gnome-utils/libgncmod-gnome-utils.la../../src/app-utils/ libgncmod-app-utils.la ../../src/gnc-module/libgnc-module.la -pthread -lguile -lltdl -lgmp -lcrypt -lm -lltdl -pthread -Wl,--export-dynamic -lgobject-2.0 -lgthread-2.0 -lgmodule-2.0 -lrt -lglib-2.0 -pthread -lgnomeui-2 -lSM -lICE -lbonoboui-2 -lgnomevfs-2 -lgnomecanvas-2 -lgnome-2 -lpopt -lbonobo-2 -lbonobo-activation -lORBit-2 -lart_lgpl_2 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lm -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgconf-2 -lgmodule-2.0 -lgobject-2.0 -lgthread-2.0 -lrt -lglib-2.0 -pthread -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lm -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0 -lm -lm libtool: link: gcc -Wdeclaration-after-statement -O2 -march=i486 -mtune=i686 -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wno-unused -o .libs/gnucash gnucash-bin.o -pthread -pthread -Wl,--export-dynamic -pthread -pthread ../../src/libqof/qof/.libs/libgnc-qof.so ../../src/core-utils/.libs/libgnc-core-utils.so ../../src/engine/.libs/libgncmod-engine.so ../../src/gnome/.libs/libgnc-gnome.so ../../src/gnome-utils/.libs/libgncmod-gnome-utils.so ../../src/app-utils/.libs/libgncmod-app-utils.so ../../src/gnc-module/.libs/libgnc-module.so /usr/lib/libguile.so /usr/lib/libgmp.so -lcrypt /usr/lib/libltdl.so /usr/lib/libgnomeui-2.so /usr/lib/libSM.so /usr/lib/libICE.so /usr/lib/libbonoboui-2.so /usr/lib/libgnomevfs-2.so /usr/lib/libgnomecanvas-2.so /usr/lib/libgnome-2.so /usr/lib/libpopt.so /usr/lib/libbonobo-2.so /usr/lib/libbonobo-activation.so /usr/lib/libORBit-2.so /usr/lib/libart_lgpl_2.so /usr/lib/libgconf-2.so /usr/lib/libgtk-x11-2.0.so /usr/lib/libgdk-x11-2.0.so /usr/lib/ libatk-1.0.so /usr/lib/libgio-2.0.so /usr/lib/libpangoft2-1.0.so /usr/lib/ libpangocairo-1.0.so /usr/lib/libgdk_pixbuf-2.0.so /usr/lib/libcairo.so /usr/lib/libpango-1.0.so /usr/lib/libfreetype.so /usr/lib/libfontconfig.so /usr/lib/libgobject-2.0.so /usr/lib/libgmodule-2.0.so /usr/lib/ libgthread-2.0.so -lrt /usr/lib/libglib-2.0.so -lm -pthread -Wl,-rpath -Wl,/usr/lib/gnucash /usr/lib/gnucash/libgncmod-report-gnome.so: undefined reference to `gnc_html_export' /usr/lib/gnucash/libgncmod-report-gnome.so: undefined reference to `gnc_html_copy' /usr/lib/gnucash/libgncmod-report-gnome.so: undefined reference to `gnc_html_new' collect2: ld returned 1 exit status make[4]: *** [gnucash] Error 1 make[4]: Leaving directory `/tmp/SBo/gnucash-2.4.5/src/bin' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/tmp/SBo/gnucash-2.4.5/src/bin' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/SBo/gnucash-2.4.5/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/SBo/gnucash-2.4.5' make: *** [all] Error 2 gnucash: Would you like to continue processing the rest of the build queue or would you like to abort? If this failed package is a dependency of another package in the queue then it may not make sense to continue. (Y)es to continue, (N)o to abort, (R)etry the build?: README gnucash-2.4.5.tar.bz2 gnucash.SlackBuild.build gnucash.info gnucash.info.sbopkg doinst.sh gnucash.SlackBuild gnucash.SlackBuild.sbopkg gnucash.info.build slack-desc James Gilmour. ___ SlackBuilds-users mailing list
Re: [Slackbuilds-users] tangogps slackbuild doesn't work
On Fri, Aug 5, 2011 at 3:16 PM, Donald Allen donaldcal...@gmail.com wrote: I have reached the point where I've had enough problems with slackbuilds and I'm tired of the pain of slackware package management (or lack thereof) that I'm giving debian a try (I found that I could install it without a desktop environment, exactly what I wanted; I just run dwm) and I have to do it on the netbook for various reasons. So I no longer have slackware installed on that machine, so I won't be able to do further testing in a car. Well, this was an interesting exercise, leaving me sheepishly coming back to Slackware after a couple of days of experimentation. Having been reminded, at my advanced age, that convenience exacts a price. Debian's wireless stuff is flakey on my netbook, a showstopper. It worked, and then it didn't; config files unchanged and correct, dhcpcd installed properly. Plus, Debian's packages tend to be old, so for certain applications where I care about having the most recent version, such as gnucash, I'd be in the business of building from source, without the help of slackbuild scripts and dependency information (building gnucash 2.4.7 was not fun). Then there's the awful Sys V init setup and the general feeling that Debian is too complicated. Speaking of complicated, I then I spent some time trying Gentoo, which I used for a couple of years in the past. Installation is a multi-hour proposition, especially on a slow machine, and I found that X did not work correctly on the machine where I tried it. It's also an ongoing maintenance headache, which is the reason I gave up on it when it was my primary distribution. Once I started having X problems, that was that. I didn't even bother with Arch, which I tried a few years ago. Their rolling release idea means that because they are continuously releasing new stuff, they can't possibly test the whole system every time something new appears. And occasionally, something new will appear that will blow up your system if you install it, at which point you get to boot from a CD and learn how to use chroot. I have been running FreeBSD 8.2 on three of my machines and it's a solid system. But yesterday, I tried to upgrade gnucash to 2.4.7, that version having appeared in /usr/ports after an update. One of the standard port management tools (portmaster) failed miserably in managing the upgrade, leaving me with a gnucash executable that segfaulted immediately. Various attempts to rescue the situation failed. Getting to gnucash 2.4.7 with slackware is easy. I have a home-brew make-based tool that I use to wget slackbuilds, source files, info files, etc. from slackbuilds.org and whatever it points to. Dependencies are expressed in the makefile. I had built 2.4.5 using this (that's the current version available from slackbuilds.org), so all the dependencies were installed, and therefore upgrading to 2.4.7 was a simple matter of downloading the source tarball and running the slackbuild script manually. When I realized how easy this was, compared to what I had been through with debian and freebsd, it dawned on me that I was heading in exactly the wrong direction, away from from slackware. So I'm back, chastened. The moral of the story is that while things in the Slackware world aren't perfect, for my minimalist tastes (I don't run a desktop environment, just dwm with some of the standard patches, one of which I contributed), it's better for me than anything else I can find. Live and learn. /Don ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] tangogps slackbuild doesn't work
On Sun, Aug 7, 2011 at 11:29 AM, Pierre Cazenave pwcazen...@gmail.comwrote: On 07/08/2011 15:01, Donald Allen wrote: snip I have a home-brew make-based tool that I use to wget slackbuilds, source files, info files, etc. from slackbuilds.org /snip I'm sure you're aware, but just in case, there's sbopkg ( http://www.sbopkg.org) which takes care of a lot of the mundane fetching, checking md5sums, checking signatures etc. for building packages from SlackBuilds.org. I honestly can't imagine building package for Slackware without it since it's queuing functionality means you can figure out the build order in a text file and then give it that queue file, set it running and forget about it until it's finished. Yes, I'm aware of it and have it. I'm looking at how to use it, probably in conjunction with my make-based tool. But thanks for the helpful comments. /Don Pierre __**_ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.**org SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/**mailman/listinfo/slackbuilds-**usershttp://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/**pipermail/slackbuilds-users/http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] tangogps slackbuild doesn't work
On Sun, Jul 31, 2011 at 8:57 PM, Pedro Mendes pe...@gepasi.org wrote: Too bad, I had already submitted. I think I can pull it out and will wait for further information from you. We can add a patch to the slackbuild, this is done in other packages when it cannot be avoided. Hi -- Sorry it has taken me awhile to get back. We had a family emergency that took me away for a couple of days. I have not tested tangogps with the changes I installed as thoroughly as I would have liked, but the testing I did resulted in no segfaults, which were pretty easy to provoke before I installed the changes below. I have reached the point where I've had enough problems with slackbuilds and I'm tired of the pain of slackware package management (or lack thereof) that I'm giving debian a try (I found that I could install it without a desktop environment, exactly what I wanted; I just run dwm) and I have to do it on the netbook for various reasons. So I no longer have slackware installed on that machine, so I won't be able to do further testing in a car. But I think it's safe to install the changes below. Here are the diffs: diff src/tile_management.c /home/dca/Software/tangogps-0.99.4/src/tile_management.c 249a250 curl_easy_setopt(curl, CURLOPT_NOSIGNAL, 1); diff src/util.c /home/dca/Software/tangogps-0.99.4/src/util.c 111a112 curl_easy_setopt(curl_handle, CURLOPT_NOSIGNAL, 1); 168a170 curl_easy_setopt(curl_handle, CURLOPT_NOSIGNAL, 1); The left-hand files (in src/) as the originals; the right-hand files are the ones I modified, adding the calls to curl_easy_setopt. I hope this helps. /Don thanks pedro On Mon, Aug 1, 2011 at 12:34 AM, Donald Allen donaldcal...@gmail.com wrote: Pedro -- I should have copied you on this, because you need to be aware of this discussion. We don't have an answer yet, but B Watson may have identified the problem. I'll be sure to let you know how my testing turns out. Right now, even tangogps 0.99.4 (built from source) is unreliable on slackware 13.37. Hopefully, this will fix the problem. More when I know more. /Don -- Forwarded message -- From: B Watson yalh...@gmail.com Date: Sun, Jul 31, 2011 at 5:39 PM Subject: Re: [Slackbuilds-users] tangogps slackbuild doesn't work To: SlackBuilds.org Users List slackbuilds-users@slackbuilds.org On 7/31/11, Donald Allen donaldcal...@gmail.com wrote: If you google for 'libcurl error 6 segfault', you get hits involving all sorts of applications that apparently use curl. Try it. This looks to me like a bug in libcurl. So unless you are feeling better, stay in bed. This appears to be someone else's problem. This sounds really similar to the issue with uget that I dealt with a while back. If it's the same issue, it can be fixed by adding curl_easy_setopt(curl, CURLOPT_NOSIGNAL, 1); somewhere in the bit of code that sets the other curl options. The issue is actually documented in the curl API docs: if curl is built with threads but without c-ares support (like the one shipped with slackware), the default DNS timeout handling (which uses signals, presumably SIGALRM) is unsafe. Adding to the confusion is that (at least in the case of uget) this didn't actually hurt anything on slackware 13.1, but it does on 13.37. I dunno if you can consider this a bug in curl or not: it's documented, but if I were a curl dev, I'd want to fix it (by having CURLOPT_NOSIGNAL default to 1 when curl is built without c-ares). Application code can set CURLOPT_NOSIGNAL, but I don't know how hard it is for a configure script or makefile to detect whether curl was built with c-ares, and I don't know what happens if you set CURLOPT_NOSIGNAL when using a libcurl with c-ares support. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ -- Pedro, o guardador de enzimas e computadores ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] yajl source link broken
Following the link to the source file on the page http://slackbuilds.org/repository/13.37/libraries/yajl/ results in a 404 Not Found error. /Don Allen ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] tangogps slackbuild doesn't work
The tangogps slackbuild does not work with gpsd (on a 64-bit 13.37 Slackware system running on a Toshiba NB305 netbook), also installed from slackbuilds.org. I am using a GlobalSat BU-353 gps receiver. After starting gpsd, I run xgps to test, and I get a 3D fix and everything looks normal. But when I start tangogps, while the chatter it produces indicates that it has successfully hooked up with gpsd, there is no indication of that in the map display. Current position is not displayed correctly, and various bits of data that would normally come from the gps are blank or displayed as zero, nor does it display your track and heading. So I decided to download the source from the tangogps website and built and installed it (configure complained that libsoup was not installed, which I fixed; it is not mentioned as a dependency on http://slackbuilds.org/repository/13.37/misc/tangogps/; this may have to do with the version issues I will discuss below). This version works properly (though it does occasionally seg-fault). I noticed that the slackbuilds.org package uses tangogps version 0.99.2 (which was released on 12/3/2009) and the version I built from source, the current version, is 0.99.4 (released 6/25/2010). I note that the release notes for 0.99.4 include support for the new gpsd protocol. So perhaps the failure of the slackbuild is due to tangogps trying to talk old protocol to gspd, which no longer supports it? (I am running gpsd v2.96, as supplied by the slackbuild) It appears that gpsd switched to the new protocol with version 2.90 and from what I can tell from their website, the old protocol is no longer supported. So I'm guessing that any version of tangogps before 0.99.4 is not going to work with any gpsd version = 2.90. (As I've indicated, I'm speculating about the cause of the breakage -- I've written to the tangogps author about this, and if I learn anything further I will share with this list.) As for the libsoup issue, perhaps that dependency was introduced after 0.99.2? In any case, I would recommend updating this slackbuild and the associated web-page to use the current version, 0.99.4, which I think will solve the problem. libsoup needs to be added to list of dependencies. /Don Allen ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] tangogps slackbuild doesn't work
2011/7/31 Ozan Türkyılmaz ozan.turkyil...@gmail.com 2011/7/31 Donald Allen donaldcal...@gmail.com: http://slackbuilds.org/repository/13.37/misc/tangogps/; this may have to do with the version issues I will discuss below). This version works properly (though it does occasionally seg-fault). What's the output when it SEGFAULTs. 'Segmentation fault'. No core file, due to the 'core file size' resource limit defaulting to zero. Debugging myself looks hopeless (21 comment lines in almost 8300 lines of C) and I'm not going to put any effort into this until I hear from the the author, who has been unresponsive thus far (just a couple of days). /Don -- Ozan, BSc, BEng ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] tangogps slackbuild doesn't work
2011/7/31 Ozan Türkyılmaz ozan.turkyil...@gmail.com 2011/7/31 Donald Allen donaldcal...@gmail.com: 2011/7/31 Ozan Türkyılmaz ozan.turkyil...@gmail.com 2011/7/31 Donald Allen donaldcal...@gmail.com: http://slackbuilds.org/repository/13.37/misc/tangogps/; this may have to do with the version issues I will discuss below). This version works properly (though it does occasionally seg-fault). What's the output when it SEGFAULTs. 'Segmentation fault'. No core file, due to the 'core file size' resource limit defaulting to zero. Debugging myself looks hopeless (21 comment lines in almost 8300 lines of C) and I'm not going to put any effort into this until I hear from the the author, who has been unresponsive thus far (just a couple of days). How about /var/log/messages? Jul 30 15:41:32 olympia kernel: [ 486.225116] tangogps[2468]: segfault at 811 ip 7f143b3c2a02 sp 7f142e7f9d58 error 6 in libcurl.so.4.2.0[7f143b398000+56000] -- Ozan, BSc, BEng ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] tangogps slackbuild doesn't work
2011/7/31 Ozan Türkyılmaz ozan.turkyil...@gmail.com 2011/7/31 Donald Allen donaldcal...@gmail.com: Jul 30 15:41:32 olympia kernel: [ 486.225116] tangogps[2468]: segfault at 811 ip 7f143b3c2a02 sp 7f142e7f9d58 error 6 in libcurl.so.4.2.0[7f143b398000+56000] Hmm libcurl. But as you said before, without debug symbols, It's really hard tyo see where this goes. Exactly. I proposed to the author that I compile with -g and run under gdb, but, as I said, unless and until I hear from him, I'm not going to spend any time on this, since the code is inscrutable, and there's a lot of it. /Don -- Ozan, BSc, BEng ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] tangogps slackbuild doesn't work
On Sun, Jul 31, 2011 at 12:53 PM, David Spencer baildon.resea...@googlemail.com wrote: There is a newer / older version of gpsd in the pending queue (not approved yet). I'm copying the maintainer to see if he has any idea... The gpsd maintainer is lying in bed feeling very very ill and reading email with the brightness set to minimum :-( gpsd-2.96 has an API change (the function set_raw_hook was removed) which means viking-1.1 doesn't build. That's why I recently submitted the downgraded gpsd-2.95. Both tangogps-0.99-2 and tangogps-0.99.4 build ok with both gpsd-2.96 and gpsd-2.95. I don't know of any specific changes in gpsd-2.96 that will cause a runtime segfault in tangogps. Because it's difficult to get a satellite fix in bed, actual testing of tangogps-0.99.4 will require the gpsd maintainer to get out of bed :-/ digression I've only just noticed there is a problem with SBo's viking.info at the moment. Although the SlackBuild is for version 1.1, the .info file is still for the old version 0.9.94 /digression FWIW, libcurl's error 6 is Couldn't resolve host. The given remote host was not resolved. which doesn't sound like the sort of thing that would provoke a segfault. The gpsd maintainer is now feeling a bit better, having spent the last 20 minutes thinking about tangogps, viking and gpsd instead of migraine. Maybe later tonight the gpsd maintainer will get out of bed :-) If you google for 'libcurl error 6 segfault', you get hits involving all sorts of applications that apparently use curl. Try it. This looks to me like a bug in libcurl. So unless you are feeling better, stay in bed. This appears to be someone else's problem. /Don Probably more later -D. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] tangogps slackbuild doesn't work
On Sun, Jul 31, 2011 at 5:39 PM, B Watson yalh...@gmail.com wrote: On 7/31/11, Donald Allen donaldcal...@gmail.com wrote: If you google for 'libcurl error 6 segfault', you get hits involving all sorts of applications that apparently use curl. Try it. This looks to me like a bug in libcurl. So unless you are feeling better, stay in bed. This appears to be someone else's problem. This sounds really similar to the issue with uget that I dealt with a while back. If it's the same issue, it can be fixed by adding curl_easy_setopt(curl, CURLOPT_NOSIGNAL, 1); somewhere in the bit of code that sets the other curl options. The issue is actually documented in the curl API docs: if curl is built with threads but without c-ares support (like the one shipped with slackware), the default DNS timeout handling (which uses signals, presumably SIGALRM) is unsafe. Adding to the confusion is that (at least in the case of uget) this didn't actually hurt anything on slackware 13.1, but it does on 13.37. I dunno if you can consider this a bug in curl or not: it's documented, but if I were a curl dev, I'd want to fix it (by having CURLOPT_NOSIGNAL default to 1 when curl is built without c-ares). Application code can set CURLOPT_NOSIGNAL, but I don't know how hard it is for a configure script or makefile to detect whether curl was built with c-ares, and I don't know what happens if you set CURLOPT_NOSIGNAL when using a libcurl with c-ares support. Thanks for this -- I'll try it. It sounds like the curl people may not have chosen the most conservative default, but you concede to not completely understanding the trade-offs and I know a good deal less than you do about this, so I will leave this as pure speculation. I will report back to the list when either 1. I've run tangogps for a good deal longer than the mean-time-between-segfaults without a crash, or 2. I continue to see segfaults even with the suggested fix installed.. /Don ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] lapack
On Fri, May 20, 2011 at 10:51 AM, markus reichelt m...@mareichelt.com wrote: * Donald Allen donaldcal...@gmail.com wrote: For me, it's no longer a problem; I got it built. My concern is just that others might trip over this and waste time figuring out what I already did. Folks using SBo should know about env variables and how to adapt them. I'm sorry, but I couldn't disagree more strongly. The page on slackbuilds.org says the version is 3.3.0. The info file says the version is 3.3.0. The source is for 3.3.1, except there is no way to find that out other than to run the slackbuild script, have it fail, and then dig through the error messages to find out what went wrong. That's not normal use of environment variables, that's debugging. I already did that and am suggesting passing that information on to others. Maybe put a note on the page alerting people that the version has changed, the slackbuild awaits updating, Too much of a hassle. And quite frankly, users should expect such minor inconveniences - life, it's out there. Changing a web page is too much hassle to save some people some time and aggravation? Also, there's several scripts on SBo that don't get updated just because of a new version. A bummer for sbopkg users but hardly a show-stopper for the rest of us. You and I have different standards, apparently. -- left blank, right bald ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] lapack
On Fri, May 20, 2011 at 11:19 AM, markus reichelt m...@mareichelt.com wrote: * Donald Allen donaldcal...@gmail.com wrote: You and I have different standards, apparently. You are not listening. Ah, what you say must be right, because YOU said it, so if I disagree, I must not be listening. Got it. -- left blank, right bald ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] lapack
On Wed, May 18, 2011 at 11:42 PM, Donald Allen donaldcal...@gmail.comwrote: The 13.37 version of lapack does not build without a little help. The Slackbuild script defaults VERSION to 3.3.0, but the sources are 3.3.1. Changing the default or passing in VERSION works. The default should be updated. The lapack.info file pointed to on the http://slackbuilds.org/repository/13.37/libraries/lapack/ page also has the version at 3.3.0. /Don /Don Allen ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] chicken slackbuild issue
On Sat, Apr 23, 2011 at 9:54 AM, Donald Allen donaldcal...@gmail.comwrote: On a 64-bit Slackware 13.1 system, the Chicken (Scheme compiler) slackbuild fails if you specify ARCH=x86_64: chicken-4.6.0/LICENSE chicken-4.6.0/srfi-1.c make -f ./Makefile.linux CONFIG= all make[1]: Entering directory `/tmp/SBo/chicken-4.6.0' make[1]: *** No rule to make target `apply-hack.x86_64.S', needed by `apply-hack.x86_64.o'. Stop. make[1]: Leaving directory `/tmp/SBo/chicken-4.6.0' make: *** [all] Error 2 If you don't specify ARCH, it fails differently: gcc -shared -Wl,-soname,libchicken.so \ -o libchicken.so library.o eval.o data-structures.o ports.o files.o extras.o lolevel.o utils.o tcp.o srfi-1.o srfi-4.o srfi-13.o srfi-14.o srfi-18.o srfi-69.o posixunix.o regex.o scheduler.o profiler.o stub.o expand.o chicken-syntax.o chicken-ffi-syntax.o runtime.o apply-hack.x86-64.o -lm -ldl gcc -L. -shared -Wl,-R. setup-download.o -o setup-download.so \ -lchicken \ -lm -ldl ./libchicken.so: file not recognized: File format not recognized collect2: ld returned 1 exit status make[1]: *** [setup-download.so] Error 1 make[1]: *** Waiting for unfinished jobs ln -sf libchicken.so libchicken.so.5 make[1]: Leaving directory `/tmp/SBo/chicken-4.6.0' make: *** [all] Error 2 I think the second error was caused by my use of parallel make (specifying -j 4 to make). The chicken README file mentions that parallel make is not supported and I get the same error when I simply download the 4.6.0 source tarball and attempt to build it with -j 4. Without -j 4, the slackbuild works -- builds the slackware package successfully. /Don /Don Allen ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] [uzbl-dev] Problem downloading gzipped tar files
On Mon, Apr 11, 2011 at 2:15 AM, Robby Workman rwork...@slackbuilds.org wrote: On Thu, 7 Apr 2011 08:56:13 -0400 Donald Allen donaldcal...@gmail.com wrote: On Thu, Apr 7, 2011 at 8:38 AM, Donald Allen donaldcal...@gmail.com wrote: Robby -- Below is a response from one of the uzbl developers to a message I sent them, which unfortunately is truncated in his response. The issue is that with the uzbl browser, which is built on top of webkitgtk, when I download slackbuild tar files, they get gunzipped, though the locally stored file is still named foo.tar.gz. As mentioned below, I do not see this behavior when downloading .tar.gz files from other sites, nor do I see it with Firefox. His message explains all this, including asserting that slackbuilds.org sending Content-Encoding: gzip is incorrect. If you agree that this is an error (in my experience, the uzbl guys know what they are talking about when it comes to browser matters, web protocols, etc.), please put fixing this on your to-do list. I just did a bit of reading on this and it's pretty clear that he's right. Content-Encoding: gzip asks the browser to gunzip what the server sends. Whatever Firefox is doing is a heuristic, a hack to avoid uncompressing .tar.gz files even if the server says Content-Encoding: gzip incorrectly. That sounds right; the problem is that RemoveEncoding (which I'm pretty sure works as expected on httpd-2.x) doesn't seem to do what I think it should on apache-1.x. Until/unless we either figure out the required magic, or upgrade to a later release of Slackware (which probably won't happen unless we get new hardware), wget or some other browser is my recommended solution :-) The automated (make-based) thing I use to obtain packages from slackbuilds.org uses wget, so except in oddball cases (such as flash-plugin, which generates a slackware package with a version number different than that in the .info file) where I need to do things manually, it's not an issue. And now that I know what's going on, I use firefox instead of uzbl in situations like that, so it's not an operational problem for me. I just wanted to get it on your list because others might trip over it. Too bad apache isn't cooperating -- thanks for trying. /Don -RW ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Fwd: [uzbl-dev] Problem downloading gzipped tar files
Robby -- Below is a response from one of the uzbl developers to a message I sent them, which unfortunately is truncated in his response. The issue is that with the uzbl browser, which is built on top of webkitgtk, when I download slackbuild tar files, they get gunzipped, though the locally stored file is still named foo.tar.gz. As mentioned below, I do not see this behavior when downloading .tar.gz files from other sites, nor do I see it with Firefox. His message explains all this, including asserting that slackbuilds.org sending Content-Encoding: gzip is incorrect. If you agree that this is an error (in my experience, the uzbl guys know what they are talking about when it comes to browser matters, web protocols, etc.), please put fixing this on your to-do list. By the way, my earlier message about the flash-plugin slackbuild may have been a result of this problem. I don't remember if I tried downloading it with firefox. If I didn't, the file may actually have been ok and was delivered uncompressed to me because of the above issue. Thanks -- /Don -- Forwarded message -- From: Dan Winship d...@gnome.org Date: Thu, Apr 7, 2011 at 8:17 AM Subject: Re: [uzbl-dev] Problem downloading gzipped tar files To: Donald Allen donaldcal...@gmail.com Cc: uzbl-...@lists.uzbl.org On 04/06/2011 11:24 PM, Donald Allen wrote: uzbl, what I end up with is the tar file gunzip-ed, but it is still named foo.tar.gz. For example, go to http://slackbuilds.org/repository/13.1/academic/ess/ and click the 'ess.tar.gz' link. Unless there's something about my setup that's causing this, you will get an ess.tar.gz file that is actually an uncompressed tar file. Doing the same with Firefox 3.6.15 results in a gzipped tar file, as one would expect. I do not see this behavior when downloading gzipped tar files from some other sites, e.g., gnucash.org. It's because slackbuilds is sending Content-Encoding: gzip, which is wrong. Other browsers work around this, but WebKitGTK doesn't. There's a bug at https://bugzilla.gnome.org/show_bug.cgi?id=613361. We never got around to figuring out exactly how Firefox is special-casing this, so it never got fixed. -- Dan ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] [uzbl-dev] Problem downloading gzipped tar files
On Thu, Apr 7, 2011 at 8:38 AM, Donald Allen donaldcal...@gmail.com wrote: Robby -- Below is a response from one of the uzbl developers to a message I sent them, which unfortunately is truncated in his response. The issue is that with the uzbl browser, which is built on top of webkitgtk, when I download slackbuild tar files, they get gunzipped, though the locally stored file is still named foo.tar.gz. As mentioned below, I do not see this behavior when downloading .tar.gz files from other sites, nor do I see it with Firefox. His message explains all this, including asserting that slackbuilds.org sending Content-Encoding: gzip is incorrect. If you agree that this is an error (in my experience, the uzbl guys know what they are talking about when it comes to browser matters, web protocols, etc.), please put fixing this on your to-do list. I just did a bit of reading on this and it's pretty clear that he's right. Content-Encoding: gzip asks the browser to gunzip what the server sends. Whatever Firefox is doing is a heuristic, a hack to avoid uncompressing .tar.gz files even if the server says Content-Encoding: gzip incorrectly. /Don By the way, my earlier message about the flash-plugin slackbuild may have been a result of this problem. I don't remember if I tried downloading it with firefox. If I didn't, the file may actually have been ok and was delivered uncompressed to me because of the above issue. Thanks -- /Don -- Forwarded message -- From: Dan Winship d...@gnome.org Date: Thu, Apr 7, 2011 at 8:17 AM Subject: Re: [uzbl-dev] Problem downloading gzipped tar files To: Donald Allen donaldcal...@gmail.com Cc: uzbl-...@lists.uzbl.org On 04/06/2011 11:24 PM, Donald Allen wrote: uzbl, what I end up with is the tar file gunzip-ed, but it is still named foo.tar.gz. For example, go to http://slackbuilds.org/repository/13.1/academic/ess/ and click the 'ess.tar.gz' link. Unless there's something about my setup that's causing this, you will get an ess.tar.gz file that is actually an uncompressed tar file. Doing the same with Firefox 3.6.15 results in a gzipped tar file, as one would expect. I do not see this behavior when downloading gzipped tar files from some other sites, e.g., gnucash.org. It's because slackbuilds is sending Content-Encoding: gzip, which is wrong. Other browsers work around this, but WebKitGTK doesn't. There's a bug at https://bugzilla.gnome.org/show_bug.cgi?id=613361. We never got around to figuring out exactly how Firefox is special-casing this, so it never got fixed. -- Dan ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] flash-plugin
On Tue, Apr 5, 2011 at 2:49 PM, Robby Workman rwork...@slackbuilds.org wrote: On Tue, 5 Apr 2011 14:10:35 -0400 Donald Allen donaldcal...@gmail.com wrote: The flash-player-plugin SlackBuild (flash-player-plugin.tar.gz) referenced http://slackbuilds.org/repository/13.1/multimedia/flash-player-plugin/ is not gzipped. It's an ordinary tar file. This confuses some automated stuff I've built to deal with packages from slackbuilds.org that expects .tar.gz files to be what they say they are -- gzipped. Fixed; thanks! Thank you! /Don -RW ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Fwd: Dangling postgresql source pointer
I sent this message 11 days ago and it is still broken. The fix is simple -- point to 9.0.3 instead. /Don -- Forwarded message -- From: Donald Allen donaldcal...@gmail.com Date: Tue, Feb 8, 2011 at 9:59 PM Subject: Dangling postgresql source pointer To: slackbuilds-users@slackbuilds.org The link ftp://ftp.postgresql.org/pub/source/v9.0.1/postgresql-9.0.1.tar.bz2 to the source on the page http://slackbuilds.org/repository/13.1/system/postgresql/ does not work; the v9.0.1 directory no longer exists. v9.0.2 and v9.0.3 are available. /Don ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Fwd: Dangling postgresql source pointer
On Sat, Feb 19, 2011 at 7:54 PM, Erik Hanson e...@slackbuilds.org wrote: On Sat, 19 Feb 2011 19:17:02 -0500 Donald Allen donaldcal...@gmail.com wrote: I sent this message 11 days ago and it is still broken. The fix is simple -- point to 9.0.3 instead. This needs to go to the maintainer of postgresql, who may not be subscribed to this list. It did (take a careful look at the addressees on the message I sent). /Don -- Erik Hanson ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] Dangling postgresql source pointer
The link ftp://ftp.postgresql.org/pub/source/v9.0.1/postgresql-9.0.1.tar.bz2 to the source on the page http://slackbuilds.org/repository/13.1/system/postgresql/ does not work; the v9.0.1 directory no longer exists. v9.0.2 and v9.0.3 are available. /Don ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Spam - is it only me?
On Tue, Dec 7, 2010 at 9:31 AM, Niels Horn niels.h...@gmail.com wrote: On Tue, Dec 7, 2010 at 12:25 PM, Martin Pagnan mpag...@acanac.net wrote: Hi, I have suddenly been flooded with spam. I am trying to understand how my email address got into the hands of nasties. I recently joined Slackbuilds Users List and I notice that the content is searchable through Google together with the email addresses in the format someone at mail site. It is by now a pretty old and easy trick to parse at as @ and to try the address. Is anyone else at the site experiencing problems? Not more than normal... My e-mail address has been on the internet for years, through newsgroups, forums, etc. But my spam-filter works well. I get the occasional false-positive, but I can live with that. Same with me. Spam arrival rate is normal, mostly taken care of by gmail's excellent spam filter. /Don Niels ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] libtasn1 source link broken
The link to the source on http://slackbuilds.org/repository/13.1/libraries/libtasn1/ is broken. /Don ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] make -j -l
Thanks for the responses. I guess you've convinced me that setting -j as a function of cores/hyperthreading is probably a bad idea. Question: the gnu make man page and the info writeup are not clear on the effect of MAKEFLAGS. There's a lot of chatter about sub-makes, but it is not clear that env MAKEFLAGS='-j 4' make is equivalent to make -j 4 If anyone knows definitively, plz let me know. Otherwise, I'll get the answer by experiment. But if the above equivalence holds, then I agree that there's no need to modify the slackbuild scripts. /Don ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] fotoxx problem
On the page http://slackbuilds.org/repository/13.0/graphics/fotoxx/ if you click the fotoxx-9.9.tar.gz link, you get a Page not found error. /Don ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] fotoxx problem
On Fri, May 21, 2010 at 10:08 PM, Niels Horn niels.h...@gmail.com wrote: On Fri, May 21, 2010 at 10:48 PM, Donald Allen donaldcal...@gmail.com wrote: On the page http://slackbuilds.org/repository/13.0/graphics/fotoxx/ if you click the fotoxx-9.9.tar.gz link, you get a Page not found error. /Don Newer versions were released since the SlackBuild was approved. Have you tried using the script with the newer tarballs from here: http://kornelix.squarespace.com/downloads/ Thanks for the pointer, but my main purpose in sending the message was to alert Robby et al that the source link on this page was dangling. /Don Niels ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] Call for testing: Latest Opera snapshot
Have any of you run opera and top at the same time? I tried opera for the umpteenth time a few months ago on a Linux system and found that while it worked, the processor utilization was extremely high, much higher than Firefox. I've also seen complaints about this on opera user groups. So, for the umpteen+1th time, I gave up on it. I'd be curious to know if any of you are seeing the same thing. /Don On Sat, May 15, 2010 at 7:46 AM, vvoody wxj.g...@gmail.com wrote: From: Šime Ramov s...@ramov.com Subject: [Slackbuilds-users] Call for testing: Latest Opera snapshot Date: Thu, 13 May 2010 19:56:20 +0200 (CEST) Message-ID: 1273773380.87676...@192.168.2.228 Hello - I created a new Opera SlackBuild targeting latest snapshot, 6336 as of this writing. It is available here: http://dl.slackfu.com/opera.tar.gz Unix installer script is completely rewritten. More about latest packaging: http://my.opera.com/ruario/blog/new-opera-unix-packages-arrive-deb-rpm-tar Prefix is hard coded (in addition to other annoyances like no DESTDIR support) and they actually recommend using the .deb archive and re- packaging that until they release a more capable install script. Please note Opera no longer depends on QT -- they use they own native libraries. Comments welcome. Thanks! Works, thank you Ramov. Opera's installation script gets even weirder. Now we have to generate the slack package by depending on the deb pkg. LOL... Hope for a enhanced script. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] postgresql again
On Thu, Apr 15, 2010 at 4:03 AM, Tim Dickson dickson@googlemail.com wrote: just a thought.. It should be easy enough to just echo instructions using doinst.sh That way the end user/installer gets to know how to get things working, without the package interfering and doing it for them. Either that, or (or as well) include the instructions in an rc. file as comments, in the same way that the mysql package already does. And (as I mentioned in my original post) in the README.SBo, together with the instructions for how to initialize the database. I agree with Robby that this isn't quite a bug -- it's more a documentation issue. And despite what you've said above, if it turns out to be inconvenient or undesirable to have the package check for the presence of the postgres group and user at install time, anyone installing postgresql is going to have to consult the README.SBo to know how to edit rc.local/rc.local_shutdown get the server running/stopped and the database initialized. So having the information about the needed group and user there seems like the natural place to put it. I'd be happy with just that. If the package can do the check at install time, so much the better. /Don Tim On 15/04/2010 03:22, Robby Workman wrote: On Wed, 14 Apr 2010 12:03:30 -0400 Donald Allen donaldcal...@gmail.com wrote: When you run the postgresql.SlackBuild, you get reminded that you need to create a postgres group and user and you are given the commands to do so. You comply, the postgres package builds, you install it, and then get it running following the instructions in README.SBo. Some time later, you use the resulting package to try to install postgresql on another system. It installs, but when you attempt to get it running, you can't, because you need to create the postgres group and user, which you find out when you attempt to do su postgres -c initdb -D /var/lib/pgsql/data Except the error you get doesn't tell you how to fix the problem. So maybe you remember enough from when you originally built the package to dig through the postgresql.SlackBuild and figure it out. My point is this: the reminders to create the group and user should not occur at build time, they should occur at install time (or maybe both, if they are really needed at build time). At the very least, the README.SBo ought to tell you that the group- and user-creation is needed and how to do it. It seems to be assuming that this has already been done, which it may not be, if you are installing a package that you created on a different system six months ago. This issue is similar in nature to the issue I had with the gnucash package: the package is not self-contained and should be. This one is a WONTFIX, if only because I don't see it as a bug. That's not to say that I don't see your point -- I do -- but there's not any obvious way that we can do this better without adding some badness. By badness, I mean: we are not going to have postinstall scripts create users and/or groups on the system. In essence, this is one of those things that's going to have to be documented by the system admin in a local ChangeLog or some such and then consulted when doing new installs. -RW ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] postgresql again
When you run the postgresql.SlackBuild, you get reminded that you need to create a postgres group and user and you are given the commands to do so. You comply, the postgres package builds, you install it, and then get it running following the instructions in README.SBo. Some time later, you use the resulting package to try to install postgresql on another system. It installs, but when you attempt to get it running, you can't, because you need to create the postgres group and user, which you find out when you attempt to do su postgres -c initdb -D /var/lib/pgsql/data Except the error you get doesn't tell you how to fix the problem. So maybe you remember enough from when you originally built the package to dig through the postgresql.SlackBuild and figure it out. My point is this: the reminders to create the group and user should not occur at build time, they should occur at install time (or maybe both, if they are really needed at build time). At the very least, the README.SBo ought to tell you that the group- and user-creation is needed and how to do it. It seems to be assuming that this has already been done, which it may not be, if you are installing a package that you created on a different system six months ago. This issue is similar in nature to the issue I had with the gnucash package: the package is not self-contained and should be. /Don ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] A nit
Here's another little nit that will be easy to fix. On the gnucash page: http://slackbuilds.org/repository/13.0/business/gnucash/ there is a list of dependencies. I copied that list to paste into a for lib in slib libofx . do little script to build and install the lib done This didn't work quite right because the name of the ORBit2 library incorrectly has a lower-case 'b' on that page -- 'ORbit2'. So the build of that library fails, as does the subsequent build of GConf, because ORBit2 isn't installed. I'd suggest fixing that little typo, so someone else doesn't get bitten by this. Thanks -- /Don ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] postgresql
On Mon, Apr 5, 2010 at 2:04 PM, Ben Mendis dragonwis...@gmail.com wrote: On Mon, Apr 5, 2010 at 8:39 AM, Adis Nezirovic a...@linux.org.ba wrote: Preserving mode for existing scripts is OK, but I personally think that the default for new scripts should be 0644. Admin should run chmod +x manually. I don't disagree that the Admin is ultimately responsible for making sure it's correctly configured, but I don't agree that the admin should be forced to do everything manually (especially things that could be so trivially scripted) as a general policy. IMHO, sane automation of the configuration (such as adopting the same permissions as the version being replaced) are preferable. This is especially useful in systems where the updates might be happening unattended. (Of course, in the absence of automation 0644 is a better default than 0755.) Exactly. Slavish worship of doing things manually *where there's no clear benefit to doing so* doesn't make sense and this is one of those cases. Slackware seems devoted to finding a sensible balance in this area, automating where it's useful (by making things easier or less error-prone for the sys-admin) but not overdoing it (having things happen behind the scenes that a sys-admin might want to know about and/or control). I'm in the process of installing Slackware on four systems for my personal use, and so far it feels like the decisions relating to this issue have been very well thought out (which doesn't surprise me, given the years of experience Patrick Volkerding brings to the Linux-distribution problem). /Don ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] gnucash 2.2.9 dependencies
If you load just the dependencies (from a combination of slackbuilds.org and a gnomeslackbuild.org mirror) specified on the gnucash 2.2.9 page, namely slib libofx ORbit2 GConf libtasn1 gnome-keyring gnome-mime-data libbonobo gnome-vfs libgnomecanvas libgnome libbonoboui libgnomeui libgnomecups libgnomeprint libgnomeprintui gtkhtml goffice gnucash will not build. You get the following error: -2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgconf-2 -lgthread-2.0 -lrt -lgmodule-2.0 -lgobject-2.0 -lglib-2.0 -pthread -Wl,--export-dynamic -lgtkhtml-3.14 -lgnomeui-2 -lSM -lICE -lglade-2.0 -lenchant -lbonoboui-2 -lgnomevfs-2 -lgnomecanvas-2 -lgnome-2 -lpopt -lbonobo-2 -lbonobo-activation -lORBit-2 -lart_lgpl_2 -lgconf-2 -lgthread-2.0 -lrt -lgtk-x11-2.0 -lxml2 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -pthread -L/usr/lib64 -lguile -lltdl -lgmp -lcrypt -lm -lltdl -lgdk_pixbuf-2.0 -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lglade-2.0 -lgtk-x11-2.0 -lxml2 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -pthread -L/usr/lib64 -lguile -lltdl -lgmp -lcrypt -lm -lltdl -pthread -Wl,--export-dynamic -lgthread-2.0 -lrt -lgobject-2.0 -lgmodule-2.0 -lglib-2.0../../lib/libqof/qof/libgnc-qof.la -lgoffice-0.8 -lgsf-1 -lglade-2.0 -lart_lgpl_2 -lgtk-x11-2.0 -lxml2 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lfreetype -lfontconfig -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -lglib-2.0-lxml2 -lX11 -lpopt -lm -lm grep: /usr/lib64/libavahi-glib.la: No such file or directory /bin/sed: can't read /usr/lib64/libavahi-glib.la: No such file or directory libtool: link: `/usr/lib64/libavahi-glib.la' is not a valid libtool archive I fixed this by installing avahi-0.6.25-x86_64-8gsb.txz from ftp://ftp.slackware.org.uk/gsb/gsb64-2.26_slackware64-13.0/gsb64/a/ I suggest that this be added to the dependencies on the gnucash page. Thanks very much for the excellent service you provide! I've just returned to Slackware, having used in it in the early 1990s, when it was the distribution of choice (it might have been the only choice -- I don't remember). I want my computing environment very minimal -- a window manager (dwm) and the apps I need, nothing more. So need a distribution that gives me a lot of control and lets me build from the ground up. I've been using Arch, but their rolling release scheme is a bad idea. Periodically, updating your Arch system will blow it up (I'm talking about so screwed up that the only choice is to re-install). Given that their system is constantly changing, I think it's impossible for them to thoroughly test each new configuration, and the result is an unstable system. I've ignored Slackware, because of the lack of so-called modern package management. But I decided to give it a try when I finally got fed up with Arch, and was pleasantly surprised at how easy it is to get what I need installed and working, with much help from your site. /Don Allen ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
[Slackbuilds-users] postgresql
Here's another one, given that I performed so brilliantly on the first submission. The postgresql page says: Before you can run postgresql you'll need to create the database; please see README.SBo. README.SBo instructs you to add # Startup postgresql if [ -x /etc/rc.d/rc.postgresql ]; then /etc/rc.d/rc.postgresql start fi to /etc/rc.d/rc.local. But this doesn't work (the postgres server doesn't start) because /etc/rc.d/rc.postgresql doesn't have execute permission after installing the postgresql package that results from running postgresql.SlackBuild. Simply doing the obvious chmod +x /etc/rc.d/rc.postgresql in a root shell fixes the problem, but, of course, that shouldn't be necessary. I think the SlackBuild script, or, more likely, its associated doinst.sh, or the permissions on the postgresql/rc.postgresql.new (644) that results from from un-tarring the downloaded postgresql.tar.gz needs a little tweaking. /Don ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] gnucash 2.2.9 dependencies
My apologies -- you are right. I'm not sure how I did this, but I
managed to convince myself that not all of gnucash's required gnome
libraries were present on slackbuilds.org (perhaps a copy-paste
error?). It looks like they are. So with this incorrect notion in my
head, I got the libraries from gsb. Different versions and thus the
avahi dependency. Actually, there's another one that shows up at boot
time -- avahi depends on libdaemon. Anyway, false alarm.
/Don
On Fri, Apr 2, 2010 at 11:31 AM, Robby Workman rwork...@slackbuilds.org wrote:
On Fri, 2 Apr 2010 08:28:24 -0600
Vincent Batts vba...@hashbangbash.com wrote:
Thanks for the input. Have you tried just compiling the requirements
listed, only pulling from slackbuilds.org, on a slackware{,64}-13.0
system? the avahi is not needed then.
I'm adding Don to CC because he isn't (or at least wasn't)
subscribed to the list when he sent this.
As Batts said, this should all be fine *if* the dependencies
are built on a clean system. It sounds like something in
the GSB package list requires avahi, so when gnucash tries
to link that, the missing avahi is noticed.
-RW
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/
Re: [Slackbuilds-users] postgresql
I do note that the README.SBo says make sure rc.postgresql is executable, which I overlooked on first reading. I still think this is a bug, or at least an inconvenience. Why require the user to add execute permission? The installation should just take care of it. /Don On Fri, Apr 2, 2010 at 12:25 PM, Donald Allen donaldcal...@gmail.com wrote: Here's another one, given that I performed so brilliantly on the first submission. The postgresql page says: Before you can run postgresql you'll need to create the database; please see README.SBo. README.SBo instructs you to add # Startup postgresql if [ -x /etc/rc.d/rc.postgresql ]; then /etc/rc.d/rc.postgresql start fi to /etc/rc.d/rc.local. But this doesn't work (the postgres server doesn't start) because /etc/rc.d/rc.postgresql doesn't have execute permission after installing the postgresql package that results from running postgresql.SlackBuild. Simply doing the obvious chmod +x /etc/rc.d/rc.postgresql in a root shell fixes the problem, but, of course, that shouldn't be necessary. I think the SlackBuild script, or, more likely, its associated doinst.sh, or the permissions on the postgresql/rc.postgresql.new (644) that results from from un-tarring the downloaded postgresql.tar.gz needs a little tweaking. /Don ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
