Re: [Slackbuilds-users] BUG: pdftk decrypt doesn't work

2017-01-02 Thread Eduardo Sanchez 
> Hi Eduardo
> 
> I tested on slackware-current and it worked fine
> I created a blank PDF with password willysr using LibreOffice export
> feature and then i decrypt the file using this command:
> pdftk test.pdf input_pw willysr output test_decrypted.pdf
> 
> i can open the decrypted file in Atril

Hi Willy:

This leaves me completely dumbfounded.

Something I have must be messing with my system.

Thanks,

Eduardo


-- 
Eduardo Sánchez Gauto, Abog., Th.M.
Abogado - Traductor Público Matriculado Inglés - Español
Web: http://sombragris.org - Blog: http://shadow.sombragris.org
TW: @thegreyshadow - FB: /thegreyshadow
Teléfono: (0991) 755-355 - Asunción, Paraguay
==
___
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] BUG: Cannot build clementine after chromaprint upgrade

2017-01-02 Thread Willy Sudiarto Raharjo 
> I'm using -current but this might happen as well with 14.2 so I report
> it here.
> 
> After SBo's last ChangeLog and its chromaprint-1.4 update, clementine
> cannot run anymore.
> 
> Trying to rebuild fails with the following errors:
> 
> [ 61%] Building CXX object
> src/CMakeFiles/clementine_lib.dir/musicbrainz/acoustidclient.cpp.o
> [ 61%] Building CXX object
> src/CMakeFiles/clementine_lib.dir/musicbrainz/chromaprinter.cpp.o 
> /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:
> In member function ‘QString
> Chromaprinter::CreateFingerprint()’: 
> /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:147:35:
> error: invalid conversion from ‘void*’ to ‘const int16_t* {aka const
> short int*}’ [-fpermissive] data.size() / 2); ^ In file included
> from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: 
> /usr/include/chromaprint.h:235:45:
> note:   initializing argument 2 of ‘int
> chromaprint_feed(ChromaprintContext*, const int16_t*, int)’
> CHROMAPRINT_API int chromaprint_feed(ChromaprintContext *ctx, const
> int16_t *data, int size);
> ^ /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:152:72:
> error: invalid conversion from ‘void**’ to ‘uint32_t** {aka unsigned
> int**}’ [-fpermissive] int ret =
> chromaprint_get_raw_fingerprint(chromaprint, , ); ^ In file
> included
> from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: 
> /usr/include/chromaprint.h:273:45:
> note:   initializing argument 2 of ‘int
> chromaprint_get_raw_fingerprint(ChromaprintContext*, uint32_t**, int*)’
> CHROMAPRINT_API int chromaprint_get_raw_fingerprint(ChromaprintContext
> *ctx, uint32_t **fingerprint, int *size);
> ^ /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:158:62:
> error: invalid conversion from ‘void*’ to ‘const uint32_t* {aka const
> unsigned int*}’ [-fpermissive] , _size, 1); ^ In file
> included
> from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: 
> /usr/include/chromaprint.h:331:45:
> note:   initializing argument 1 of ‘int
> chromaprint_encode_fingerprint(const uint32_t*, int, int, char**, int*,
> int)’ CHROMAPRINT_API int chromaprint_encode_fingerprint(const uint32_t
> *fp, int size, int algorithm, char **encoded_fp, int *encoded_size, int
> base64);
> ^ /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:158:62:
> error: invalid conversion from ‘void**’ to ‘char**’ [-fpermissive]
> , _size, 1); ^ In file included
> from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: 
> /usr/include/chromaprint.h:331:45:
> note:   initializing argument 4 of ‘int
> chromaprint_encode_fingerprint(const uint32_t*, int, int, char**, int*,
> int)’ CHROMAPRINT_API int chromaprint_encode_fingerprint(const uint32_t
> *fp, int size, int algorithm, char **encoded_fp, int *encoded_size, int
> base64); ^ At global scope: cc1plus: error: unrecognized command line
> option ‘-Wno-unknown-warning-option’ [-Werror] cc1plus: error:
> unrecognized command line option ‘-Wno-unused-private-field’ [-Werror]
> cc1plus: all warnings being treated as errors
> src/CMakeFiles/clementine_lib.dir/build.make:7366: recipe for target
> 'src/CMakeFiles/clementine_lib.dir/musicbrainz/chromaprinter.cpp.o'
> failed make[2]: ***
> [src/CMakeFiles/clementine_lib.dir/musicbrainz/chromaprinter.cpp.o]
> Error 1 CMakeFiles/Makefile2:1071: recipe for target
> 'src/CMakeFiles/clementine_lib.dir/all' failed make[1]: ***
> [src/CMakeFiles/clementine_lib.dir/all] Error 2 Makefile:127: recipe
> for target 'all' failed make: *** [all] Error 2
> 
> ===
> 
> btw, I'm not at all interested in "audio fingerprints". Is there a way
> to get rid of this dependency?

It's fixed in my branch already
https://slackbuilds.org/cgit/slackbuilds/commit/?h=willysr=9c5f47526eaef77727c6ff4eb53cdeb90c4e95b4



-- 
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/

[Slackbuilds-users] BUG: Cannot build clementine after chromaprint upgrade

2017-01-02 Thread Eduardo Sanchez 
Hi there,

I'm using -current but this might happen as well with 14.2 so I report
it here.

After SBo's last ChangeLog and its chromaprint-1.4 update, clementine
cannot run anymore.

Trying to rebuild fails with the following errors:

[ 61%] Building CXX object
src/CMakeFiles/clementine_lib.dir/musicbrainz/acoustidclient.cpp.o
[ 61%] Building CXX object
src/CMakeFiles/clementine_lib.dir/musicbrainz/chromaprinter.cpp.o 
/tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:
In member function ‘QString
Chromaprinter::CreateFingerprint()’: 
/tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:147:35:
error: invalid conversion from ‘void*’ to ‘const int16_t* {aka const
short int*}’ [-fpermissive] data.size() / 2); ^ In file included
from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: 
/usr/include/chromaprint.h:235:45:
note:   initializing argument 2 of ‘int
chromaprint_feed(ChromaprintContext*, const int16_t*, int)’
CHROMAPRINT_API int chromaprint_feed(ChromaprintContext *ctx, const
int16_t *data, int size);
^ /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:152:72:
error: invalid conversion from ‘void**’ to ‘uint32_t** {aka unsigned
int**}’ [-fpermissive] int ret =
chromaprint_get_raw_fingerprint(chromaprint, , ); ^ In file
included
from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: 
/usr/include/chromaprint.h:273:45:
note:   initializing argument 2 of ‘int
chromaprint_get_raw_fingerprint(ChromaprintContext*, uint32_t**, int*)’
CHROMAPRINT_API int chromaprint_get_raw_fingerprint(ChromaprintContext
*ctx, uint32_t **fingerprint, int *size);
^ /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:158:62:
error: invalid conversion from ‘void*’ to ‘const uint32_t* {aka const
unsigned int*}’ [-fpermissive] , _size, 1); ^ In file
included
from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: 
/usr/include/chromaprint.h:331:45:
note:   initializing argument 1 of ‘int
chromaprint_encode_fingerprint(const uint32_t*, int, int, char**, int*,
int)’ CHROMAPRINT_API int chromaprint_encode_fingerprint(const uint32_t
*fp, int size, int algorithm, char **encoded_fp, int *encoded_size, int
base64);
^ /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:158:62:
error: invalid conversion from ‘void**’ to ‘char**’ [-fpermissive]
, _size, 1); ^ In file included
from /tmp/SBo/Clementine-1.3.1/src/musicbrainz/chromaprinter.cpp:27:0: 
/usr/include/chromaprint.h:331:45:
note:   initializing argument 4 of ‘int
chromaprint_encode_fingerprint(const uint32_t*, int, int, char**, int*,
int)’ CHROMAPRINT_API int chromaprint_encode_fingerprint(const uint32_t
*fp, int size, int algorithm, char **encoded_fp, int *encoded_size, int
base64); ^ At global scope: cc1plus: error: unrecognized command line
option ‘-Wno-unknown-warning-option’ [-Werror] cc1plus: error:
unrecognized command line option ‘-Wno-unused-private-field’ [-Werror]
cc1plus: all warnings being treated as errors
src/CMakeFiles/clementine_lib.dir/build.make:7366: recipe for target
'src/CMakeFiles/clementine_lib.dir/musicbrainz/chromaprinter.cpp.o'
failed make[2]: ***
[src/CMakeFiles/clementine_lib.dir/musicbrainz/chromaprinter.cpp.o]
Error 1 CMakeFiles/Makefile2:1071: recipe for target
'src/CMakeFiles/clementine_lib.dir/all' failed make[1]: ***
[src/CMakeFiles/clementine_lib.dir/all] Error 2 Makefile:127: recipe
for target 'all' failed make: *** [all] Error 2

