[Slackbuilds-users] Latest Nvidia driver 384.59

[Lenard Spencer]

I guess this message should be directed to Ed since he maintains the 
nvidia-driver and nvidia-kernel packages.


As you all may know, the latest Nvidia long-term driver 384.59 was 
released a couple of weeks ago.  Since I was out of town all last week, 
today was the first chance I got to play with it.  I have found that 
there are two lines in nvidia-driver.SlackBuild that apparently not 
needed.  Here's the patch I came up with:




--- nvidia-driver.SlackBuild.orig2017-08-06 20:56:53.0 -0400
+++ nvidia-driver.SlackBuild2017-08-07 16:40:16.581511628 -0400
@@ -26,7 +26,7 @@
 # see changelog.txt

 PRGNAM=nvidia-driver
-VERSION=${VERSION:-375.66}
+VERSION=${VERSION:-384.59}
 BUILD=${BUILD:-1}
 TAG=${TAG:-_SBo}

@@ -313,11 +313,7 @@
cd -
 fi

-#ICDs
-install -m 644 nvidia.icd $PKG/etc/OpenCL/vendors/
-install -m 644 nvidia_icd.json $PKG/etc/vulkan/icd.d/
-
-# Remove xorg conf file since we take care of that in nvidia-driver
+# Remove xorg conf file since we take care of that in nvidia-kernel
 rm -rf $PKG/etc/X11/xorg.conf.d

 cat < $PKG/var/log/nvidia/README.txt


The #ICDs section apparently is not needed as these two files get 
written when nvidia-driver is installed. (At least I haven't gotten it 
to fail on either stable or current.)


As a side note, the GLVND=no parameter seems to be broken ATM.

Hope this helps


___
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] http://www.hyperrealm.com/libconfig/

[Daniel Prosser]

The hyperrealm site is still down, FYI. The source is available on
GitHub (https://github.com/hyperrealm/libconfig/archive/v1.5.tar.gz),
but it has a different md5sum and requires an autoreconf to build.
There's also a version 1.6 available. Maybe switching to the GitHub link
would be more reliable?
On Fri, Aug 04, 2017 at 11:31:39AM +0200, Matteo Bernardini wrote:
> 2017-08-04 11:28 GMT+02:00 Habs :
> >
> > Hello good morning all
> >
> > Server error @ http://www.hyperrealm.com/libconfig/
> >
> > libconfig-1.5.tar.gz
> >
> >
> > Is there an alternative link for now please ?
> 
> http://slackware.uk/sbosrcarch/by-name/libraries/libconfig/libconfig-1.5.tar.gz
> ___
> 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 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] Exported ARCH causing libraries/hiredis build failure

[B Watson]

On 8/7/17, David Spencer  wrote:

> Promise me you're not thinking of another git orgy?  You've got
> shelves to fix :)

The shelves are as fixed as they're going to be. Currently they're
supporting 40-50lbs of junk, and haven't ripped out of the wall yet :)

> Warning!! **Lots** of the unset_ARCH SlackBuilds below are binary
> packages that are picky about the ARCH you request on 32 bit, and so
> they do *NOT* need unexport on the make command.

If there's no make command, I definitely won't add one...
___
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] Exported ARCH causing libraries/hiredis build failure

[David Spencer]

> Definitely. What's the list of builds you have hints for in slackrepo?

Promise me you're not thinking of another git orgy?  You've got
shelves to fix :)

Warning!! **Lots** of the unset_ARCH SlackBuilds below are binary
packages that are picky about the ARCH you request on 32 bit, and so
they do *NOT* need unexport on the make command.

References to DISPLAY and DISTCC_HOSTS below are (I think) not
relevant. This list might include packages that have been removed or
renamed since the last time I updated all this, and I haven't retested
these in a long time, so there may be some false positives. I don't
think the difference between unset and noexport is relevant for these
purposes.

Cheers
-D.

development/asl/asl.hint:PRAGMA="unset_ARCH"
development/avr8-gnu-toolchain/avr8-gnu-toolchain.hint:PRAGMA="unset_ARCH"
development/bmake/bmake.hint:PRAGMA="noexport_TAG"
development/eclipse-cpp/eclipse-cpp.hint:PRAGMA="unset_ARCH"
development/eclipse-java/eclipse-java.hint:PRAGMA="unset_ARCH"
development/eclipse-jee/eclipse-jee.hint:PRAGMA="unset_ARCH"
development/fpc/fpc.hint:PRAGMA="unset_ARCH"
development/lazarus/lazarus.hint:PRAGMA="unset_ARCH"
development/mtasc/mtasc.hint:PRAGMA="unset_ARCH"
development/robomongo/robomongo.hint:PRAGMA="unset_ARCH"
development/sbcl/sbcl.hint:PRAGMA="unset_ARCH"
development/vstudio/vstudio.hint:PRAGMA="unset_ARCH"
games/etlegacy/etlegacy.hint:PRAGMA="unset_ARCH"
games/firestorm-opensim/firestorm-opensim.hint:PRAGMA="unset_ARCH"
games/firestorm/firestorm.hint:PRAGMA="unset_ARCH"
games/gargoyle/gargoyle.hint:PRAGMA="noexport_BUILD download_basename"
games/gens-gs/gens-gs.hint:PRAGMA="unset_ARCH"
games/ioquake3/ioquake3.hint:PRAGMA="unset_ARCH"
games/libretro-lutro/libretro-lutro.hint:PRAGMA="unset_ARCH"
games/mame/mame.hint:PRAGMA="noexport_BUILD"
games/mame2010-libretro/mame2010-libretro.hint:PRAGMA="noexport_BUILD"
games/mame2014-libretro/mame2014-libretro.hint:PRAGMA="noexport_BUILD"
games/quakeforge/quakeforge.hint:PRAGMA="unset_ARCH nofakeroot"
games/singularity/singularity.hint:PRAGMA="unset_ARCH"
games/skulltag/skulltag.hint:PRAGMA="unset_ARCH"
games/tome/tome.hint:PRAGMA="unset_ARCH"
games/tome4/tome4.hint:PRAGMA="noexport_ARCH"
libraries/hiredis/hiredis.hint:PRAGMA="unset_ARCH"
libraries/xview/xview.hint:PRAGMA="unset_ARCH"
libraries/zziplib/zziplib.hint:PRAGMA="noexport_BUILD"
misc/hashkill/hashkill.hint:PRAGMA="unset_BUILD"
misc/klibc/klibc.hint:PRAGMA="kernel nofakeroot unset_DISTCC_HOSTS unset_ARCH"
misc/moedict-desktop.app/moedict-desktop.app.hint:PRAGMA="unset_ARCH"
misc/par2cmdline-tbb/par2cmdline-tbb.hint:PRAGMA="unset_ARCH"
multimedia/HandBrake/HandBrake.hint:PRAGMA="unset_ARCH"
network/RSSOwl/RSSOwl.hint:PRAGMA="unset_ARCH"
network/broadcom-sta/broadcom-sta.hint:PRAGMA="kernelmodule unset_ARCH"
network/btsync/btsync.hint:PRAGMA="unset_ARCH"
network/davmail/davmail.hint:PRAGMA="unset_ARCH"
network/hipchat/hipchat.hint:PRAGMA="unset_ARCH"
network/megasync/megasync.hint:PRAGMA="unset_ARCH"
network/netsurf/netsurf.hint:PRAGMA="noexport_BUILD"
network/nxclient/nxclient.hint:PRAGMA="unset_ARCH"
network/opera/opera.hint:PRAGMA="unset_ARCH"
network/palemoon/palemoon.hint:PRAGMA="unset_ARCH"
network/r8168/r8168.hint:PRAGMA="kernelmodule unset_ARCH"
network/rtl8188eu/rtl8188eu.hint:PRAGMA="kernelmodule unset_ARCH"
network/syncthing/syncthing.hint:PRAGMA="unset_ARCH"
network/teamviewer/teamviewer.hint:PRAGMA="unset_ARCH"
network/wuala/wuala.hint:PRAGMA="unset_ARCH"
network/xtables-addons/xtables-addons.hint:PRAGMA="kernelmodule unset_ARCH"
office/LibreOffice/LibreOffice.hint:PRAGMA="unset_ARCH unset_DISPLAY"
python/pypy/pypy.hint:PRAGMA="unset_ARCH"
python/pypy3/pypy3.hint:PRAGMA="unset_ARCH"
system/crashplan/crashplan.hint:PRAGMA="unset_ARCH"
system/csh/csh.hint:PRAGMA="noexport_BUILD"
system/lirc/lirc.hint:PRAGMA="kernel unset_ARCH"
system/netatop/netatop.hint:PRAGMA="kernelmodule unset_ARCH"
system/refind/refind.hint:PRAGMA="unset_ARCH"
system/samsung-mfp-drivers/samsung-mfp-drivers.hint:PRAGMA="unset_ARCH"
system/spl-solaris/spl-solaris.hint:PRAGMA="kernelmodule unset_ARCH"
system/steamos-xpad/steamos-xpad.hint:PRAGMA="kernelmodule unset_ARCH"
system/sysdig/sysdig.hint:PRAGMA="kernelmodule unset_ARCH"
system/tracker/tracker.hint:PRAGMA="noexport_BUILD"
system/vhba-module/vhba-module.hint:PRAGMA="kernelmodule unset_ARCH"
system/xen/xen.hint:PRAGMA="stubs-32 unset_ARCH"
system/zfs-on-linux/zfs-on-linux.hint:PRAGMA="kernelmodule unset_ARCH"
___
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] Exported ARCH causing libraries/hiredis build failure

[B Watson]

On 8/7/17, David Spencer  wrote:

>> at this time.  I just submitted a fix that adds ARCH="" to the make line,
>> which seems to fix the problem.
>
> I *would* have asked about this years ago, but (1) afaik nobody else
> has found this problem until now, and (2) I hadn't thought of your fix
> ;-)

I had to add ARCH="" to the make commands in eduke32.SlackBuild ages ago.

> Do people think it's worth fixing this in the whole repo?

Definitely. What's the list of builds you have hints for in slackrepo?
___
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] Exported ARCH causing libraries/hiredis build failure

[Andreas Guldstrand]

On 7 August 2017 at 19:57, David Spencer
 wrote:
> Do people think it's worth fixing this in the whole repo?

Definitely! :)

Less gotchas when building can only be a good thing imo
___
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] Exported ARCH causing libraries/hiredis build failure

[David Spencer]

> A user reported a build failure that was likely caused by having ARCH=x86_64
> exported in the environment.  This may be due to sbopkg, which I don't use
> at this time.  I just submitted a fix that adds ARCH="" to the make line,
> which seems to fix the problem.

Heh!  slackrepo has hints to cope with this problem in multiple
SlackBuilds, but your fix is much better than my fix :D

There are also 9 more SlackBuilds that don't like exported BUILD and
one that doesn't like exported TAG

I *would* have asked about this years ago, but (1) afaik nobody else
has found this problem until now, and (2) I hadn't thought of your fix
;-)

Do people think it's worth fixing this in the whole repo?

Thanks Kent
-D.
___
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] Scribus-1.4.6: build fails not finding freetype.h

[Rich Shepard]

On Mon, 7 Aug 2017, Andreas Guldstrand wrote:


The line before the line you added needs to end in a \ as well


  Fixed that. Now, back to the previous error:

In file included from
/tmp/SBo/scribus-1.4.6/scribus/desaxe/saxiohelper.cpp:10:0:
/tmp/SBo/scribus-1.4.6/scribus/scfonts.h:19:23: fatal error: freetype.h: No
such file or directory
 #include FT_FREETYPE_H
   ^
compilation terminated.
make[2]: ***
[scribus/desaxe/CMakeFiles/scribus_desaxe_lib.dir/saxiohelper.cpp.o] Error 1
make[2]: Leaving directory /tmp/SBo/scribus-1.4.6'
make[1]: *** [scribus/desaxe/CMakeFiles/scribus_desaxe_lib.dir/all] Error 2
make[1]: Leaving directory /tmp/SBo/scribus-1.4.6'
make: *** [all] Error 2

  For some reason not worth pursuing any longer (since scribus builds and
works with freetype-2.6.3), it just won't build with freetype-2.5.5 on this
host.

Rich
___
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] Scribus-1.4.6: build fails not finding freetype.h

[Rich Shepard]

On Mon, 7 Aug 2017, Andreas Guldstrand wrote:


The line before the line you added needs to end in a \ as well


  Aw, foo! Mea culpa; I should have seen that.

Rich
___
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] Scribus-1.4.6: build fails not finding freetype.h

[Andreas Guldstrand]

On 7 August 2017 at 19:22, Rich Shepard  wrote:
> cmake \
>   -DCMAKE_C_FLAGS="$SLKCFLAGS" \
>   -DCMAKE_CXX_FLAGS="$SLKCFLAGS" \
>   -DCMAKE_INSTALL_PREFIX:PATH=/usr \
>   -DLIB_SUFFIX=${LIBDIRSUFFIX} \
>   -DRENDER_LIB=CAIRO
>   -D FREETYPE_INCLUDE_DIRS:PATH="/usr/include/freetype2" \
>   ./CMakeLists.txt

The line before the line you added needs to end in a \ as well
___
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] Scribus-1.4.6: build fails not finding freetype.h

[Rich Shepard]

On Mon, 7 Aug 2017, Sebastien BALLET wrote:


It complains because you forgot to add "./CMakeLists.txt" after "-D
=". Here is what you need to add after "-DRENDER_LIB=CAIRO \".

8<--
 *-D FREETYPE_INCLUDE_DIRS:PATH="/u*

*sr/include/freetype2" \  ./CMakeLists.txt *8<
--


Sebastien,

  Actually, I copied this:


 -D FREETYPE_INCLUDE_DIRS:PATH="/usr/include/freetype2" \
 ./CMakeLists.txt


from your message into scribus.SlackBuild.

  With freetype-2.5.5-i486-2_slack14.1.txz installed, and the cmake portion
of the build script containing:

cmake \
  -DCMAKE_C_FLAGS="$SLKCFLAGS" \
  -DCMAKE_CXX_FLAGS="$SLKCFLAGS" \
  -DCMAKE_INSTALL_PREFIX:PATH=/usr \
  -DLIB_SUFFIX=${LIBDIRSUFFIX} \
  -DRENDER_LIB=CAIRO
  -D FREETYPE_INCLUDE_DIRS:PATH="/usr/include/freetype2" \
  ./CMakeLists.txt

  I run the script:

# VERBOSE=1 ./scribus.SlackBuild

and see this:

-- Configuring done
-- Generating done
-- Build files have been written to: /tmp/SBo/scribus-1.4.6
./scribus.SlackBuild: line 82: -D: command not found

Rich

___
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] Scribus-1.4.6: build fails not finding freetype.h

[Sebastien BALLET]

Hello,

It complains because you forgot to add "./CMakeLists.txt" after "-D
=". Here is what you need to add after "-DRENDER_LIB=CAIRO \".

8<--
  *-D FREETYPE_INCLUDE_DIRS:PATH="/u*

*sr/include/freetype2" \  ./CMakeLists.txt *8<
--

--
SeB

2017-08-07 18:49 GMT+02:00 Rich Shepard :

> On Mon, 7 Aug 2017, Sebastien BALLET wrote:
>
> You shouldn't have removed that space. It is required. The option -D allows
>> to create a cmake cache entry :
>>
>
> Sebastien,
>
>   When I left it in, the build complained it could not find a '-D '; that's
> why I removed the space.
>
> Rich
> ___
> 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 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] Scribus-1.4.6: build fails not finding freetype.h

[Rich Shepard]

On Mon, 7 Aug 2017, Sebastien BALLET wrote:


You shouldn't have removed that space. It is required. The option -D allows
to create a cmake cache entry :


Sebastien,

  When I left it in, the build complained it could not find a '-D '; that's
why I removed the space.

Rich
___
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] Scribus-1.4.6: build fails not finding freetype.h

[Sebastien BALLET]

Hello,

You shouldn't have removed that space. It is required. The option -D allows
to create a cmake cache entry :

$ man cmake
...
 -D :=, -D =
  Create a cmake cache entry.

  When cmake is first run in an empty build tree, it  creates
a  CMakeCache.txt
  file and populates it with customizable settings for the
project.  This option
  may be used to specify a  setting  that  takes  priority
over  the  project's
  default  value.   The  option  may  be  repeated  for as many
cache entries as
  desired.

-- 
SeB


2017-08-07 17:59 GMT+02:00 Rich Shepard :

> On Mon, 7 Aug 2017, Sebastien BALLET wrote:
>
> That's really weird. It would be better to find why cmake finds freetype
>> /in usr/local/include instead of /usr/include, but, you can try this hack:
>> Edit scribus.SlackBuild, then, modify the cmake block (starting at line
>> #76) as below (changes are in bold) :
>>
>> 8<--
>> cmake \
>>  -DCMAKE_C_FLAGS="$SLKCFLAGS" \
>>  -DCMAKE_CXX_FLAGS="$SLKCFLAGS" \
>>  -DCMAKE_INSTALL_PREFIX:PATH=/usr \
>>  -DLIB_SUFFIX=${LIBDIRSUFFIX} \
>>  -DRENDER_LIB=CAIRO \
>>  -D FREETYPE_INCLUDE_DIRS:PATH="/usr/include/freetype2" \
>>  ./CMakeLists.txt
>> 8<--
>>
>
> Sebastian,
>
>   Yes, it would be nice to learn why cmake finds freetype in
> /usr/local/include/ when it's actually in /usr/include/.
>
>   I deleted the space between -D and FREETYPE... above and with
> freetype-2.5.5 installed this error is produced:
>
> -- Configuring done
> -- Generating done
> -- Build files have been written to: /tmp/SBo/scribus-1.4.6
> ./scribus.SlackBuild: line 83:
> -DFREETYPE_INCLUDE_DIRS:PATH=/usr/include/freetype2: No such file or
> directory
>
>   /usr/include/ has freetype2/ with all the expected files, and freetype/
> with this softlink:
> lrwxrwxrwx 1 root root 9 Aug  7 08:45 /usr/include/freetype -> freetype2/
> which was apparently generated when I tried the above build.
>
>   For completeness, using freetype--2.6.3-i586-1, scribus-1.4.6 builds.
>
>   Summary: On my system, scribus-1.4.6 builds with freetype-2.5.0 and
> -2.6.3, but not 2.5.5. Figuring out why is well beyond my experience.
>
> Thanks again,
>
> Rich
>
> ___
> 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 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] Scribus-1.4.6: build fails not finding freetype.h

[Rich Shepard]

On Mon, 7 Aug 2017, Sebastien BALLET wrote:


That's really weird. It would be better to find why cmake finds freetype
/in usr/local/include instead of /usr/include, but, you can try this hack:
Edit scribus.SlackBuild, then, modify the cmake block (starting at line
#76) as below (changes are in bold) :

8<--
cmake \
 -DCMAKE_C_FLAGS="$SLKCFLAGS" \
 -DCMAKE_CXX_FLAGS="$SLKCFLAGS" \
 -DCMAKE_INSTALL_PREFIX:PATH=/usr \
 -DLIB_SUFFIX=${LIBDIRSUFFIX} \
 -DRENDER_LIB=CAIRO \
 -D FREETYPE_INCLUDE_DIRS:PATH="/usr/include/freetype2" \
 ./CMakeLists.txt
8<--


Sebastian,

  Yes, it would be nice to learn why cmake finds freetype in
/usr/local/include/ when it's actually in /usr/include/.

  I deleted the space between -D and FREETYPE... above and with
freetype-2.5.5 installed this error is produced:

-- Configuring done
-- Generating done
-- Build files have been written to: /tmp/SBo/scribus-1.4.6
./scribus.SlackBuild: line 83:
-DFREETYPE_INCLUDE_DIRS:PATH=/usr/include/freetype2: No such file or
directory

  /usr/include/ has freetype2/ with all the expected files, and freetype/
with this softlink:
lrwxrwxrwx 1 root root 9 Aug  7 08:45 /usr/include/freetype -> freetype2/
which was apparently generated when I tried the above build.

  For completeness, using freetype--2.6.3-i586-1, scribus-1.4.6 builds.

  Summary: On my system, scribus-1.4.6 builds with freetype-2.5.0 and
-2.6.3, but not 2.5.5. Figuring out why is well beyond my experience.

Thanks again,

Rich

___
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] [slackbuilds-users] sage-8.0 OPTIONALSPKG fails to find optional packages

[King Beowulf]

On 08/07/2017 01:24 AM, Willy Sudiarto Raharjo wrote:
>> Sage is in 'pending' and I had thought that the previous maintainer had
>> worked this out.  My script-fu is still young so comments are welcome.
> 
> TBH, i never check the optional deps.
> I kept what was inherited from the original maintainer as building sage
> itself was time consuming already
> 
> 

Indeed.  I takes over 2.5 hrs to build on my box (time for an upgrade?).
 Since no one else has mentioned this issue, I'll send in a fix on the
next submission, as well as a few minor README updates.  No rush.

-Ed



signature.asc
Description: OpenPGP digital signature
___
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] Scribus-1.4.6: build fails not finding freetype.h [SOLVED]

[Sebastien BALLET]

Hello,

Nice that you found a solution for this weird issue Rich.

-- 
SeB

2017-08-07 16:35 GMT+02:00 Rich Shepard :

> On Fri, 4 Aug 2017, Rich Shepard wrote:
>
>  I'm trying to upgrade scribus from 1.4.4. to 1.4.6, but the build fails
>> here:
>> /tmp/SBo/scribus-1.4.6/scribus/scfonts.h:19:23: fatal error: freetype.h:
>> No
>> / such file or directory
>>
>
> Didier/Sebastien:
>
>   I found the problem and a solution to it. For some reason, the patched
> freetype-2.5.5 fails, but the original freetype-2.5.0 works. Now, why that
> should be the case here and not on Sebastian's virtual 14.1/x86_i586 I've
> no
> idea.
>
>   I downloaded the SlackBuilds source for freetype-4.6.3 from the 14.2
> repoaistory at osuosl.org. I'll build that and see how scribus reacts.
>
> Thanks again,
>
> Rich
> ___
> 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 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] Scribus-1.4.6: build fails not finding freetype.h

[Sebastien BALLET]

Hello,

That's really weird. It would be better to find why cmake find freetype in
/usr/local/include instead of /usr/include, but, you can try this hack:
Edit scribus.SlackBuild, then, modify the cmake block (starting at line
#76) as below (changes are in bold) :

8<--
cmake \
  -DCMAKE_C_FLAGS="$SLKCFLAGS" \
  -DCMAKE_CXX_FLAGS="$SLKCFLAGS" \
  -DCMAKE_INSTALL_PREFIX:PATH=/usr \
  -DLIB_SUFFIX=${LIBDIRSUFFIX} \
  -DRENDER_LIB=CAIRO \
  -D FREETYPE_INCLUDE_DIRS:PATH="/usr/include/freetype2" \
  ./CMakeLists.txt
8<--

Then, try to build scribus as below and post the output (unless it not
fails).

$ VERBOSE=1 ./scribus.SlackBuild

-- 
SeB

2017-08-07 15:32 GMT+02:00 Rich Shepard :

> On Mon, 7 Aug 2017, Sebastien BALLET wrote:
>
> In one of my previous post, I ask you to create the file
>> /tmp/cmake-test/CMakeLists.txt
>> with the content below :
>>
>
> Sebastien,
>
> If you have deleted it, recreate it. Otherwise, run the commands below :
>> $ cd /tmp/cmake-test
>> $ rm CMakeCache.txt
>>
>
>   Done.
>
> Remove freetype package :
>> $ removepkg freetype
>>
>
>   Done
>
> In /tmp/cmake-test, run the command below :
>> $ cmake .
>>
>> You should get this :
>>
>> 8<--
>> $ cmake .
>>
>> -- Could NOT find Freetype (missing FREETYPE_LIBRARY
>> FREETYPE_INCLUDE_DIRS)
>> freetype_include_dirs:
>> -- Configuring done
>> -- Generating done
>> -- Build files have been written to: /tmp/cmake-test
>> 8<--
>>
>
> If freetype_include_dirs is not *empty* (which I doubt), check the returned
>> directories content.
>>
>
>   I see the same results and assume the freetype_include_dirs is empty.
>
> Now, install freetype, with slackpkg or any other tools...
>> Then, in /tmp/cmake-test, run the commands below :
>> $ rm CMakeCache.txt
>> $ cmake .
>> You should get this :
>> 8<--
>> -- Found Freetype: /usr/lib/libfreetype.so (found version "2.5.5")
>> freetype_include_dirs: /usr/include/freetype2;/usr/include
>> -- Configuring done
>> -- Generating done
>> -- Build files have been written to: /tmp/cmake-test
>> 8<--
>>
>
>   Yes.
>
> ​If you get the output above, you can (re)try to build scribus. Otherwise
>> ... I don't know.
>>
>
>   Sigh. Same error. Later today I'll try the original freetype-2.5.5 rather
> than this past March's patch.
>
> Thanks, Sebastien, I'm as puzzled and frustrated as you are,
>
> Rich
> ___
> 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 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] Scribus-1.4.6: build fails not finding freetype.h [SOLVED]

[Rich Shepard]

On Fri, 4 Aug 2017, Rich Shepard wrote:


 I'm trying to upgrade scribus from 1.4.4. to 1.4.6, but the build fails
here:
/tmp/SBo/scribus-1.4.6/scribus/scfonts.h:19:23: fatal error: freetype.h: No
/ such file or directory


Didier/Sebastien:

  I found the problem and a solution to it. For some reason, the patched
freetype-2.5.5 fails, but the original freetype-2.5.0 works. Now, why that
should be the case here and not on Sebastian's virtual 14.1/x86_i586 I've no
idea.

  I downloaded the SlackBuilds source for freetype-4.6.3 from the 14.2
repoaistory at osuosl.org. I'll build that and see how scribus reacts.

Thanks again,

Rich
___
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] Exported ARCH causing libraries/hiredis build failure

[Kent Fritz]

A user reported a build failure that was likely caused by having
ARCH=x86_64 exported in the environment.  This may be due to sbopkg, which
I don't use at this time.  I just submitted a fix that adds ARCH="" to the
make line, which seems to fix the problem.

If that's not the right fix, let me know.

Kent.
___
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] Scribus-1.4.6: build fails not finding freetype.h

[Rich Shepard]

On Mon, 7 Aug 2017, Sebastien BALLET wrote:


In one of my previous post, I ask you to create the file
/tmp/cmake-test/CMakeLists.txt
with the content below :


Sebastien,


If you have deleted it, recreate it. Otherwise, run the commands below :
$ cd /tmp/cmake-test
$ rm CMakeCache.txt


  Done.


Remove freetype package :
$ removepkg freetype


  Done


In /tmp/cmake-test, run the command below :
$ cmake .

You should get this :

8<--
$ cmake .

-- Could NOT find Freetype (missing FREETYPE_LIBRARY FREETYPE_INCLUDE_DIRS)
freetype_include_dirs:
-- Configuring done
-- Generating done
-- Build files have been written to: /tmp/cmake-test
8<--



If freetype_include_dirs is not *empty* (which I doubt), check the returned
directories content.


  I see the same results and assume the freetype_include_dirs is empty.


Now, install freetype, with slackpkg or any other tools...
Then, in /tmp/cmake-test, run the commands below :
$ rm CMakeCache.txt
$ cmake .
You should get this :
8<--
-- Found Freetype: /usr/lib/libfreetype.so (found version "2.5.5")
freetype_include_dirs: /usr/include/freetype2;/usr/include
-- Configuring done
-- Generating done
-- Build files have been written to: /tmp/cmake-test
8<--


  Yes.


​If you get the output above, you can (re)try to build scribus. Otherwise
... I don't know.


  Sigh. Same error. Later today I'll try the original freetype-2.5.5 rather
than this past March's patch.

Thanks, Sebastien, I'm as puzzled and frustrated as you are,

Rich
___
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] [slackbuilds-users] sage-8.0 OPTIONALSPKG fails to find optional packages

[Willy Sudiarto Raharjo]

> Sage is in 'pending' and I had thought that the previous maintainer had
> worked this out.  My script-fu is still young so comments are welcome.

TBH, i never check the optional deps.
I kept what was inherited from the original maintainer as building sage
itself was time consuming already



-- 
Willy Sudiarto Raharjo



signature.asc
Description: OpenPGP digital signature
___
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] Scribus-1.4.6: build fails not finding freetype.h

[Sebastien BALLET]

​​
​Hello,

In one of my previous post, I ask you to create the file
/tmp/cmake-test/CMakeLists.txt
with the content below :

8<---/tmp/cmake-test/CMakeLists.txt --
cmake_minimum_required(VERSION 2.8)
find_package(Freetype)
if (FREETYPE_FOUND)
  include_directories(${FREETYPE_INCLUDE_DIRS})
endif (FREETYPE_FOUND)

MESSAGE("freetype_include_dirs: ${FREETYPE_INCLUDE_DIRS}")
8<--

If you have deleted it, recreate it. Otherwise, run the commands below :

$ cd /tmp/cmake-test
$ rm CMakeCache.txt

Remove freetype package :

$ removepkg freetype

In /tmp/cmake-test, run the command below :

$ cmake .

You should get this :

8<--
$ cmake .

-- Could NOT find Freetype (missing FREETYPE_LIBRARY FREETYPE_INCLUDE_DIRS)
freetype_include_dirs:
-- Configuring done
-- Generating done
-- Build files have been written to: /tmp/cmake-test
8<--

If freetype_include_dirs is not *empty* (which I doubt), check the returned
directories content.

Now, install freetype, with slackpkg or any other tools...

$ slackpkg install freetype

Then, in /tmp/cmake-test, run the commands below :

$ rm CMakeCache.txt
$ cmake .

You should get this :

8<--
-- Found Freetype: /usr/lib/libfreetype.so (found version "2.5.5")
freetype_include_dirs: /usr/include/freetype2;/usr/include
-- Configuring done
-- Generating done
-- Build files have been written to: /tmp/cmake-test
8<--

​If you get the output above, you can (re)try to build scribus. Otherwise
... I don't know.

-- 
SeB​


2017-08-06 18:22 GMT+02:00 Rich Shepard :

> On Sun, 6 Aug 2017, Sebastien BALLET wrote:
>
> can you post the output of commands below :
>>
>> $ find /usr/include -iname "ft2build.h"
>>
>
> /usr/include/freetype2/ft2build.h
>
> $ cat /usr/lib/pkgconfig/freetype2.pc | grep "includedir"
>>
>
> includedir=/usr/include/freetype2
> Cflags: -I${includedir}
>
> $ ls -l /var/log/packages/freetype*
>>
>
> -rw-r--r-- 1 root root 3544 May 16 17:20
> - /var/log/packages/freetype-2.5.5-i486-2_slack14.1
>
> $ cat /var/log/packages/freetype-* | grep -E "ft2build.h|freetype.h"
>>
>
> usr/include/freetype2/ft2build.h
> usr/include/freetype2/freetype.h
>
>   Wonder where the /usr/local/include came from.
>
> Rich
> ___
> 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 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] transmission current broken.

[Jeremy Hansen]

On Mon, Aug 7, 2017 at 2:09 AM, Fernando Lopez 
wrote:

> i did,... however just posting to linuxquestions... hmm...
>

The point Matteo is trying to make is that SBo does not offer any support
for building on -current. That includes providing support on the official
mailing list on issues when you're attempting to build software on -current
using SlackBuilds from SBo.. Matteo has an *unofficial* repo available that
should allow building software on -current, but if you have issues, he asks
that you report it on that thread in the LQ forum. Continuing to request
assistance for SlackBuilds on -current on this mailing list will likely
lead to a lot of frustrated people and admins, so it is best to report any
issues you find in that thread rather than on this mailing list.

Jeremy
___
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] transmission current broken.

[Fernando Lopez]

i did,... however just posting to linuxquestions... hmm...


On Sun, Aug 6, 2017 at 11:15 PM, Matteo Bernardini <
matteo.bernard...@gmail.com> wrote:

> 2017-08-07 7:07 GMT+02:00 Fernando Lopez :
> > sorry. hehehe.. who do i report broken packages to then on current?
>
> I linked you in my previous answer
>
> https://www.linuxquestions.org/questions/slackware-14/
> sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/
>
> be sure to read *carefully* the first post of that thread before posting
> in it.
>
> if you would like people to take time to read and understand your
> questions, should be nice you take the same time to read and
> understand their answers...
> ___
> 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/
>
>


-- 


Regards,
Fernando Lopez Jr.
___
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/