That which could be fixed in SBo thread.

Ponce, just a heads up, make sure you double check the library install path for libfreshwrapper-pepperflash.so if you update it further. In newer versions, such as 0.3.3, the library is named a bit different to libfreshwrapper-flashplayer.so, no idea why, and I do believe the configuration file is required to use the search /file/path/to for the pepperflash plugin from Chrome/Chromium. You may want to install it by default rather than leave it to the user configuration as a suggestion. It "says" it's optional, but the last time I tried it, the plugin wouldn't work well, or work at all.

the plugin file name is libfreshwrapper-flashplayer.so since version 0.3.3 (before it was called libfreshwrapper-pepperflash.so)

https://github.com/i-rinat/freshplay...ses/tag/v0.3.3

FYI 0.3.3 seems to work fine without any config file here...

(beside the fact another update for f***ing flash -19.0.0.226- has just been released...)

And Flash is supposed to be dead...

QtiPlot wont build on -current with Python enabled. Maybe need to be patched for sip version in -current.

I've not checked recently, but it's in the patch list for current:

http://cgit.ponce.cc/slackbuilds/commit/?h=QtiPlot

Originally Posted by ponce I've not checked recently, but it's in the patch list for current: http://cgit.ponce.cc/slackbuilds/commit/?h=QtiPlot

it wont build with theese patches with Python enabled.

maybe similar bug https://bugs.launchpad.net/ubuntu/+s...t/+bug/1243269

I've not tried it yet, but you can check if it builds with this additional patch

https://projects.archlinux.org/svnto...ckages/qtiplot

Yes, the sip upgrade back in August broke QtiPlot again... there are patches out there (e.g. Arch) so I'll try and fix it later tonight, (and I'll fix my mistake in the avogadro commit message at the same time!)

Edit: Wow Matteo you work fast!

unfortunately that patch seems not to be enough... still

g++ -c -pipe -O2 -D_REENTRANT -Wall -W -DSCRIPTING_CONSOLE -DSVN_REVISION="\"\"" -DQT_PLUGIN -DTRANSLATIONS_PATH=\"/usr/share/qtiplot/translations\" -DMANUAL_PATH=\"/usr/doc/QtiPlot-0.9.8.9/manual\" -DSCRIPTING_MUPARSER -DSCRIPTING_PYTHON -DPYTHON_CONFIG_PATH=\"/usr/share/qtiplot\" -DGL2PS_HAVE_LIBPNG -DTEX_OUTPUT -DHAVE_ALGLIB -DHAVE_TAMUANOVA -DNO_LOG_FILE -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_QT3SUPPORT_LIB -DQT3_SUPPORT -DQT_XML_LIB -DQT_OPENGL_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/lib64/qt/mkspecs/linux-g++ -I. -I/usr/lib64/qt/include/QtCore -I/usr/lib64/qt/include/QtNetwork -I/usr/lib64/qt/include/QtGui -I/usr/lib64/qt/include/QtOpenGL -I/usr/lib64/qt/include/QtXml -I/usr/lib64/qt/include/Qt3Support -I/usr/lib64/qt/include/QtSvg -I/usr/lib64/qt/include -I/usr/lib64/qt/include/QtAssistantClient -I/usr/lib64/qt/include/QtAssistant -I../3rdparty/qwt/src -I../3rdparty/qwtplot3d/include -Iicons -Isrc/analysis -Isrc/analysis/dialogs -Isrc/core -Isrc/excel -Isrc/lib/include -Isrc/lib/3rdparty/qtcolorpicker/src -Isrc/plot2D -Isrc/plot2D/dialogs -Isrc/plot3D -Isrc/matrix -Isrc/table -Isrc/scripting -I/usr/include/python2.7 -I../3rdparty/QTeXEngine/src -I/usr/include/libalglib -I/usr/include/tamu_anova -I/usr/include -Isrc/plugins/OriginPlugin -Isrc/plugins/OriginPlugin/liborigin1 -Isrc/plugins/OriginPlugin/liborigin2 -Isrc/plugins/OriginPlugin/tree.phi-sci.com -I../3rdparty/boost -I/usr/include -I/tmp/SBo/QtiPlot-0.9.8.9/qtiplot-0.9.8.9/tmp/qtiplot -o ../tmp/qtiplot/sipqtiImageWidget.o ../tmp/qtiplot/sipqtiImageWidget.cpp
In file included from src/scripting/qti.sip:1119:0:
icons/../src/plot2D/ImageWidget.h: In member function 'virtual void sipImageWidget::paintEvent(QPaintEvent*)':
icons/../src/plot2D/ImageWidget.h:73:7: error: 'virtual void ImageWidget::paintEvent(QPaintEvent*)' is private
  void paintEvent(QPaintEvent *e);
       ^
