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

[Fellype do Nascimento]

On 08/08/2018 05:17 PM, King Beowulf wrote:

1. Upstream does not want you to compile as root
2. All modules paths are hard coded during compile
3. relocatable package impossible? - I can't get it to work

The devs want the end user to compile as user in $HOME, and so seem
hostile to the idea that anyone might not.  There are scripts etc to try
to fix the directory paths to relocate the folder tree - they use one
for the bre-built binary - but I can't get it to work, or generate one
for Slackware

I give up.  I'm dropping this turd.

Just a tip for anyone interested in take over maintenance for sage:
The AUR guys have made efforts to get the latest version (git) working 
on Arch Linux (https://aur.archlinux.org/packages/sagemath-git/).

Well... there are up to 16 patches applied in order to get sage working :-P
Good look for the next sage maintainer...

I'm tired of getting (hate)emails.

It's sad to hear this kind of thing.
When a SlackBuild script doesn't work I don't blame its maintainer 
because I know that some environmental variables can affect the build 
(e.g.: mix SBo packages with software from other 3rdparty repos).


I've never tried to build sage from source because I have an 
underpowered machine, and as I would install the sage just out of 
curiosity it's not worth the effort.


Best wishes,

--

Dr. Fellype do Nascimento - fellype (at) gmail.com
Center for Semiconductor Components and Nanotechnologies / Laboratório de 
Plasmas
State University of Campinas, C.P. 6101,
Rua João Pandia Calogeras, No.90,
Cidade Universitária Zeferino Vaz,
Campinas, SP, 13083-870, Brazil
Fone/Phone: +55 19 35217321

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] MasterPDFEditor on 32 bit

[Fellype do Nascimento]

On 03/13/2018 09:45 AM, Rich Shepard wrote:

On Tue, 13 Mar 2018, Willy Sudiarto Raharjo wrote:

So, i need to ask the audience in this mailing list whether you are 
using

MasterPDFEditor and still using 32 bit machine?


Willy,

  Yes, I am, on two hosts: desktop and Dell Latitude 2100 with an Atom
processor. Currently running MasterPDFEditor-4.3.82 with Qt4.

Hi Willy,
I also still using a 32 bits machine and MasterPDFEditor 4 + Qt4. But I 
don't care if it is kept in version 4.3.82. That is, I don't need it to 
be updated.

So, it is OK for me if you move to Qt5 version and for 64 bit only.

Fellype
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] What is the best way to add a tag to the version of a program?

[Fellype do Nascimento]

On 01/10/2018 03:56 PM, Andrzej Telszewski wrote:


I think your reasoning is not exactly correct, but the outcome result 
is good ;-)


What I mean is that BUILD should not mimic in any way the upstream 
versioning schema.


The only thing you have to change is that you cannot use "-" in 
version string.

Common practice here is to replace it with "_" (underscore).
Then your SlackBuild should somehow deal with "_" is VERSION but with 
"-" in source tarball name.


Something like:
SRCVER=$(echo $VERSION | tr _ -)



Hi Andrzej!

Thank you for your tip. I got it.

Best regards,

Fellype

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] What is the best way to add a tag to the version of a program?

[Fellype do Nascimento]

Hi all!

At the moment I am the maintainer of sayonara-player.SlackBuild [1]. The 
version numbering structure of Sayonara Player (SP) is:


x.y.z-gitX-MMDD where x=major release, y=minor release, z=bugfix 
release and gitX-MMDD = "small adjustments" release.


Sometimes the SP developers make only some small adjustments and release it.
Currently the VERSION variable in sayonara-player.SlackBuild is set only 
as x.y.z (following the way that the previous maintainer - Edinaldo P. 
Silva - wrote it), and another variable, SRCVER, with gitX-MMDD is 
used in the 'tar' step. Then, when sayonara-player.SlackBuild is updated 
due to a small adjustments release, SBo users that use sbotools and run 
sbocheck do not notice that it was updated, even if the BUILD variable 
is changed.
For this reason, I would like to change the version number structure of 
SP in sayonara-player.SlackBuild from


VERSION=${VERSION:-x.y.z}

to

VERSION=${VERSION:-x.y.z-gitX-MMDD} (FYI, the latest version of SP 
is 1.0.0-git1-20171231)


and to discard the SRCVER variable.

I know, from a test, that it works. But I would like to know if there is 
a more "correct" way to do this change?


Best regards,