===

btw, I'm not at all interested in "audio fingerprints". Is there a way
to get rid of this dependency?

Thanks,


Eduardo


-- 
Eduardo Sánchez Gauto, Abog., Th.M.
Abogado - Traductor Público Matriculado Inglés - Español
Web: http://sombragris.org - Blog: http://shadow.sombragris.org
TW: @thegreyshadow - FB: /thegreyshadow
Teléfono: (0991) 755-355 - Asunción, Paraguay
==
___
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] skippy-xd source missing

2017-01-02 Thread Willy Sudiarto Raharjo 
> Try this:
> http://slackware.uk/sbosrcarch/by-md5/5/7/57bb5c943059ae959efd4a035d4f7279/skippy-xd-0.5.1.tar.xz

Thanks
fixed in my branch


-- 
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/

[Slackbuilds-users] Nvidia updates 375.26 commentary

2017-01-02 Thread King Beowulf 
I've refactored the nvidia-drive script to use nvidia-installer instead
of sifting through all the libs and symlinks manually. This was getting
unwieldy and error-prone. The script should now be able to be updated by
just changing $VERSION. Also, GLVND and vulkan support is now possible.

As a result of these changes, nvidia-switch is gone for now. See README
to restore mesa and xorg F/OSS functionality.

Issues and help request:
1. nvidia-installer peforms a backup of mesa and xorg files but mangles
them into a weird directory tree. Is there a way to get the installer to
leave them alone for an out-of-tree install to $PKG? The
nvidia-installer backups and log are archived here:
/var/lib/nvidia-archive-2017-01-02.bz2
/var/log/nvidia-installer-2017-01-02.log
after the script runs.

2. libwfb.so does not seem to get backed up (see error below)? I've
kludged a stanza to restore libwfb after nvidia-installer's mangling but
its ugly.  The nvidia version give the error below which I can't figure
out to fix properly.

(II) Loading sub module "wfb"
(II) LoadModule: "wfb"
[(II) Loading /usr/lib64/xorg/modules/libwfb.so
(EE) Failed to load /usr/lib64/xorg/modules/libwfb.so:
/usr/lib64/xorg/modules/libwfb.so: undefined symbol:
PictureScreenPrivateIndex
(II) UnloadModule: "wfb"
(II) Unloading wfb
(EE) Failed to load module "wfb" (loader failed, 7)
...
(EE) NVIDIA(0): Need libwfb but wfbScreenInit not found

3. COMPAT32 feedback is appreciated.  So far it looks ok (Steam and WINE).

4. I am currently unable to fully test on Slackware 32-bit.

As always, let me know if you spot anything weird.
-Ed



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] skippy-xd source missing

2017-01-02 Thread edps.mundo...@gmail.com 
Hi!
Try this:
http://slackware.uk/sbosrcarch/by-md5/5/7/57bb5c943059ae959efd4a035d4f7279/skippy-xd-0.5.1.tar.xz

Cheers,
Edinaldo___
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] skippy-xd source missing

2017-01-02 Thread Nicolas Kovacs 
Hi,

Source tarball for skippy-xd is not available.

Cheers,

Niki
-- 
Microlinux - Solutions informatiques durables
7, place de l'église - 30730 Montpezat
Web  : http://www.microlinux.fr
Mail : i...@microlinux.fr
Tél. : 04 66 63 10 32
___
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] Updates - 20161231.1

2017-01-02 Thread Ryan P.C. McQuen 
This would be nearly impossible for some packages. |atom|, for instance
has hundreds of module dependencies.

OK. That’s a bit of a shame, because it’s against the philosophy we try
to keep here (i.e. SlackBuild shall not download on its own).

It’s a good philosophy, but it is not practical for a tool like slackrepo
to block scripts from doing *anything*. The classic Unix way is to allow
the user to shoot themselves in the foot … this is why no tools are
officially endorsed by SBo other than the old fashioned way of running
everything manually. Like I said before, I’d call this a slackrepo issue,
and it should be reported to their issue tracker/mailing list.

—
-Ryan
[ryanpcmcquen.org]
​
-- 
--
[ryanpcmcquen.org]
___
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] Updates - 20161231.1

2017-01-02 Thread Jeremy Hansen 
If the dependencies are properly listed by the package maintainer, and
they're installed prior to trying to install the main package, it obviously
won't need to download any.

But if there is no real option to pass to the build/install process to
prevent downloading additional modules, that's a little frustrating. It's a
nice option for those who like it, but it should be easily disableable.

On Mon, Jan 2, 2017, 4:21 PM Andrzej Telszewski 
wrote:

> On 02/01/17 21:46, Ryan P.C. McQuen wrote:
> >
> > Do you know if it's possible to disable automatic downloading by the
> > setup script (on the command line)?
> >
> > If it is, I think we should apply this rule to SlackBuilds and then
> > we had the true dependencies ;-)
> >
> > This would be nearly impossible for some packages. |atom|, for instance
> > has hundreds of module dependencies.
> >
>
> OK. That's a bit of a shame, because it's against the philosophy we try
> to keep here (i.e. SlackBuild shall not download on its own).
>
> --
> 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 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] Updates - 20161231.1

2017-01-02 Thread Andrzej Telszewski 

On 02/01/17 21:46, Ryan P.C. McQuen wrote:


Do you know if it's possible to disable automatic downloading by the
setup script (on the command line)?

If it is, I think we should apply this rule to SlackBuilds and then
we had the true dependencies ;-)

This would be nearly impossible for some packages. |atom|, for instance
has hundreds of module dependencies.



OK. That's a bit of a shame, because it's against the philosophy we try 
to keep here (i.e. SlackBuild shall not download on its own).


--
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] Updates - 20161231.1

2017-01-02 Thread Ryan P.C. McQuen 
> Do you know if it's possible to disable automatic downloading by the setup
> script (on the command line)?
>
> If it is, I think we should apply this rule to SlackBuilds and then we had
> the true dependencies ;-)
>
This would be nearly impossible for some packages. atom, for instance has
hundreds of module dependencies.
​


-- 
-Ryan
[ryanpcmcquen.org]
___
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] Updates - 20161231.1

2017-01-02 Thread Jeremy Hansen 
Best I could find is modifying the program's setup.cfg and add the
following:

[easy_install]
allow_hosts: None

This doesn't disable attempting to download packages (I couldn't find
anything for that), but it does prevents connections because it, obviously,
doesn't have any allowable hosts.

On Mon, Jan 2, 2017, 2:17 PM Andrzej Telszewski 
wrote:

> On 02/01/17 18:37, Audrius Kažukauskas wrote:
> > On Mon, 2017-01-02 at 01:16:32 +0100, Andrzej Telszewski wrote:
> >> Maybe slackrepo does not allow to download something needed by the
> Python
> >> install script.
> >
> > I don't know slackrepo well enough, but this seems likely.
> >
> >> But it shouldn't be downloaded in the first place.
> >>
> >> I don't know enough about Python installation scripts to say the final
> word.
> >
> > borgbackup's setup.py contains the following line:
> >
> >   setup_requires=['setuptools_scm>=1.7'],
> >
> > Thus setuptools_scm should really be a requirement for borgbackup.
> >
> > setuptools documentation has this description of setup_requires field:
> >
> >   A string or list of strings specifying what other distributions need
> >   to be present in order for the setup script to run.  setuptools will
> >   attempt to obtain these (even going so far as to download them using
> >   EasyInstall) before processing the rest of the setup script or
> >   commands. <...>
> >
> > This explains why the build succeeded for Willy and, if slackrepo does
> > indeed disable network access, why it didn't for you.
> >
>
> Thanks for clarification.
> That is what I was thinking is more or less happening.
>
> Do you know if it's possible to disable automatic downloading by the
> setup script (on the command line)?
>
> If it is, I think we should apply this rule to SlackBuilds and then we
> had the true dependencies ;-)
>
> --
> 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 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] Updates - 20161231.1

2017-01-02 Thread Andrzej Telszewski 

On 02/01/17 18:37, Audrius Kažukauskas wrote:

On Mon, 2017-01-02 at 01:16:32 +0100, Andrzej Telszewski wrote:

Maybe slackrepo does not allow to download something needed by the Python
install script.


I don't know slackrepo well enough, but this seems likely.


But it shouldn't be downloaded in the first place.

I don't know enough about Python installation scripts to say the final word.


borgbackup's setup.py contains the following line:

  setup_requires=['setuptools_scm>=1.7'],

Thus setuptools_scm should really be a requirement for borgbackup.

setuptools documentation has this description of setup_requires field:

  A string or list of strings specifying what other distributions need
  to be present in order for the setup script to run.  setuptools will
  attempt to obtain these (even going so far as to download them using
  EasyInstall) before processing the rest of the setup script or
  commands. <...>

This explains why the build succeeded for Willy and, if slackrepo does
indeed disable network access, why it didn't for you.



Thanks for clarification.
That is what I was thinking is more or less happening.

Do you know if it's possible to disable automatic downloading by the 
setup script (on the command line)?


If it is, I think we should apply this rule to SlackBuilds and then we 
had the true dependencies ;-)


--
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] Updates - 20161231.1

2017-01-02 Thread Audrius Kažukauskas 
On Mon, 2017-01-02 at 01:16:32 +0100, Andrzej Telszewski wrote:
> Maybe slackrepo does not allow to download something needed by the Python
> install script.

I don't know slackrepo well enough, but this seems likely.

> But it shouldn't be downloaded in the first place.
> 
> I don't know enough about Python installation scripts to say the final word.

borgbackup's setup.py contains the following line:

  setup_requires=['setuptools_scm>=1.7'],

Thus setuptools_scm should really be a requirement for borgbackup.

setuptools documentation has this description of setup_requires field:

  A string or list of strings specifying what other distributions need
  to be present in order for the setup script to run.  setuptools will
  attempt to obtain these (even going so far as to download them using
  EasyInstall) before processing the rest of the setup script or
  commands. <...>

This explains why the build succeeded for Willy and, if slackrepo does
indeed disable network access, why it didn't for you.

-- 
Audrius Kažukauskas
http://neutrino.lt/


signature.asc
Description: PGP 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] atlas failed to build with recent updates

2017-01-02 Thread Serban Udrea 

On 01/01/2017 01:36 AM, Willy Sudiarto Raharjo wrote:

When I've tried to build atlas on the fresh-installed slackware64-14.2
machine with all recent updates installed, I've got an error (the complete
log is in attachment). Similar problems was with -current installations,
but it is reasonable since it is not supported. The machine is HP ProDesk
400
(Pentium 4400, all integrated in H110 chipset).


Tested here in clean VM

lapack-atlas:
  MD5SUM check for lapack-3.6.1.tgz ... OK
  Building package lapack-atlas-3.6.1-x86_64-1_SBo.tgz ... OK
  Installing package lapack-atlas-3.6.1-x86_64-1_SBo.tgz ... OK

atlas:
  MD5SUM check for atlas3.10.3.tar.bz2 ... OK
  Building package atlas-3.10.3-x86_64-1_SBo.tgz ... OK
  Installing package atlas-3.10.3-x86_64-1_SBo.tgz ... OK
...


Hello and Happy New Year!

Last year I got two reports about errors during ATLAS compilation, one was from 
Daniil. As Willy, I too cannot reproduce the error, which seems to be platform 
dependent and related to the fact that on the affected machines ATLAS's configure 
decides at some point to use g++ for further compilation. I'll try again to find a 
solution and probably file a bug report with ATLAS's maintainer but I cannot 
promise a solution very soon.


Best regards,

Serban Udrea
___
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/