../tmp/qtiplot/sipqtiImageWidget.cpp:877:35: error: within this context
         ImageWidget::paintEvent(a0);
                                   ^
make: *** [../tmp/qtiplot/sipqtiImageWidget.o] Error 1

Yeah, but one of the others (qtiplot-0.9.8.9-private.patch) seems to help

Edit: It builds, but (I just noticed) it puts its libraries in /usr/lib/qtiplot/plugins/ instead of lib64

guys,

i apologize that i have been inactive with my slackbuilds recently. If you find a patch for qtiplot and any other of the slackbuilds i maintain, please let me know! and thank you very, very much for your efforts!

Originally Posted by solarfields i apologize that i have been inactive with my slackbuilds recently. If you find a patch for qtiplot and any other of the slackbuilds i maintain, please let me know! and thank you very, very much for your efforts!

Hey it's no problem! I'm quite inactive too at the moment

I just pushed a QtiPlot patched for -current to https://github.com/Ponce/slackbuilds...ademic/QtiPlot -- it seems to build... As I'm sure you understand there's nothing "official" about Ponce's repo, and if anything there saves you work when you update your SlackBuilds for 14.2, that's great, but I don't really understand the apps and can't really test them in the way that maintainers do. (The reason why I try to fix things for -current is because, when something is broken, I don't know if it's broken because of -current, or broken because my build environment and tools have a bug!)

Of all your SlackBuilds, there are two that I think are very difficult to fix on current at the moment (cufflinks and tophat). One exposes a bug in gcc-4.9, the other exposes a bug in boost-1.58 -- don't make your life miserable by trying to fix them!

Py3cairo no longer compiles with the python-3.5.0 now in the SBo repo.

patching file waf
Hunk #1 succeeded at 153 with fuzz 2.
/tmp/SBo/pycairo-1.10.0/.waf3-1.6.4-e3c1e08604b18a10567cfcd2d02eb6e6 /tmp/SBo/pycairo-1.10.0
patching file waflib/Tools/python.py
/tmp/SBo/pycairo-1.10.0
  ./options()
Setting top to                           : /tmp/SBo/pycairo-1.10.0 
Setting out to                           : /tmp/SBo/pycairo-1.10.0/build_directory 
  ./configure()
Checking for 'gcc' (c compiler)          : ok 
Checking for program python              : /usr/bin/python3 
Checking for python version              : (3, 5, 0, 'final', 0) 
Traceback (most recent call last):
  File "/tmp/SBo/pycairo-1.10.0/.waf3-1.6.4-e3c1e08604b18a10567cfcd2d02eb6e6/waflib/Scripting.py", line 93, in waf_entry_point
    run_commands()
  File "/tmp/SBo/pycairo-1.10.0/.waf3-1.6.4-e3c1e08604b18a10567cfcd2d02eb6e6/waflib/Scripting.py", line 145, in run_commands
    run_command(cmd_name)
  File "/tmp/SBo/pycairo-1.10.0/.waf3-1.6.4-e3c1e08604b18a10567cfcd2d02eb6e6/waflib/Scripting.py", line 138, in run_command
    ctx.execute()
  File "/tmp/SBo/pycairo-1.10.0/.waf3-1.6.4-e3c1e08604b18a10567cfcd2d02eb6e6/waflib/Configure.py", line 124, in execute
    super(ConfigurationContext,self).execute()
  File "/tmp/SBo/pycairo-1.10.0/.waf3-1.6.4-e3c1e08604b18a10567cfcd2d02eb6e6/waflib/Context.py", line 87, in execute
    self.recurse([os.path.dirname(g_module.root_path)])
  File "/tmp/SBo/pycairo-1.10.0/.waf3-1.6.4-e3c1e08604b18a10567cfcd2d02eb6e6/waflib/Context.py", line 127, in recurse
    user_function(self)
  File "/tmp/SBo/pycairo-1.10.0/wscript", line 29, in configure
    ctx.check_python_headers()
  File "/tmp/SBo/pycairo-1.10.0/.waf3-1.6.4-e3c1e08604b18a10567cfcd2d02eb6e6/waflib/Configure.py", line 217, in fun
    return f(*k,**kw)
  File "/tmp/SBo/pycairo-1.10.0/.waf3-1.6.4-e3c1e08604b18a10567cfcd2d02eb6e6/waflib/Tools/python.py", line 146, in check_python_headers
    result=conf.check(lib=name,uselib='PYEMBED',libpath=path,mandatory=False,msg='Checking for library %s in LIBDIR'%name)
  File "/tmp/SBo/pycairo-1.10.0/.waf3-1.6.4-e3c1e08604b18a10567cfcd2d02eb6e6/waflib/Configure.py", line 217, in fun
    return f(*k,**kw)
  File "/tmp/SBo/pycairo-1.10.0/.waf3-1.6.4-e3c1e08604b18a10567cfcd2d02eb6e6/waflib/Tools/c_config.py", line 357, in check
    ret=self.run_c_code(*k,**kw)
  File "/tmp/SBo/pycairo-1.10.0/.waf3-1.6.4-e3c1e08604b18a10567cfcd2d02eb6e6/waflib/Configure.py", line 217, in fun
    return f(*k,**kw)
  File "/tmp/SBo/pycairo-1.10.0/.waf3-1.6.4-e3c1e08604b18a10567cfcd2d02eb6e6/waflib/Tools/c_config.py", line 435, in run_c_code
    bld.compile()
  File "/tmp/SBo/pycairo-1.10.0/.waf3-1.6.4-e3c1e08604b18a10567cfcd2d02eb6e6/waflib/Build.py", line 190, in compile
    self.store()
  File "/tmp/SBo/pycairo-1.10.0/.waf3-1.6.4-e3c1e08604b18a10567cfcd2d02eb6e6/waflib/Utils.py", line 300, in f
    ret=fun(*k,**kw)
  File "/tmp/SBo/pycairo-1.10.0/.waf3-1.6.4-e3c1e08604b18a10567cfcd2d02eb6e6/waflib/Build.py", line 164, in store
    cPickle.dump(data,f)
AttributeError: Can't pickle local object 'Context.__init__.<locals>.node_class'

sbotools stopped working with the 10-29-2015 -Current update. I already emailed the author so hopefully it can be fixed.

Originally Posted by orbea Py3cairo no longer compiles with the python-3.5.0 now in the SBo repo. patching file waf Hunk #1 succeeded at 153 with fuzz 2. /tmp/SBo/pycairo-1.10.0/.waf3-1.6.4-e3c1e08604b18a10567cfcd2d02eb6e6 /tmp/SBo/pycairo-1.10.0 patching file waflib/Tools/python.py /tmp/SBo/pycairo-1.10.0 ./options() Setting top to : /tmp/SBo/pycairo-1.10.0 Setting out to : /tmp/SBo/pycairo-1.10.0/build_directory ./configure() Checking for 'gcc' (c compiler) : ok Checking for program python : /usr/bin/python3 Checking for python version : (3, 5, 0, 'final', 0) Traceback (most recent call last): File "/tmp/SBo/pycairo-1.10.0/.waf3-1.6.4-e3c1e08604b18a10567cfcd2d02eb6e6/waflib/Scripting.py", line 93, in waf_entry_point run_commands() [snip lots of traceback]

The problem is that the SlackBuild treats each waf command as a script rather than executable i.e. it always tries to run 'python3 ./waf ....' whereas it should actually be running 'PYTHON=python3 ./waf ...'. Unfortunately the python 3.4 related patch repeats the mistake. A successful build (works for me) is possible by commenting out the patch named pycairo-1.10.0-waf_python_3_4-1.patch in the SlackBuild, as well as replacing any instance of 'python3 ./waf" with 'PYTHON=python3 ./waf'

chris