[Slackbuilds-users] gnulib is evil
Heads up to maintainers. If your build uses gnulib, there's a good chance it's modifying the timestamp of /usr/lib when it runs. I don't mean "if your build has gnulib as a dependency", because the normal way to use gnulib is to bundle it with the source code. The top-level directory will generally have a gnulib/ directory (along with src/ and whatever else is in the tarball). What it's doing is checking $PREFIX/lib (along with some other directories) to see whether it's able to create a file whose name is longer than 14 characters. man-db was doing this, and I had to patch the configure script to stop it. This appears to be severe brain damage to me: - The /usr/lib test will always fail if you're compiling as a normal user - Nobody still runs a 1989 version of SCO or SVr3 or whatever - ./configure and make should never write to system directories (only 'make install' should do that) Probably worth looking at how I patched it, if you want to do something similar for your own build. Patch is attached to this email (also in my user/urchlay/updates git branch). dont_write_in_usr.diff.gz Description: GNU Zip compressed data ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Question about git workflow
On 03/05/2017 04:38 AM, Willy Sudiarto Raharjo wrote: >>> is there a guide or any sort of documentation about how to submit >>> patches to slackbuilds.org via git? >> >> I think it's not supported. > > Not officially supported, but i personally have accepted PR from public > github repository for some people for their own scripts (not updating > others nor new submission). I've always wondered about this. Wouldn't it be easier for the maintenance team to deal with _some_ form of version control, rather than updated archives delivered through slackbuilds.org? -- Dave ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] Updates - 20170305.1
Hi folks, Sorry for the unscheduled updates but the xen update seems quite important. We also had so many new python submission for Flask applications. Happy Weekend :) Sun Mar 5 04:30:32 UTC 2017 academic/lapack95: New maintainer. desktop/gtk-theme-Greybird: Updated for version 3.22.12. games/FlightGear-data: Updated for version 2017.1.2. games/FlightGear: Updated for version 2017.1.2. games/chessx: Updated for version 1.4.4. libraries/SimGear: Updated for version 2017.1.2. libraries/html5lib: New maintainer libraries/libseccomp: Updated for version 2.3.2. misc/grc: Updated for version 1.10.1. misc/subsurface: Updated for version 4.6.3 network/krb5: Updated for version 1.15.1. network/sslscan: Fix DOWNLOAD url. network/weechat: Fix path on x86_64 perl/perl-Math-BigInt: Updated for version 1.999810. perl/perl-Sidef: Updated for version 2.36. python/Flask-Babel: Added (i18n/l10n support to Flask). python/Flask-Gravatar: Added (Flask extension for Gravatar service). python/Flask-HTMLmin: Added (Minimize rendered templates html). python/Flask-Mail: Added (Flask extension for sending email). python/Flask-Principal: Added (Identity management for flask). python/Flask-Security: Added (Simple security for Flask apps). python/Flask-WTF: Added (Simple integration of Flask and WTForms). python/PyStemmer: Added (Snowball stemming algorithms). python/WTForms: Added (web forms validation). python/alabaster: Added (Sphinx theme). python/babel: Update DEP. python/extras: Added (Python bindings for augeas). python/htmlmin: Added (An HTML Minifier). python/imagesize: Added (python library for images). python/linecache2: Added (Backports of the linecache python module). python/pyrsistent: Added (data structures). python/python-augeas: Update DOWNLOAD url. python/python-mimeparse: Added (module for parsing mime-type). python/snowballstemmer: Added (stemmer algorithms for python). python/speaklater: Added (Python module). python/testtools: Added (Python unit testing framework extension). python/traceback2: Addded (Backports of the traceback module). system/letsencrypt: Updated for version 0.12.0. system/vinterm: Fix icon/desktop installation. system/xen: XSA 207-210 update. +--+ -- Willy Sudiarto Raharjo signature.asc Description: OpenPGP digital signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Submitting packages with cyclic dependencies via website
On 03/05/2017 04:33 AM, Willy Sudiarto Raharjo wrote: >> how are we supposed to submit new packages with cyclic dependencies >> via the website? >> >> This time, I am trying to submit two python packages fixtures and testtools. >> I tried to be imaginative and removed testtools from REQUIRES, then >> submitted testtools and then tried to submit again fixtures with the >> testtools included in the REQUIRES, but >> "a submission by the name 'fixtures' is already pending approval." :) >> >> How should I proceed so that we can have these two packages added properly? > > Unless you want to resubmit everything, i have removed fixture from > testtools in my branch and after public update, i will remove fixture > from pending (it can't be deleted now since it's listed as dep for > testtools). > > cyclic dependency should be listed in the README. > I think opencv and ffmpeg also had the same problem I will wait for the next public update, then resubmit fixture and testtools with the appropriate REQUIRES string and with fixed README files. -- Nikos ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Submitting packages with cyclic dependencies via website
> how are we supposed to submit new packages with cyclic dependencies > via the website? > > This time, I am trying to submit two python packages fixtures and testtools. > I tried to be imaginative and removed testtools from REQUIRES, then > submitted testtools and then tried to submit again fixtures with the > testtools included in the REQUIRES, but > "a submission by the name 'fixtures' is already pending approval." :) > > How should I proceed so that we can have these two packages added properly? Unless you want to resubmit everything, i have removed fixture from testtools in my branch and after public update, i will remove fixture from pending (it can't be deleted now since it's listed as dep for testtools). cyclic dependency should be listed in the README. I think opencv and ffmpeg also had the same problem -- Willy Sudiarto Raharjo signature.asc Description: OpenPGP digital signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Question about git workflow
>> is there a guide or any sort of documentation about how to submit >> patches to slackbuilds.org via git? > > I think it's not supported. Not officially supported, but i personally have accepted PR from public github repository for some people for their own scripts (not updating others nor new submission). -- Willy Sudiarto Raharjo signature.asc Description: OpenPGP digital signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Atom doesn't build
I've just turned on my laptop and tried to upgrade atom using su - instead of su. Now it works. Andreas, thank you for the tip! ___ Site/blog @ https://crish4cks.net/ Registered user #488179 @ http://linuxcounter.net Slackware, because it works! =) Da: SlackBuilds-users per conto di Andreas Guldstrand Inviato: sabato 4 marzo 2017 13:41:01 A: SlackBuilds.org Users List Oggetto: Re: [Slackbuilds-users] Atom doesn't build On 4 March 2017 at 11:04, Cristiano Urban wrote: > I've tried to update atom via sbotools (# sboupgrade atom) for three > consecutive times and it fails to build. > > Here below I attach a .txt with some info. > > Does anyone have the same issue? I had the same issue when trying to install it too (not upgrade because I didn't have it before). But I noticed that the prerequisite, nodejs, had something it installed into /etc/profile.d, so I assumed I needed that loaded before installing atom, so I logged out, and logged in again using a proper root shell and tried again, and then it worked. Regards / Andreas ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/ ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Question about git workflow
On 04/03/17 14:41, Nikos Giotis wrote: is there a guide or any sort of documentation about how to submit patches to slackbuilds.org via git? I think it's not supported. -- Best regards, Andrzej Telszewski ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] gdal SlackBuild fails
On Sat, Mar 04, 2017 at 03:11:36PM +0100, Matteo Bernardini wrote: > 2017-03-04 15:02 GMT+01:00 Duncan Roe : > > On Sat, Mar 04, 2017 at 12:15:29PM +0100, Matteo Bernardini wrote: > >> 2017-03-04 12:06 GMT+01:00 Duncan Roe : > >> > On Sat, Mar 04, 2017 at 09:48:36PM +1100, Duncan Roe wrote: > >> >> Paste is http://pastebin.com/v4gXJbDr > >> >> > >> > And, I did not override -j1. This pocessor does have 2 cores though. > >> > >> Duncan, sorry, before anyone else asks: the paste above looks done > >> from your unprivilege used environment. > >> it could be there are no differences but maybe it's better if you post > >> the one you got from running the SlackBuild (you can take it directly > >> from the /tm/SBo/gdal-* directory) from the root environment (in which > >> you get by running "su -l" from your user shell). > >> > >> Matteo > > > > Hi Matteo, > > > > I ran the build from a logged-in-as-root environment, as evidenced by: > > > >> 22:00:11# echo $0 > >> -bash > > > > I just do su but then immediately start a fresh xterm (with a pink > > background, > > so I know it's root); then exit from the su. > > > > What looks unprivileged in the paste? > > in the paste you have these lines > > PATH: /home/dunc/bin64 > PATH: /home/dunc/bin > PATH: /home/dunc/command_line_tools/bin > PATH: /usr/local/sbin > PATH: /usr/sbin > PATH: /sbin > PATH: /usr/local/bin > PATH: /usr/bin > PATH: /bin > PATH: /usr/games > PATH: /usr/lib/java/bin > PATH: /usr/lib64/kde4/libexec > PATH: /usr/lib64/qt/bin > PATH: /usr/share/texmf/bin > > these mean that you have executed just "su" and not "su -" (or "su > -l") so your root environment, not having being launched as a true > login shell, was polluted by user variables (see point 3 of the howto > https://slackbuilds.org/howto/). > you shouldn't run SBo's build scripts executing just "su". > > Matteo No, they don't mean that at all: > 00:47:13# ls -l ~/.bashrc > lrwxrwxrwx 1 root root 18 May 5 2014 /root/.bashrc -> /home/dunc/.bashrc Cheers ... Duncan. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] gdal SlackBuild fails
2017-03-04 15:02 GMT+01:00 Duncan Roe : > On Sat, Mar 04, 2017 at 12:15:29PM +0100, Matteo Bernardini wrote: >> 2017-03-04 12:06 GMT+01:00 Duncan Roe : >> > On Sat, Mar 04, 2017 at 09:48:36PM +1100, Duncan Roe wrote: >> >> Paste is http://pastebin.com/v4gXJbDr >> >> >> > And, I did not override -j1. This pocessor does have 2 cores though. >> >> Duncan, sorry, before anyone else asks: the paste above looks done >> from your unprivilege used environment. >> it could be there are no differences but maybe it's better if you post >> the one you got from running the SlackBuild (you can take it directly >> from the /tm/SBo/gdal-* directory) from the root environment (in which >> you get by running "su -l" from your user shell). >> >> Matteo > > Hi Matteo, > > I ran the build from a logged-in-as-root environment, as evidenced by: > >> 22:00:11# echo $0 >> -bash > > I just do su but then immediately start a fresh xterm (with a pink background, > so I know it's root); then exit from the su. > > What looks unprivileged in the paste? in the paste you have these lines PATH: /home/dunc/bin64 PATH: /home/dunc/bin PATH: /home/dunc/command_line_tools/bin PATH: /usr/local/sbin PATH: /usr/sbin PATH: /sbin PATH: /usr/local/bin PATH: /usr/bin PATH: /bin PATH: /usr/games PATH: /usr/lib/java/bin PATH: /usr/lib64/kde4/libexec PATH: /usr/lib64/qt/bin PATH: /usr/share/texmf/bin these mean that you have executed just "su" and not "su -" (or "su -l") so your root environment, not having being launched as a true login shell, was polluted by user variables (see point 3 of the howto https://slackbuilds.org/howto/). you shouldn't run SBo's build scripts executing just "su". Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] gdal SlackBuild fails
On Sat, Mar 04, 2017 at 12:15:29PM +0100, Matteo Bernardini wrote: > 2017-03-04 12:06 GMT+01:00 Duncan Roe : > > On Sat, Mar 04, 2017 at 09:48:36PM +1100, Duncan Roe wrote: > >> On Fri, Mar 03, 2017 at 12:19:09PM +, David Spencer wrote: > >> > > Looks like the kind of issue caused by using MAKEFLAGS=-j3 (or anything > >> > > other than -j1). That's a snap diagnosis, I don't know what gdal even > >> > > is. > >> > > >> > gdal already has 'make -j1' hard-coded, because it definitely fails > >> > with multiple parallel make jobs. > >> > > >> > For some reason that I don't understand, on Duncan's system gcc is > >> > being invoked through libtool. > >> > The compilation explicitly has '-o > >> > build/temp.linux-x86_64-2.7/extensions/.libs/gdal_wrap.o', but that > >> > file does not exist at the time the next command 'g++ -pthread -shared > >> > build/temp.linux-x86_64-2.7/extensions/gdal_wrap.o' is invoked. > >> > > >> > So this really does look like a multiple parallel make jobs failure. > >> > Duncan, for avoidance of doubt you haven't removed -j1 or overridden it > >> > somehow? > >> > Are you on -current? > >> > Do you have CC and/or CXX defined in the environment? > >> > could you put your config.log on pastebin or somewhere similar? > >> > > >> Hi David, > >> > >> On 14.2 unpatched > >> > >> env has CC=gcc > >> > >> Paste is http://pastebin.com/v4gXJbDr > >> > > And, I did not override -j1. This pocessor does have 2 cores though. > > Duncan, sorry, before anyone else asks: the paste above looks done > from your unprivilege used environment. > it could be there are no differences but maybe it's better if you post > the one you got from running the SlackBuild (you can take it directly > from the /tm/SBo/gdal-* directory) from the root environment (in which > you get by running "su -l" from your user shell). > > Matteo Hi Matteo, I ran the build from a logged-in-as-root environment, as evidenced by: > 22:00:11# echo $0 > -bash I just do su but then immediately start a fresh xterm (with a pink background, so I know it's root); then exit from the su. What looks unprivileged in the paste? Cheers ... Duncan. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] Question about git workflow
Hi, is there a guide or any sort of documentation about how to submit patches to slackbuilds.org via git? Nikos ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] Submitting packages with cyclic dependencies via website
Hi, how are we supposed to submit new packages with cyclic dependencies via the website? This time, I am trying to submit two python packages fixtures and testtools. I tried to be imaginative and removed testtools from REQUIRES, then submitted testtools and then tried to submit again fixtures with the testtools included in the REQUIRES, but "a submission by the name 'fixtures' is already pending approval." :) How should I proceed so that we can have these two packages added properly? Also, Nikos ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Atom doesn't build
On 4 March 2017 at 11:04, Cristiano Urban wrote: > I've tried to update atom via sbotools (# sboupgrade atom) for three > consecutive times and it fails to build. > > Here below I attach a .txt with some info. > > Does anyone have the same issue? I had the same issue when trying to install it too (not upgrade because I didn't have it before). But I noticed that the prerequisite, nodejs, had something it installed into /etc/profile.d, so I assumed I needed that loaded before installing atom, so I logged out, and logged in again using a proper root shell and tried again, and then it worked. Regards / Andreas ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Proper installation directory for TCL files?
* On 2017 04 Mar 04:50 -0600, Andreas Guldstrand wrote: > On 4 March 2017 at 03:45, Nate Bargmann wrote: > > Right now the TCL files are being placed in /usr/lib[64]/tcl by the > > library's build system, yet I find tcl8, tcl8.6, and tclx8.4 under > > /usr/lib[64]. Which of these directories should the generated files be > > placed into? Also, there is a generated pkgIndex.tcl file that would > > appear to conflict with any of the above full installation directories. > > Hi, while I don't exactly know things about TCL, the pkgIndex.tcl file > sounds similar to the perllocal.pod that is usually generated by perl > installation tools - that file is simply removed in the template for > perl slackbuilds, and I'd assume that would be the right thing to do > for this file as well. But as I said, I don't really know much about > TCL, so take my words with a couple grains of salt. Hi Andreas. My post was incomplete. Here is the tree for the TCL files as installed by the package's Makefile: $ tree ./usr/lib64/tcl/ ./usr/lib64/tcl/ `-- Library |-- librarytcl-99.99.so |-- librarytcl.la `-- pkgIndex.tcl As can seen, the installed files will be in their own directory, so any existing pkgIndex.tcl would not be overwritten. My question now is even a bit more simple, and perhaps by looking things over again, I've found an acceptable answer. I see the sqlite package is installed under /usr/lib[64]/tcl8.6/sqlite3 which contains libtclsqlite3.so and pkgIndex.tcl. It appears as though pkgIndex.tcl is necessary to map the .so file for the tcl interpreter, so I shall proceed by having the Slackbuild script rename 'tcl' to 'tcl8.6', remove librarytcl.la, and continue testing. Thanks. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Ham radio, Linux, bikes, and more: http://www.n0nb.us ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] SOLVED: gdal SlackBuild fails
> I removed CC=gcc from the environment and the SB ran to completion. Sorry for the noise everybody: I missed your solution before I replied just now :( Anyway I hope the additional info was useful. As I implied previously, gdal's configure is quite fragile in multiple ways. I'll add --without-libtool to the SlackBuild, because explicitly setting a default in an environment variable shouldn't break stuff. Thanks Duncan, we got there in the end :) -D. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] gdal SlackBuild fails
>> env has CC=gcc aaah!!! Add this to the ./configure arguments --without-libtool \ and/or try it again without CC in the environment. (There have been reports on the gdal mailing list where setting CC/CXX in the environment causes gdal's configure to use libtool, leading to python-related build failures. Both steps in that chain of causality are bizarre and unwelcome; let's hope the workround works.) Thanks -D. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] gdal SlackBuild fails
2017-03-04 12:06 GMT+01:00 Duncan Roe : > On Sat, Mar 04, 2017 at 09:48:36PM +1100, Duncan Roe wrote: >> On Fri, Mar 03, 2017 at 12:19:09PM +, David Spencer wrote: >> > > Looks like the kind of issue caused by using MAKEFLAGS=-j3 (or anything >> > > other than -j1). That's a snap diagnosis, I don't know what gdal even is. >> > >> > gdal already has 'make -j1' hard-coded, because it definitely fails >> > with multiple parallel make jobs. >> > >> > For some reason that I don't understand, on Duncan's system gcc is >> > being invoked through libtool. >> > The compilation explicitly has '-o >> > build/temp.linux-x86_64-2.7/extensions/.libs/gdal_wrap.o', but that >> > file does not exist at the time the next command 'g++ -pthread -shared >> > build/temp.linux-x86_64-2.7/extensions/gdal_wrap.o' is invoked. >> > >> > So this really does look like a multiple parallel make jobs failure. >> > Duncan, for avoidance of doubt you haven't removed -j1 or overridden it >> > somehow? >> > Are you on -current? >> > Do you have CC and/or CXX defined in the environment? >> > could you put your config.log on pastebin or somewhere similar? >> > >> Hi David, >> >> On 14.2 unpatched >> >> env has CC=gcc >> >> Paste is http://pastebin.com/v4gXJbDr >> > And, I did not override -j1. This pocessor does have 2 cores though. Duncan, sorry, before anyone else asks: the paste above looks done from your unprivilege used environment. it could be there are no differences but maybe it's better if you post the one you got from running the SlackBuild (you can take it directly from the /tm/SBo/gdal-* directory) from the root environment (in which you get by running "su -l" from your user shell). Matteo ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] SOLVED: gdal SlackBuild fails
On Sat, Mar 04, 2017 at 10:06:09PM +1100, Duncan Roe wrote: > On Sat, Mar 04, 2017 at 09:48:36PM +1100, Duncan Roe wrote: > > On Fri, Mar 03, 2017 at 12:19:09PM +, David Spencer wrote: > > > > Looks like the kind of issue caused by using MAKEFLAGS=-j3 (or anything > > > > other than -j1). That's a snap diagnosis, I don't know what gdal even > > > > is. > > > > > > gdal already has 'make -j1' hard-coded, because it definitely fails > > > with multiple parallel make jobs. > > > > > > For some reason that I don't understand, on Duncan's system gcc is > > > being invoked through libtool. > > > The compilation explicitly has '-o > > > build/temp.linux-x86_64-2.7/extensions/.libs/gdal_wrap.o', but that > > > file does not exist at the time the next command 'g++ -pthread -shared > > > build/temp.linux-x86_64-2.7/extensions/gdal_wrap.o' is invoked. > > > > > > So this really does look like a multiple parallel make jobs failure. > > > Duncan, for avoidance of doubt you haven't removed -j1 or overridden it > > > somehow? > > > Are you on -current? > > > Do you have CC and/or CXX defined in the environment? > > > could you put your config.log on pastebin or somewhere similar? > > > > > Hi David, > > > > On 14.2 unpatched > > > > env has CC=gcc > > > > Paste is http://pastebin.com/v4gXJbDr > > > And, I did not override -j1. This pocessor does have 2 cores though. > I removed CC=gcc from the environment and the SB ran to completion. It's been in my .bashrc for years, will take it out. Cheers ... Duncan. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] gdal SlackBuild fails
On Sat, Mar 04, 2017 at 09:48:36PM +1100, Duncan Roe wrote: > On Fri, Mar 03, 2017 at 12:19:09PM +, David Spencer wrote: > > > Looks like the kind of issue caused by using MAKEFLAGS=-j3 (or anything > > > other than -j1). That's a snap diagnosis, I don't know what gdal even is. > > > > gdal already has 'make -j1' hard-coded, because it definitely fails > > with multiple parallel make jobs. > > > > For some reason that I don't understand, on Duncan's system gcc is > > being invoked through libtool. > > The compilation explicitly has '-o > > build/temp.linux-x86_64-2.7/extensions/.libs/gdal_wrap.o', but that > > file does not exist at the time the next command 'g++ -pthread -shared > > build/temp.linux-x86_64-2.7/extensions/gdal_wrap.o' is invoked. > > > > So this really does look like a multiple parallel make jobs failure. > > Duncan, for avoidance of doubt you haven't removed -j1 or overridden it > > somehow? > > Are you on -current? > > Do you have CC and/or CXX defined in the environment? > > could you put your config.log on pastebin or somewhere similar? > > > Hi David, > > On 14.2 unpatched > > env has CC=gcc > > Paste is http://pastebin.com/v4gXJbDr > And, I did not override -j1. This pocessor does have 2 cores though. Cheers ... Duncan. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] LibreOffice.SlackBuild: java selection code
On 4 March 2017 at 11:21, Andrzej Telszewski wrote: > Isn't it the task of the shell to actually source the correct file? That would force the user to log out and log in again between installing openjdk/openjdk8/jdk and LibreOffice (or have them source it manually of course, but that wouldn't be "the shell" doing it anyway) ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Proper installation directory for TCL files?
On 4 March 2017 at 03:45, Nate Bargmann wrote: > Right now the TCL files are being placed in /usr/lib[64]/tcl by the > library's build system, yet I find tcl8, tcl8.6, and tclx8.4 under > /usr/lib[64]. Which of these directories should the generated files be > placed into? Also, there is a generated pkgIndex.tcl file that would > appear to conflict with any of the above full installation directories. Hi, while I don't exactly know things about TCL, the pkgIndex.tcl file sounds similar to the perllocal.pod that is usually generated by perl installation tools - that file is simply removed in the template for perl slackbuilds, and I'd assume that would be the right thing to do for this file as well. But as I said, I don't really know much about TCL, so take my words with a couple grains of salt. Regards / Andreas ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] gdal SlackBuild fails
On Fri, Mar 03, 2017 at 12:19:09PM +, David Spencer wrote: > > Looks like the kind of issue caused by using MAKEFLAGS=-j3 (or anything > > other than -j1). That's a snap diagnosis, I don't know what gdal even is. > > gdal already has 'make -j1' hard-coded, because it definitely fails > with multiple parallel make jobs. > > For some reason that I don't understand, on Duncan's system gcc is > being invoked through libtool. > The compilation explicitly has '-o > build/temp.linux-x86_64-2.7/extensions/.libs/gdal_wrap.o', but that > file does not exist at the time the next command 'g++ -pthread -shared > build/temp.linux-x86_64-2.7/extensions/gdal_wrap.o' is invoked. > > So this really does look like a multiple parallel make jobs failure. > Duncan, for avoidance of doubt you haven't removed -j1 or overridden it > somehow? > Are you on -current? > Do you have CC and/or CXX defined in the environment? > could you put your config.log on pastebin or somewhere similar? > Hi David, On 14.2 unpatched env has CC=gcc Paste is http://pastebin.com/v4gXJbDr Cheers ... Duncan. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] LibreOffice.SlackBuild: java selection code
Hi,
In the latest LibreOffice.SlackBuild you have:
JAVA=${JAVA:-openjdk}
if [ "$JAVA" = "openjdk" ]; then
. /etc/profile.d/openjdk.sh
use_java="--with-java=java"
elif [ "$JAVA" = "openjdk8" ]; then
. /etc/profile.d/openjdk8.sh
use_java="--with-java=java"
elif [ "$JAVA" = "jdk" ]; then
. /etc/profile.d/jdk.sh
use_java="--with-java=java"
elif [ "$JAVA" = "no" ]; then
use_java="--with-java=no"
fi
Isn't it the task of the shell to actually source the correct file?
--
Best regards,
Andrzej Telszewski
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
[Slackbuilds-users] Atom doesn't build
Hi, I've tried to update atom via sbotools (# sboupgrade atom) for three consecutive times and it fails to build. Here below I attach a .txt with some info. Does anyone have the same issue? Thanks to all in advance, Cristiano. ___ Site/blog @ https://crish4cks.net/ Registered user #488179 @ http://linuxcounter.net Slackware, because it works! =) DELETE_CACHE=yes|no (default: no) * Use atom with some version of electron previously installed in the system. This feature don't make a distributable binary, and you can use like as node script application. This requires electron available in SBo ELECTRON=yes|no (default=no) If you need to use any option do something like: ELECTRON=yes ./atom.SlackBuild NOTE: Atom may failed to build at first attempt. Simply retry the process and it should be working. It looks like atom has options; would you like to set any when the slackbuild is run? [n] y Please supply any options here, or enter to skip: DISABLE_METRICS=yes DELETE_CACHE=yes Proceed with atom? [y] y atom added to upgrade queue. Upgrade queue: atom Are you sure you wish to continue? [y] y tar: /usr/sbo/repo/development/atom/atom-1.14.3.tar.gz: funzione "open" non riuscita: File o directory non esistente tar: Error is not recoverable: exiting now atom-1.14.3/ atom-1.14.3/.coffeelintignore atom-1.14.3/.gitattributes atom-1.14.3/.gitignore atom-1.14.3/.pairs atom-1.14.3/.python-version atom-1.14.3/.travis.yml atom-1.14.3/CHANGELOG.md atom-1.14.3/CODE_OF_CONDUCT.md atom-1.14.3/CONTRIBUTING.md atom-1.14.3/Dockerfile atom-1.14.3/ISSUE_TEMPLATE.md atom-1.14.3/LICENSE.md atom-1.14.3/PULL_REQUEST_TEMPLATE.md atom-1.14.3/README.md atom-1.14.3/apm/ atom-1.14.3/apm/README.md atom-1.14.3/apm/package.json atom-1.14.3/appveyor.yml atom-1.14.3/atom.sh atom-1.14.3/benchmarks/ atom-1.14.3/benchmarks/benchmark-runner.js atom-1.14.3/benchmarks/text-editor-large-file-construction.bench.js atom-1.14.3/circle.yml atom-1.14.3/coffeelint.json atom-1.14.3/docs/ atom-1.14.3/docs/README.md atom-1.14.3/docs/apm-rest-api.md atom-1.14.3/docs/build-instructions/ atom-1.14.3/docs/build-instructions/build-status.md atom-1.14.3/docs/build-instructions/freebsd.md atom-1.14.3/docs/build-instructions/linux.md atom-1.14.3/docs/build-instructions/macos.md atom-1.14.3/docs/build-instructions/windows.md atom-1.14.3/docs/contributing-to-packages.md atom-1.14.3/docs/contributing.md atom-1.14.3/docs/native-profiling.md atom-1.14.3/dot-atom/ atom-1.14.3/dot-atom/.gitignore atom-1.14.3/dot-atom/init.coffee atom-1.14.3/dot-atom/keymap.cson atom-1.14.3/dot-atom/packages/ atom-1.14.3/dot-atom/packages/README.md atom-1.14.3/dot-atom/snippets.cson atom-1.14.3/dot-atom/styles.less atom-1.14.3/exports/ atom-1.14.3/exports/atom.js atom-1.14.3/exports/clipboard.js atom-1.14.3/exports/ipc.js atom-1.14.3/exports/remote.js atom-1.14.3/exports/shell.js atom-1.14.3/exports/web-frame.js atom-1.14.3/keymaps/ atom-1.14.3/keymaps/base.cson atom-1.14.3/keymaps/darwin.cson atom-1.14.3/keymaps/linux.cson atom-1.14.3/keymaps/win32.cson atom-1.14.3/menus/ atom-1.14.3/menus/darwin.cson atom-1.14.3/menus/linux.cson atom-1.14.3/menus/win32.cson atom-1.14.3/package.json atom-1.14.3/resources/ atom-1.14.3/resources/app-icons/ atom-1.14.3/resources/app-icons/beta/ atom-1.14.3/resources/app-icons/beta/atom.icns atom-1.14.3/resources/app-icons/beta/atom.ico atom-1.14.3/resources/app-icons/beta/png/ atom-1.14.3/resources/app-icons/beta/png/1024.png atom-1.14.3/resources/app-icons/beta/png/128.png atom-1.14.3/resources/app-icons/beta/png/16.png atom-1.14.3/resources/app-icons/beta/png/24.png atom-1.14.3/resources/app-icons/beta/png/256.png atom-1.14.3/resources/app-icons/beta/png/32.png atom-1.14.3/resources/app-icons/beta/png/48.png atom-1.14.3/resources/app-icons/beta/png/512.png atom-1.14.3/resources/app-icons/beta/png/64.png atom-1.14.3/resources/app-icons/dev/ atom-1.14.3/resources/app-icons/dev/atom.icns atom-1.14.3/resources/app-icons/dev/atom.ico atom-1.14.3/resources/app-icons/dev/png/ atom-1.14.3/resources/app-icons/dev/png/1024.png atom-1.14.3/resources/app-icons/dev/png/128.png atom-1.14.3/resources/app-icons/dev/png/16.png atom-1.14.3/resources/app-icons/dev/png/24.png atom-1.14.3/resources/app-icons/dev/png/256.png atom-1.14.3/resources/app-icons/dev/png/32.png atom-1.14.3/resources/app-icons/dev/png/48.png atom-1.14.3/resources/app-icons/dev/png/512.png atom-1.14.3/resources/app-icons/dev/png/64.png atom-1.14.3/resources/app-icons/stable/ atom-1.14.3/resources/app-icons/stable/atom.icns atom-1.14.3/resources/app-icons/stable/atom.ico atom-1.14.3/resources/app-icons/stable/png/ atom-1.14.3/resources/app-icons/stable/png/1024.png atom-1.14.3/resources/app-icons/stable/png/128.png atom-1.14.3/resources/app-icons/stable/png/16.png atom-1.14.3/resources/app-icons/stable/png/24.png atom-1.14.3/resources/app-icons/stable/png/256.png atom-1.14.3/resources/app-icons/stable/png/32.png atom-1.14.3/resources/app-