Fellype

[1] 
https://slackbuilds.org/slackbuilds/14.2/audio/sayonara-player/sayonara-player.SlackBuild


--

Dr. Fellype do Nascimento - fellype (at) gmail.com
Center for Semiconductor Components and Nanotechnologies / Laboratório de 
Plasmas
State University of Campinas, C.P. 6101,
Rua João Pandia Calogeras, No.90,
Cidade Universitária Zeferino Vaz,
Campinas, SP, 13083-870, Brazil
Fone/Phone: +55 19 35217321

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] for christmas.... i would like...

[Fellype do Nascimento]

I hope it's not too late to ask, and neither difficult to implement:

8. Add to each program page at SBo the date of the last time its 
SlackBuild script was updated.


Best regards,

Fellype
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] How to build .txz package without editing .SlackBuild file.

[Fellype do Nascimento]

On 11/22/2017 02:12 AM, Chris Novakovic wrote:

On 22/11/17 03:45, Ananda Murthy R S wrote:

By default .SlackBuild files are written to make .tgz package.

Is there any way to build .txz file from the buildscript without editing
the .SlackBuild file by passing parameter to the buildscript to create a
.txz file?

Export PKGTYPE=txz to the SlackBuild script.


Examples:
PKGTYPE=txz ./yourprogram.SlackBuild
PKGTYPE=txz sboinstall desired_program
PKGTYPE=txz sboupgrade upgradable_programs

Best regards

Fellype

___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] Can't submit academic/veusz SlackBuild because it still in pending

[Fellype do Nascimento]

Dear SBo admins,

I'm trying to submit a new version of academic/veusz SlackBuild but I 
can't do it because is appears to still in pending (after a previous 
submission that failed to build - analyzed and reported by David Spencer).
Please, remove the previous veusz submission (md5sum: 
a466ac04d55ed2fbf83fb098a8be8a77) so I can do a new one.
If you prefer, you can update it in SBo for me (the veusz.tar.gz file is 
attached).

It was updated for version 2.0.1.
The 2.x version moved from Qt4/PyQt4 to Qt5/PyQt5, then PyQt5 was added 
to "REQUIRES".
It requires CFLAGS=-std=c++11 in order to build properly with Qt 5.7 
(see line 72 of the .SlackBuild) - thanks to Jeremy Sanders.

The README file was also updated.

Best regards


 Forwarded Message 
Subject:veusz.tar.gz still in pending
Date:   Thu, 28 Sep 2017 14:53:45 -0300
From:   Fellype do Nascimento <fell...@gmail.com>
To: David Spencer <idlem...@slackbuilds.org>



On 09/23/2017 07:10 AM, David Spencer wrote:

Hi Fellype,

Unfortunately this fails to build for me, there are a huge number of
errors, please see https://pastebin.com/PXKfgCyy

I wonder if you tested this on -current, or with a different version of
qt5?  These are the SBo dependencies I used:

numpy-1.11.1
libwacom-0.26
libinput-1.8.2
libxkbcommon-0.7.1
qt5-5.7.1
qt5-webkit-5.7.1
PyQt5-5.7

Thanks
-D.


Hi David,
Can you please remove veusz.tar.gz from pending? I can't submit a new
one nor remove it by myself.
Or, if you prefer, please update it in SBo for me (the veusz.tar.gz file
is attached).
It was updated for version 2.0.1.
The 2.x version moved from Qt4/PyQt4 to Qt5/PyQt5, then PyQt5 was added
to "REQUIRES".
It requires CFLAGS=-std=c++11 in order to build properly with Qt 5.7
(see line 72 of the .SlackBuild) - thanks to Jeremy Sanders.
The README file was also updated.

Best regards




veusz.tar.gz
Description: application/gzip
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] New maintainer for sayonara-player.SlackBuild

[Fellype do Nascimento]

Hi all!
I'm taking maintenance of sayonara-player.SlackBuild.
I have authorization from the last maintainer, as indicated below.

Best regards,
Fellype

 Forwarded Message 
Subject:Assunto: Small suggestion for sayonara-player.SlackBuild
Date:   Tue, 2 May 2017 21:03:18 + (UTC)
From:   edps.mundo...@gmail.com 
Reply-To:   edps.mundo...@gmail.com 
To: fell...@gmail.com 



You can take sayonara if interested, i'm not using anymore.

* if no: i can fix this. :)

Enviado do Yahoo Mail no Android 




___
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] Small correction in README for paraview

[Fellype do Nascimento]

Hi admins,

Please, add a small correction to this line of the paraview README file:

PYTHONQT=yes -> PYTHONQT=yes (requires PythonQt)

Since passing PYTHONQT=yes to the build script will work only if 
PythonQt is installed. It will also avoid users to confuse PythonQt with 
PyQt (like this guy that is reporting it :-p )


Regards,

Fellype
___
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] sboinstall - jdk download fails

[Fellype do Nascimento]

On 04/04/2017 01:07 PM, Matteo Bernardini wrote:


Hi Fellype,

it's written in the README

https://slackbuilds.org/repository/14.2/development/jdk/

remember it's assumed that you have read the READMEs of the things you
build from SBo, also if you use some third party automated tool with
the SBo's repository.

Matteo

Hi Matteo,
Yes, it's written in the README. My fault not reading it in full.
In a case like this, it would be useful for other distracted people 
(like me) if the phases:


"You must Agree to Oracle's download agreement before this can be 
downloaded."

"This means you have to use a web browser to download it. Sorry wget folks."

were strongly highlighted in the README.
I think that something like:

* PAY ATTENTION ON IT 
*
* You must Agree to Oracle's download agreement before this can be 
downloaded. *
* This means you have to use a web browser to download it. Sorry wget 
folks."   *

***

could help in future cases.

Best regards,

Fellype

___
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] sboinstall - jdk download fails

[Fellype do Nascimento]

Hi all,
I was trying to install jdk by using sboinstall, but the download fails. 
In order to be able to download the file jdk-8u121-linux-i586.tar.gz I 
had to access the Oracle's website [1] and click on the "Accept License 
Agreement" check box.

Best regards,

Fellype

[1] 
http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html

___
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] snowballstemmer - Unable to download/verify source file

[Fellype do Nascimento]

Hi guys,

I got this error when trying to install snowballstemmer:

Unable to download/verify source file(s) for snowballstemmer:
  md5sum failure for 
/usr/sbo/distfiles/snowballstemmer-1.2.1.tar.gz#md5=643b019667a708a922172e33a99bf2fa.


BTW, snowballstemmer is listed as a required dep for Sphinx v1.5.3, but 
Sphinx was built with no problems without snowballstemmer.


Best regards.

--

Dr. Fellype do Nascimento - fellype (at) gmail.com
Center for Semiconductor Components and Nanotechnologies / Laboratório de 
Plasmas
State University of Campinas, C.P. 6101,
Rua João Pandia Calogeras, No.90,
Cidade Universitária Zeferino Vaz,
Campinas, SP, 13083-870, Brazil
Fone/Phone: +55 19 35217321

___
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] extra-cmake-modules.SlackBuild - Approved version does not gzip manpages

[Fellype do Nascimento]

Dear SBo admins,
I verified that in the approved version of the 
extra-cmake-modules.SlackBuild the piece of code that compress the 
manpages was removed from the script. Then, the manpages generated in 
the build process will not be gzipped, and this is not the standard.
In the attached script there is a more simple piece of code (just a 
line) that compress the generated manpages:


# Compress manpages
gzip -9 $PKG/usr/man/man7/*.7

Please, include this in the extra-cmake-modules.SlackBuild before the 
next update.
If you think it is more appropriate to submit the script again via 
submission form, please let me know and I will do so.


Best regards,

Fellype


extra-cmake-modules.SlackBuild
Description: all/slackware-build-script
___
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] acroread for 64-bit machines?

[Fellype do Nascimento]

Not a solution for your problems with acroread...
But have you tried to use Okular? It works well, in full screen mode, 
with pdf files created using LaTeX/beamer.


Fellype

On 02/14/2017 02:13 PM, Rich Shepard wrote:
  My use of Adobe's acrobat reader is infrequent, but good for 
presentations

showing beamer-class slides. There was no problem that I recall using it
with 14.1, but I'm having issues trying to get a version that works with
14.2.

  I have a presentation tomorrow and neither xpdf nor mupdf will 
display the

LaTeX/beamer slides full screen. The windows are full screen, but not the
PDF file.

  Do I need the 32-bit compatibility libraries to run acroread? What are
other folks using?

Rich 


___
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] ardour has more deps than that listed on REQUIRES

[Fellype do Nascimento]

Hi all!

In order to build ardour I had to install also the following packages 
(all from SBo):

cwiid (which is listed as *optional* in the README file)
serd
sord
sratom
lilv

All these deps were asked during the "./waf configure" step.
After installation of these deps, ardour builds and runs OK.

Best regards,

Fellype

--

Dr. Fellype do Nascimento - fellype (at) gmail.com
Center for Semiconductor Components and Nanotechnologies / Laboratório de 
Plasmas
State University of Campinas, C.P. 6101,
Rua João Pandia Calogeras, No.90,
Cidade Universitária Zeferino Vaz,
Campinas, SP, 13083-870, Brazil
Fone/Phone: +55 19 35217321

___
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] Submission of SlackBuild for Qwt 5

[Fellype do Nascimento]

On 12/13/2016 02:54 PM, Petar Petrov wrote:

why don't you name it something like Qwt5 or Qwt-legacy and explain in
the readme why it is different from Qwt 6? Or can't you build it
directly in the SciDAVis package? I maintain QtiPlot, and it is
possible to build in alglib for example.
Yes, it will be named as qwt5. And yes, it is possible to build it 
directly in the SciDAVis package, but I prefer to maintain both 
separated in order to make clear what are the dependencies of the package.

btw, congratulations on the SlackBuild for scidavis, it will good to
have this on SBo. Seems that GPL QtiPlot will not be updated anymore
(newest version has another license, and source code is not freely
available) so at some point it may become impossible to build.

-petar

New QtiPlot versions not freely available is bad news... QtiPlot helped 
me a lot before SciDAVis.
Both projects were very promising as alternatives for Microcal Origin, 
but both are failing in this mission due to their slow development...


Fellype
___
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] Submission of SlackBuild for Qwt 5

[Fellype do Nascimento]

Hi all!

I want to submit a SlackBuild script for Qwt, version 5.2.3, which is 
required by another application I want to submit a SlackBuild (SciDAVis).
Qwt 5.x is required by SciDAVis because its code was not ported to Qwt 
6.x yet, then it doesn't build with Qwt 6.
Currently, SlackBuilds.org has a build script for Qwt 6.1.3, whose 
maintainer is Christoph Willing.
I wrote a SlackBuild for Qwt 5 in a way that it does not conflict with 
Qwt 6 if it is installed on the system, based on the Arch Linux experience.
Do I need to get permission from Christoph (or from Zordrak, the 
previous maintainer of Qwt 5) to submit a script from an earlier version 
of Qwt?

If yes, could you give me that permission Christoph?
I also asked Zordrak for the permission, but he doesn't answered yet.

Thanks in advance.
Best regards,

Fellype


___
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] gwyddion 2.46 requires libminizip

[Fellype do Nascimento]

Hi all,

libminizip is currently assigned as an optional dependence of gwyddion. 
But when upgrading gwyddion 2.45 -> 2.46 I got the following error(s):



jpkscan.c: In function 'match_segment_filename':
jpkscan.c:804:11: error: implicit declaration of function 'atoi' 
[-Werror=implicit-function-declaration]

 *id = atoi(s);
   ^
cc1: some warnings being treated as errors
make[3]: *** [jpkscan_la-jpkscan.lo] Error 1
Makefile:1972: recipe for target 'jpkscan_la-jpkscan.lo' failed
make[3]: Leaving directory '/tmp/SBo/gwyddion-2.46/modules/file'
make[2]: *** [all-recursive] Error 1
Makefile:642: recipe for target 'all-recursive' failed
make[2]: Leaving directory '/tmp/SBo/gwyddion-2.46/modules'
make[1]: *** [all-recursive] Error 1
Makefile:612: recipe for target 'all-recursive' failed
make[1]: Leaving directory '/tmp/SBo/gwyddion-2.46'
make: *** [all] Error 2
Makefile:521: recipe for target 'all' failed
Failures:
  gwyddion: gwyddion.SlackBuild return non-zero


gwyddion 2.46 compiled fine after installing libminizip.

Regards,


--

Dr. Fellype do Nascimento - fellype (at) gmail.com
Center for Semiconductor Components and Nanotechnologies / Laboratório de 
Plasmas
State University of Campinas, C.P. 6101,
Rua João Pandia Calogeras, No.90,
Cidade Universitária Zeferino Vaz,
Campinas, SP, 13083-870, Brazil
Fone/Phone: +55 19 35217321

___
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: sayonara-player 0.9.2 segfaults; complex, untested workaround

[Fellype do Nascimento]

On 10/06/2016 11:38 PM, B Watson wrote:

On 10/6/16, Willy Sudiarto Raharjo  wrote:


Instead of adding soundtouch as hard dep for gst-plugins-* to fix a
single package, i propose to add soundtouch as hard dep of
sayonara-player with a note that it should be installed before
installing gst-plugins-bad.

List soundtouch first in REQUIRES. It'll help out the most common case,
someone using sbopkg to install all the deps (assuming gst-plugins-bad
wasn't already installed without soundtouch support). At least, most
people will install all the deps in order.
To list soundtouch as a dep of sayonara-player will solve the problem 
*if* gst-plugins-bad wasn't already installed without soundtouch 
support. But if gst-plugins-bad is already installed, it will be 
necessary to recompile it after install soundtouch. I think that the 
note must contain this information.


Fellype
___
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: sayonara-player 0.9.2 segfaults; complex, untested workaround

[Fellype do Nascimento]

Sayonara player 0.9.2 compiles OK but segfaults upon running.

I got exactly the same output as this forum thread at upstream's
website:

https://sayonara-player.com/forum/viewthread.php?tid=277

Apparently, this is what happens: sayonara requires gst-plugins-bad,
*but now* gst-plugins-bad must be compiled with soundtouch support
(which is also on SBO).

Doing this would enable the software to run.

It is right. gst-plugins-bad must be compiled with soundtouch support in 
order to enable sayonara-player to run properly. I've recompiled 
gst-plugins-bad after install soundtouch and sayonara-player runs fine now.
But soundtouch is currently assigned as an optional dependency for 
gst-plugins-bad.

Is it possible to assign soundtouch as a required dep of gst-plugins-bad?

Regards,

Fellype
___
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] Can't build libquicktime, mlt, and kdenlive using sboinstall

[Fellype do Nascimento]

Hi all,

I can't build libquicktime, mlt, and kdenlive using sboinstall.

I discovered this issue trying to install kdenlive (by using sboinstall 
kdenlive), all other deps installed fine, but these three packages 
failed to install.


The errors I got are listed below:

# libquicktime ERRORS - START #

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I../../include 
-I../../include -DLOCALE_DIR=\"/usr/share/locale\" -O2 -march=i486 
-mtune=i686 -finline-functions -Wall -Winline -Wmissing-declarations 
-Wdeclaration-after-statement -fvisibility=hidden -MT lqt_ffmpeg.lo -MD 
-MP -MF .deps/lqt_ffmpeg.Tpo -c lqt_ffmpeg.c  -fPIC -DPIC -o 
.libs/lqt_ffmpeg.o
lqt_ffmpeg.c:389:13: error: 'CODEC_ID_MPEG1VIDEO' undeclared here (not 
in a function)

   .id = CODEC_ID_MPEG1VIDEO,
 ^
lqt_ffmpeg.c:400:13: error: 'CODEC_ID_MPEG4' undeclared here (not in a 
function)

   .id = CODEC_ID_MPEG4,
 ^
lqt_ffmpeg.c:418:13: error: 'CODEC_ID_MSMPEG4V1' undeclared here (not in 
a function)

   .id = CODEC_ID_MSMPEG4V1,
 ^
lqt_ffmpeg.c:429:13: error: 'CODEC_ID_MSMPEG4V2' undeclared here (not in 
a function)

   .id = CODEC_ID_MSMPEG4V2,
 ^
lqt_ffmpeg.c:440:13: error: 'CODEC_ID_MSMPEG4V3' undeclared here (not in 
a function)

   .id = CODEC_ID_MSMPEG4V3,
 ^
lqt_ffmpeg.c:484:13: error: 'CODEC_ID_H263' undeclared here (not in a 
function)

   .id = CODEC_ID_H263,
 ^
lqt_ffmpeg.c:511:13: error: 'CODEC_ID_H264' undeclared here (not in a 
function)

   .id = CODEC_ID_H264,
 ^
lqt_ffmpeg.c:522:13: error: 'CODEC_ID_H263P' undeclared here (not in a 
function)

   .id = CODEC_ID_H263P,
 ^
lqt_ffmpeg.c:536:13: error: 'CODEC_ID_H263I' undeclared here (not in a 
function)

   .id = CODEC_ID_H263I,
 ^
lqt_ffmpeg.c:547:13: error: 'CODEC_ID_SVQ1' undeclared here (not in a 
function)

   .id = CODEC_ID_SVQ1,
 ^
lqt_ffmpeg.c:558:13: error: 'CODEC_ID_SVQ3' undeclared here (not in a 
function)

   .id = CODEC_ID_SVQ3,
 ^
lqt_ffmpeg.c:569:13: error: 'CODEC_ID_MJPEG' undeclared here (not in a 
function)

   .id = CODEC_ID_MJPEG,
 ^
lqt_ffmpeg.c:583:13: error: 'CODEC_ID_MJPEGB' undeclared here (not in a 
function)

   .id = CODEC_ID_MJPEGB,
 ^
lqt_ffmpeg.c:597:13: error: 'CODEC_ID_TARGA' undeclared here (not in a 
function)

   .id = CODEC_ID_TARGA,
 ^
lqt_ffmpeg.c:609:13: error: 'CODEC_ID_TIFF' undeclared here (not in a 
function)

   .id = CODEC_ID_TIFF,
 ^
lqt_ffmpeg.c:620:13: error: 'CODEC_ID_8BPS' undeclared here (not in a 
function)

   .id = CODEC_ID_8BPS,
 ^
lqt_ffmpeg.c:630:13: error: 'CODEC_ID_INDEO3' undeclared here (not in a 
function)

   .id = CODEC_ID_INDEO3,
 ^
lqt_ffmpeg.c:641:13: error: 'CODEC_ID_RPZA' undeclared here (not in a 
function)

   .id = CODEC_ID_RPZA,
 ^
lqt_ffmpeg.c:651:13: error: 'CODEC_ID_SMC' undeclared here (not in a 
function)

   .id = CODEC_ID_SMC,
 ^
lqt_ffmpeg.c:661:13: error: 'CODEC_ID_CINEPAK' undeclared here (not in a 
function)

   .id = CODEC_ID_CINEPAK,
 ^
lqt_ffmpeg.c:672:13: error: 'CODEC_ID_CYUV' undeclared here (not in a 
function)

   .id = CODEC_ID_CYUV,
 ^
lqt_ffmpeg.c:683:13: error: 'CODEC_ID_QTRLE' undeclared here (not in a 
function)

   .id = CODEC_ID_QTRLE,
 ^
lqt_ffmpeg.c:696:13: error: 'CODEC_ID_MSRLE' undeclared here (not in a 
function)

   .id = CODEC_ID_MSRLE,
 ^
lqt_ffmpeg.c:706:13: error: 'CODEC_ID_DVVIDEO' undeclared here (not in a 
function)

   .id = CODEC_ID_DVVIDEO,
 ^
lqt_ffmpeg.c:775:13: error: 'CODEC_ID_FFVHUFF' undeclared here (not in a 
function)

   .id = CODEC_ID_FFVHUFF,
 ^
lqt_ffmpeg.c:788:13: error: 'CODEC_ID_FFV1' undeclared here (not in a 
function)

   .id = CODEC_ID_FFV1,
 ^
lqt_ffmpeg.c:804:13: error: 'CODEC_ID_DNXHD' undeclared here (not in a 
function)

   .id = CODEC_ID_DNXHD,
 ^
lqt_ffmpeg.c:820:13: error: 'CODEC_ID_MPEG2VIDEO' undeclared here (not 
in a function)

   .id = CODEC_ID_MPEG2VIDEO,
 ^
lqt_ffmpeg.c:842:13: error: 'CODEC_ID_MP3' undeclared here (not in a 
function)

   .id = CODEC_ID_MP3,
 ^
lqt_ffmpeg.c:842:13: error: initializer element is not constant
lqt_ffmpeg.c:842:13: note: (near initialization for 'codecidmap_a[0].id')
lqt_ffmpeg.c:854:13: error: 'CODEC_ID_MP2' undeclared here (not in a 
function)

   .id = CODEC_ID_MP2,
 ^
lqt_ffmpeg.c:854:13: error: initializer element is not constant
lqt_ffmpeg.c:854:13: note: (near initialization for 'codecidmap_a[1].id')
lqt_ffmpeg.c:869:13: error: 'CODEC_ID_AC3' undeclared here (not in a 
function)

   .id = CODEC_ID_AC3,
 ^
lqt_ffmpeg.c:869:13: error: initializer element is not constant
lqt_ffmpeg.c:869:13: