LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 10-06-2018, 01:18 PM   #2266
USUARIONUEVO
Senior Member
 
Registered: Apr 2015
Posts: 2,336

Rep: Reputation: 930Reputation: 930Reputation: 930Reputation: 930Reputation: 930Reputation: 930Reputation: 930Reputation: 930

gutenprint-5.3.1
https://sourceforge.net/projects/gim...t-5.3.1.tar.xz
 
1 members found this post helpful.
Old 10-06-2018, 02:20 PM   #2267
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 2,511

Rep: Reputation: 8475Reputation: 8475Reputation: 8475Reputation: 8475Reputation: 8475Reputation: 8475Reputation: 8475Reputation: 8475Reputation: 8475Reputation: 8475Reputation: 8475
Quote:
Originally Posted by SCerovec View Post
in UEFI only computers, like my laptop, regular memtest86 won't work at all - new EFI only memtest is needed not sure what license applies for Slackware?
What we include is memtest86+, which is GPL licensed. The version you're linking to, plain old "memtest86", is not open source and it's unclear if "free without restrictions" means that it's freely redistributable. In any case, since source code isn't available we're unlikely to ship it.

Are you sure that your computer is really "UEFI only"? All the ones I've seen support a legacy/CSM boot mode which would allow the 16-bit memtest86+ to run.
 
Old 10-06-2018, 03:24 PM   #2268
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 2,472
Blog Entries: 2

Rep: Reputation: 980Reputation: 980Reputation: 980Reputation: 980Reputation: 980Reputation: 980Reputation: 980Reputation: 980
Thumbs up

Quote:
Originally Posted by volkerdi View Post
What we include is memtest86+, which is GPL licensed. The version you're linking to, plain old "memtest86", is not open source and it's unclear if "free without restrictions" means that it's freely redistributable. In any case, since source code isn't available we're unlikely to ship it.

Are you sure that your computer is really "UEFI only"? All the ones I've seen support a legacy/CSM boot mode which would allow the 16-bit memtest86+ to run.
Sadly, sir, this is, apparently, one of those dreaded *legacy free* UEFI only laptops:

Fujitsu LifeBook T901.

Whatever gets shipped, I just note that said memtest86+, which works perfectly fine with even never (Z77) chip-sets won't on this one (QM67); that is not only older, but also limited (by BIOS/EFI firmware) to only support generation 2 CPUs.

This alone is due to the EFI lock-down and the inability to boot in legacy mode.

The decision is, as always, on the team, I'm just reporting - a rare beast here.

If I can help, I will gladly run what ever and send feedback as time permits (24h-48h response usually).
 
1 members found this post helpful.
Old 10-06-2018, 08:54 PM   #2269
ivandi
Member
 
Registered: Jul 2009
Location: Québec, Canada
Distribution: CRUX, Debian
Posts: 528

Rep: Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866Reputation: 866
The installer

Getting rid of the huge kernel.

The latest testing netinstall.iso uses the generic kernel. It still shows huge.s, but the image is vmlinuz-generic. I used this script to copy the needed modules and firmware to the initrd. Generic kernel, initrd, grub. Tested in UEFI VM with LUKS LVM.


Cheers
 
3 members found this post helpful.
Old 10-06-2018, 08:55 PM   #2270
USUARIONUEVO
Senior Member
 
Registered: Apr 2015
Posts: 2,336

Rep: Reputation: 930Reputation: 930Reputation: 930Reputation: 930Reputation: 930Reputation: 930Reputation: 930Reputation: 930
python-pillow-5.3.0
https://github.com/python-pillow/Pil...e/5.3.0.tar.gz
 
Old 10-07-2018, 03:53 AM   #2271
gmgf
Senior Member
 
Registered: Jun 2012
Location: Bergerac, France
Distribution: Slackware
Posts: 2,217

Rep: Reputation: 1006Reputation: 1006Reputation: 1006Reputation: 1006Reputation: 1006Reputation: 1006Reputation: 1006Reputation: 1006
gnuplot-5.2.5:

http://www.gnuplot.info/ReleaseNotes_5_2_5.html
https://sourceforge.net/projects/gnu...gnuplot/5.2.5/
 
1 members found this post helpful.
Old 10-07-2018, 06:41 AM   #2272
SCerovec
Senior Member
 
Registered: Oct 2006
Location: Cp6uja
Distribution: Slackware on x86 and arm
Posts: 2,472
Blog Entries: 2

Rep: Reputation: 980Reputation: 980Reputation: 980Reputation: 980Reputation: 980Reputation: 980Reputation: 980Reputation: 980
Quote:
Originally Posted by ivandi View Post
Getting rid of the huge kernel.

The latest testing netinstall.iso uses the generic kernel. It still shows huge.s, but the image is vmlinuz-generic. I used this script to copy the needed modules and firmware to the initrd. Generic kernel, initrd, grub. Tested in UEFI VM with LUKS LVM.


Cheers
great news @ivandi!
 
Old 10-07-2018, 06:43 AM   #2273
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792

Rep: Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656
Is anyone able to set a nickname for their wireless device?

I consistently see the following error whenever I connect my wireless device through /etc/rc.d/rc.inet1 (I don't use Network Manager).

Code:
Error for wireless request "Set Nickname" (8B1C) :
    SET failed on device wlan0 ; Operation not supported.
I don't remember a time when I haven't seen this error, so I wonder if it is not supported by most cards nowadays.

Considering the nickname is not vital for connecting to wireless networks, and this provides a worthless error message (especially when people unfamiliar with manually configuring their networks see the message and think it is related to problems they're having), can we remove the commands from /etc/rc.d/rc.wireless? Or we could only run the commands if NICKNAME was set from /etc/rc.d/rc.inet1.conf. This would allow anyone still wanting to use the nickname to still use it and it would get rid of the message for everyone else.

Looking at rc.wireless, I'm wondering if nickname is more useful using the "MODE" option, so the below checks if NICKNAME is empty and if MODE is non-empty, and if so, it sets NICKNAME to /bin/hostname. Then the if statement running the actual command is changed from checking if ESSID is set to if NICKNAME is set (and the second check for mode is removed since it is redundant -- if nickname is set, the command will be run... if it isn't set and MODE is set, then NICKNAME will get /bin/hostname and the command will be run).

Code:
diff --git a/scripts/rc.wireless b/scripts/rc.wireless
index e7a35b8..7e75c68 100644
--- a/scripts/rc.wireless
+++ b/scripts/rc.wireless
@@ -196,10 +196,10 @@ if [ -n "$MODE" ] ; then
         fi
 fi
 # This is a bit hackish, but should do the job right...
-if [ ! -n "$NICKNAME" ] ; then
+if [ ! -n "$NICKNAME" -a -n "$MODE" ] ; then
     NICKNAME=$(/bin/hostname)
 fi
-if [ -n "$ESSID" -o -n "$MODE" ] ; then
+if [ -n "$NICKNAME" ] ; then
        echo "$0:  $IWCOMMAND nick $NICKNAME" | $LOGGER
        $IWCOMMAND nick $NICKNAME
 fi
I'd certainly be interested in usage of the nickname command... google searches really only turn up people trying to diagnose wireless problems and that error message always pops up.
 
Old 10-07-2018, 08:33 AM   #2274
average_user
Member
 
Registered: Dec 2010
Location: Warsaw, Poland
Distribution: Slackware
Posts: 560

Rep: Reputation: 220Reputation: 220Reputation: 220
Quote:
Originally Posted by bassmadrigal View Post
Is anyone able to set a nickname for their wireless device?

I consistently see the following error whenever I connect my wireless device through /etc/rc.d/rc.inet1 (I don't use Network Manager).

Code:
Error for wireless request "Set Nickname" (8B1C) :
    SET failed on device wlan0 ; Operation not supported.
I don't remember a time when I haven't seen this error, so I wonder if it is not supported by most cards nowadays.
I've come across several devices that had nickname hardcoded to something, for example '<WIFI@REALTEK>' and it's implemented using SIOCGIWNICKN ioctl. However, it wasn't possible to change nickname and a quick look at Linux source shows that there are only a couple of drivers that implement SIOCSIWNICKN for setting nickname.
 
Old 10-07-2018, 08:34 AM   #2275
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware64-15.0
Posts: 6,374

Rep: Reputation: 2754Reputation: 2754Reputation: 2754Reputation: 2754Reputation: 2754Reputation: 2754Reputation: 2754Reputation: 2754Reputation: 2754Reputation: 2754Reputation: 2754
Quote:
Originally Posted by ivandi View Post
Getting rid of the huge kernel.

The latest testing netinstall.iso uses the generic kernel. It still shows huge.s, but the image is vmlinuz-generic. I used this script to copy the needed modules and firmware to the initrd. Generic kernel, initrd, grub. Tested in UEFI VM with LUKS LVM.


Cheers
I like this and support goes all the way to the top.
The implications for satisfying the "I use the huge kernel because it just works" user base and how updates should be handled also need to be considered.
 
1 members found this post helpful.
Old 10-07-2018, 09:30 PM   #2276
Xsane
Member
 
Registered: Jan 2014
Posts: 186

Rep: Reputation: 134Reputation: 134
Is there a reason that 'removepkg --preserve' saves the old package to a path that is clobbered upon reboot? Doesn't seem very 'preserved' to me.

If that is intentional then, IMO, admins need to be warned about it in the removepkg man page.

Yes, I got caught by it. I needed a backup of a package I was removing and the next day it was gone, doh!
 
2 members found this post helpful.
Old 10-07-2018, 09:56 PM   #2277
Xsane
Member
 
Registered: Jan 2014
Posts: 186

Rep: Reputation: 134Reputation: 134
Could packages in 'extra' have a tag to distinguish them from default
installation packages?

For example, instead of: fltk-1.3.4_2-x86_64-2.txz
Could it be something like: fltk-1.3.4_2-x86_64-2_extra.txz

I have a script that checks the integrity of my installs and one of the things
it does is list non-default packages; most of which have a tag like _SBo,
alien, or my own tag. IMO, it would be helpful for any installed 'extra'
packages to be tagged as well.
 
2 members found this post helpful.
Old 10-08-2018, 01:10 PM   #2278
dugan
LQ Guru
 
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 11,235

Rep: Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320
Here's an update to the vulkan-sdk 11.82.0 SlackBuild update I contributed here:

https://www.linuxquestions.org/quest...ml#post5898816

It now builds 11.85.0.

fetch-sources.sh is updated:

Code:
#!/bin/sh

# Copyright 2017  Patrick J. Volkerding, Sebeka, Minnesota, USA
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
#    notice, this list of conditions and the following disclaimer.
#
#  THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED
#  WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
#  MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO
#  EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
#  SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
#  PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
#  OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
#  WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
#  OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
#  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

# Call this script with the version of the Vulkan-LoaderAndValidationLayers-sdk
# that you would like to fetch the sources for. This will fetch the SDK from
# github, and then look at the revisions listed in the external_revisions
# directory to fetch the proper glslang, SPIRV-Headers, and SPIRV-Tools.
#
# Example:  VERSION=1.1.85.0 ./fetch-sources.sh

VERSION=${VERSION:-1.1.85.0}
BRANCH=${BRANCH:-sdk-1.1.85}

rm -rf Vulkan-*-*.tar.gz glslang* SPIRV-Tools* SPIRV-Headers* \
	Vulkan-Headers-sdk-"$VERSION"* \
	Vulkan-ValidationLayers-sdk-"$VERSION"* \
	Vulkan-Loader-sdk-"$VERSION"* \
	Vulkan-Tools-sdk-"$VERSION"*


git clone -b "$BRANCH" --single-branch https://github.com/KhronosGroup/Vulkan-Headers.git Vulkan-Headers-sdk-"$VERSION"
rm -rf Vulkan-Headers-sdk-"$VERSION"/.git
tar -cvvf Vulkan-Headers-sdk-"$VERSION".tar.gz Vulkan-Headers-sdk-"$VERSION"
rm -rf Vulkan-Headers-sdk-"$VERSION"

git clone -b "$BRANCH" --single-branch https://github.com/KhronosGroup/Vulkan-ValidationLayers.git Vulkan-ValidationLayers-sdk-"$VERSION"
rm -rf Vulkan-ValidationLayers-sdk-"$VERSION"/.git
tar -cvvf Vulkan-ValidationLayers-sdk-"$VERSION".tar.gz Vulkan-ValidationLayers-sdk-"$VERSION"
rm -rf Vulkan-ValidationLayers-sdk-"$VERSION"

git clone -b "$BRANCH" --single-branch https://github.com/KhronosGroup/Vulkan-Loader.git Vulkan-Loader-sdk-"$VERSION"
rm -rf Vulkan-Loader-sdk-"$VERSION"/.git
tar -cvvf Vulkan-Loader-sdk-"$VERSION".tar.gz Vulkan-Loader-sdk-"$VERSION"
rm -rf Vulkan-Loader-sdk-"$VERSION"

git clone -b "$BRANCH" --single-branch https://github.com/KhronosGroup/Vulkan-Tools.git Vulkan-Tools-sdk-"$VERSION"
rm -rf Vulkan-Tools-sdk-"$VERSION"/.git
tar -cvvf Vulkan-Tools-sdk-"$VERSION".tar.gz Vulkan-Tools-sdk-"$VERSION"
rm -rf Vulkan-Tools-sdk-"$VERSION"

GLSLANG_COMMIT=$(python3 - << EOF
import json
import tarfile
with tarfile.open('Vulkan-ValidationLayers-sdk-$VERSION.tar.gz') as layers:
	known_good = layers.extractfile('Vulkan-ValidationLayers-sdk-1.1.85.0/scripts/known_good.json')
	known_good_info = json.loads(known_good.read())
glslang = next(repo for repo in known_good_info['repos'] if repo['name'] == 'glslang')
print(glslang['commit'])
EOF
)

git clone https://github.com/KhronosGroup/glslang.git
cd glslang || exit
git checkout "$GLSLANG_COMMIT"
GLSLANG_VERSION=$(git rev-parse --short HEAD)
rm -rf .git
cd ..

mv glslang "glslang-$GLSLANG_VERSION"

SPIRV_TOOLS_COMMIT=$(python3 - << EOF
import json
with open('glslang-$GLSLANG_VERSION/known_good.json') as f:
	known_good = json.load(f)
tools = next(commit for commit in known_good['commits'] if commit['name'] == 'spirv-tools')
print(tools['commit'])
EOF
)

git clone https://github.com/KhronosGroup/SPIRV-Tools.git
cd SPIRV-Tools || exit
git checkout "$SPIRV_TOOLS_COMMIT"
SPIRV_TOOLS_VERSION="$(git rev-parse --short HEAD)"
rm -rf .git
cd - || exit
mv SPIRV-Tools "SPIRV-Tools-$SPIRV_TOOLS_VERSION"
tar -cvvf "SPIRV-Tools-$SPIRV_TOOLS_VERSION.tar" "SPIRV-Tools-$SPIRV_TOOLS_VERSION"
rm -rf "SPIRV-Tools-$SPIRV_TOOLS_VERSION"
plzip "SPIRV-Tools-$SPIRV_TOOLS_VERSION.tar"

SPIRV_HEADERS_COMMIT=$(python3 - << EOF
import json
with open('glslang-$GLSLANG_VERSION/known_good.json') as f:
	known_good = json.load(f)
name = 'spirv-tools/external/spirv-headers'
headers = next(commit for commit in known_good['commits'] if commit['name'] == name)
print(headers['commit'])
EOF
)

git clone https://github.com/KhronosGroup/SPIRV-Headers.git
cd SPIRV-Headers || exit
git checkout "$SPIRV_HEADERS_COMMIT"
SPIRV_HEADERS_VERSION="$(git rev-parse --short HEAD)"
rm -rf .git
cd - || exit
mv SPIRV-Headers "SPIRV-Headers-$SPIRV_HEADERS_VERSION"
tar -cvvf "SPIRV-Headers-$SPIRV_HEADERS_VERSION.tar" "SPIRV-Headers-$SPIRV_HEADERS_VERSION"
rm -rf "SPIRV-Headers-$SPIRV_HEADERS_VERSION"
plzip "SPIRV-Headers-$SPIRV_HEADERS_VERSION.tar"

tar -cvvf "glslang-$GLSLANG_VERSION.tar" "glslang-$GLSLANG_VERSION"
rm -rf "glslang-$GLSLANG_VERSION"
plzip "glslang-$GLSLANG_VERSION.tar"
And vulkan-sdk.SlackBuild is the same:

Code:
#!/bin/bash

# Slackware build script for vulkan-sdk

# Copyright 2016, 2017  Heinz Wiesinger, Amsterdam, The Netherlands
# Copyright 2016, 2017, 2018  Patrick J. Volkerding, Sebeka, MN, USA
# All rights reserved.
#
# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
#    notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

cd $(dirname $0) ; CWD=$(pwd)

PKGNAM=vulkan-sdk
VERSION=${VERSION:-$(echo Vulkan-ValidationLayers-sdk-*.tar.?z | rev | cut -f 3- -d . | cut -f 1 -d - | rev)}
BUILD=${BUILD:-1}

NUMJOBS=${NUMJOBS:--j7}

# Automatically determine the architecture we're building on:
MARCH=$( uname -m )
if [ -z "$ARCH" ]; then
  case "$MARCH" in
    i?86)    export ARCH=i586 ;;
    armv7hl) export ARCH=$MARCH ;;
    arm*)    export ARCH=arm ;;
    # Unless $ARCH is already set, use uname -m for all other archs:
    *)       export ARCH=$MARCH ;;
  esac
fi

# If the variable PRINT_PACKAGE_NAME is set, then this script will report what
# the name of the created package would be, and then exit. This information
# could be useful to other scripts.
if [ ! -z "${PRINT_PACKAGE_NAME}" ]; then
  echo "$PKGNAM-$VERSION-$ARCH-$BUILD.txz"
  exit 0
fi

if [ "$ARCH" = "i586" ]; then
  SLKCFLAGS="-O2 -march=i586 -mtune=i686"
  LIBDIRSUFFIX=""
elif [ "$ARCH" = "s390" ]; then
  SLKCFLAGS="-O2"
  LIBDIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
  SLKCFLAGS="-O2 -fPIC"
  LIBDIRSUFFIX="64"
elif [ "$ARCH" = "armv7hl" ]; then
  SLKCFLAGS="-O2 -march=armv7-a -mfpu=vfpv3-d16"
  LIBDIRSUFFIX=""
else
  SLKCFLAGS="-O2"
  LIBDIRSUFFIX=""
fi

TMP=${TMP:-/tmp}
PKG=$TMP/package-vulkan-sdk

GLSLANG_VERSION=$(echo glslang-*.tar.?z | rev | cut -f 3- -d . | cut -f 1 -d - | rev)
SPIRV_HEADERS_VERSION=$(echo SPIRV-Headers-sdk-*.tar.?z | rev | cut -f 3- -d . | cut -f 1 -d - | rev)
SPIRV_TOOLS_VERSION=$(echo SPIRV-Tools-*.tar.?z | rev | cut -f 3- -d . | cut -f 1 -d - | rev)

rm -rf $PKG
mkdir -p $TMP $PKG
cd $TMP
rm -rf Vulkan-ValidationLayers-sdk-$VERSION Vulkan-Headers-sdk-$VERSION glslang-$GLSLANG_VERSION

tar xvf $CWD/glslang-${GLSLANG_VERSION}.tar.?z || exit 1
cd glslang-$GLSLANG_VERSION/External
tar xvf $CWD/SPIRV-Tools-$SPIRV_TOOLS_VERSION.tar.lz
mv SPIRV-Tools-$SPIRV_TOOLS_VERSION spirv-tools
cd spirv-tools/external
tar xvf $CWD/SPIRV-Headers-$SPIRV_HEADERS_VERSION.tar.lz
mv SPIRV-Headers-$SPIRV_HEADERS_VERSION spirv-headers

cd $TMP/glslang-${GLSLANG_VERSION}

chown -R root:root .
find . \
  \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
  -exec chmod 755 {} \; -o \
  \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
  -exec chmod 644 {} \;

# Fix LIBDIRSUFFIX
for i in $(find . -name CMakeLists.txt); do
  sed -i "s|DESTINATION lib|DESTINATION \${CMAKE_INSTALL_LIBDIR}|" "$i"
done

mkdir -p build
cd build
cmake \
  -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \
  -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS" \
  -DCMAKE_INSTALL_PREFIX=$PKG \
  -DCMAKE_INSTALL_LIBDIR=lib$LIBDIRSUFFIX \
  -DCMAKE_BUILD_TYPE=Release \
  ..
cmake .. -DCMAKE_INSTALL_PREFIX=/usr
make
make install DESTDIR=$PKG

cd $TMP

tar xvf $CWD/Vulkan-Headers-sdk-$VERSION.tar.gz
cd Vulkan-Headers-sdk-$VERSION

chown -R root:root .
find . \
  \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
  -exec chmod 755 {} \; -o \
  \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
  -exec chmod 644 {} \;

mkdir -p build
cd build
cmake \
  -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \
  -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS" \
  -DCMAKE_INSTALL_PREFIX=/usr\
  -DCMAKE_INSTALL_LIBDIR=lib$LIBDIRSUFFIX \
  -DCMAKE_BUILD_TYPE=Release \
  ..
make
make install DESTDIR=$PKG
cd $TMP

tar xvf $CWD/Vulkan-Loader-sdk-$VERSION.tar.?z || exit 1
cd $TMP/Vulkan-Loader-sdk-$VERSION

chown -R root:root .
find . \
  \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
  -exec chmod 755 {} \; -o \
  \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
  -exec chmod 644 {} \;

mkdir -p build
cd build
  cmake \
    -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \
    -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS" \
    -DCMAKE_INSTALL_PREFIX=/usr \
    -DGLSLANG_INSTALL_DIR=$PKG/usr \
    -DVULKAN_HEADERS_INSTALL_DIR=$PKG/usr \
    -DBUILD_WSI_WAYLAND_SUPPORT=Off \
    -DBUILD_WSI_MIR_SUPPORT=Off \
    ..

  make $NUMJOBS VERBOSE=1 || make || exit 1
  make install DESTDIR=$PKG || exit 1

cd $TMP

tar xvf $CWD/Vulkan-ValidationLayers-sdk-$VERSION.tar.?z || exit 1
cd $TMP/Vulkan-ValidationLayers-sdk-$VERSION

chown -R root:root .
find . \
  \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
  -exec chmod 755 {} \; -o \
  \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
  -exec chmod 644 {} \;

mkdir -p build
cd build
  cmake \
    -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \
    -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS" \
    -DCMAKE_INSTALL_PREFIX=/usr \
    -DCMAKE_INSTALL_SYSCONFDIR=/etc \
    -DCMAKE_INSTALL_DATADIR=/share \
    -DCMAKE_SKIP_RPATH=True \
    -DBUILD_TESTS=Off \
    -DBUILD_WSI_XLIB_SUPPORT=On \
    -DBUILD_WSI_XCB_SUPPORT=On \
    -DBUILD_WSI_WAYLAND_SUPPORT=Off \
    -DBUILD_WSI_MIR_SUPPORT=Off \
    -DCMAKE_BUILD_TYPE=Release \
    -DGLSLANG_INSTALL_DIR=$PKG/usr \
    -DVULKAN_HEADERS_INSTALL_DIR=$PKG/usr \
    -DVULKAN_LOADER_INSTALL_DIR=$PKG/usr \
    ..

  make $NUMJOBS VERBOSE=1 || make || exit 1
  make install DESTDIR=$PKG || exit 1

cd $TMP

tar xvf $CWD/Vulkan-Tools-sdk-$VERSION.tar.?z || exit 1
cd $TMP/Vulkan-Tools-sdk-$VERSION

chown -R root:root .
find . \
  \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
  -exec chmod 755 {} \; -o \
  \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
  -exec chmod 644 {} \;

mkdir -p build
cd build
  cmake \
    -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \
    -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS" \
    -DCMAKE_BUILD_TYPE=Release \
    -DCMAKE_INSTALL_PREFIX=/usr \
    -DVULKAN_HEADERS_INSTALL_DIR=$PKG/usr \
    -DGLSLANG_INSTALL_DIR=$PKG/usr \
    -DVULKAN_LOADER_INSTALL_DIR=$PKG/usr \
    -DBUILD_WSI_WAYLAND_SUPPORT=Off \
    -DBUILD_WSI_MIR_SUPPORT=Off \
    ..

  make $NUMJOBS VERBOSE=1 || make || exit 1
  make install DESTDIR=$PKG || exit 1

cd $TMP

find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | grep ELF \
  | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true

mkdir -p $PKG/usr/doc/$PKGNAM-$VERSION
cp -a \
  Vulkan-Loader-sdk-$VERSION/*.txt \
  Vulkan-Loader-sdk-$VERSION/loader/LoaderAndLayerInterface.md \
  $PKG/usr/doc/$PKGNAM-$VERSION

mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc

cd $PKG
/sbin/makepkg -l y -c n $TMP/$PKGNAM-$VERSION-$ARCH-$BUILD.txz
 
4 members found this post helpful.
Old 10-09-2018, 01:16 PM   #2279
TurboBlaze
Member
 
Registered: Jan 2018
Location: Russian Federation, Lipetsk region, Dankov
Distribution: Porteus
Posts: 196

Rep: Reputation: Disabled
Do you have a plan to add Active Directory in Slackware 15?
 
Old 10-09-2018, 01:22 PM   #2280
dugan
LQ Guru
 
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 11,235

Rep: Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320Reputation: 5320
Quote:
Originally Posted by TurboBlaze View Post
Do you have a plan to add Active Directory in Slackware 15?
You mean PAM and Kerberos?

I'm pretty sure the answer is: "no plans, but not ruled out", and that this was the answer for many years now.

Last edited by dugan; 10-09-2018 at 01:57 PM.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Requests for -current (20151216) rworkman Slackware 3441 12-28-2017 03:50 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 04:48 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration