SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm not sure the entire reasoning, but I think it has to do with how transmission reports upload/download stats to the tracker. The point is not so much that transmission is bad, its more that using it with some trackers can have unintended failures and/or consequences.
I'm not sure the entire reasoning, but I think it has to do with how transmission reports upload/download stats to the tracker. The point is not so much that transmission is bad, its more that using it with some trackers can have unintended failures and/or consequences.
maybe it just exposes issues with their tracker software that they don't know how/have time/want to fix so they simply ban its identifying string.
Could mozilla-firefox.SlackBuild be updated, so that it easily allows for:
1. Custom optimizations,
2. Custom compiler (e.g. clang):
Code:
--- mozilla-firefox.SlackBuild.orig 2018-01-29 19:43:56.000000000 +0100
+++ mozilla-firefox.SlackBuild 2018-02-09 12:11:03.400129604 +0100
@@ -79,38 +79,38 @@
if [ "$ARCH" = "i586" ]; then
SLKCFLAGS=""
LIBDIRSUFFIX=""
- OPTIMIZE=" --enable-optimize=-O1 "
+ OPTIMIZE=${OPTIMIZE:-"-O1"}
elif [ "$ARCH" = "i686" ]; then
SLKCFLAGS=""
LIBDIRSUFFIX=""
- OPTIMIZE=" --enable-optimize=-O1 "
+ OPTIMIZE=${OPTIMIZE:-"-O1"}
elif [ "$ARCH" = "s390" ]; then
SLKCFLAGS="-O2"
LIBDIRSUFFIX=""
- OPTIMIZE=" --enable-optimize=-O1 "
+ OPTIMIZE=${OPTIMIZE:-"-O1"}
elif [ "$ARCH" = "x86_64" ]; then
SLKCFLAGS="-O2 -fPIC"
LIBDIRSUFFIX="64"
- OPTIMIZE=" --enable-optimize=-O1 "
+ OPTIMIZE=${OPTIMIZE:-"-O1"}
elif [ "$ARCH" = "arm" ]; then
SLKCFLAGS="-O2 -march=armv4 -mtune=xscale"
LIBDIRSUFFIX=""
- OPTIMIZE=" --enable-optimize=-O1 "
+ OPTIMIZE=${OPTIMIZE:-{"-O1"}
elif [ "$ARCH" = "armel" ]; then
SLKCFLAGS="-O2 -march=armv4t"
LIBDIRSUFFIX=""
- OPTIMIZE=" --enable-optimize=-O1 "
+ OPTIMIZE=${OPTIMIZE:-"-O1"}
else
SLKCFLAGS="-O2"
LIBDIRSUFFIX=""
- OPTIMIZE=" --enable-optimize=-O1 "
+ OPTIMIZE=${OPTIMIZE:-"-O1"}
fi
# Link using gold. This avoids running out of memory on 32-bit systems, and
# avoids a recurring build failure with GNU ld on other systems.
PATH="$(pwd)/gold:$PATH"
-export CC="gcc -B$(pwd)/gold"
-export CXX="g++ -B$(pwd)/gold"
+export CC=${CC:-"gcc -B$(pwd)/gold"}
+export CXX=${CXX:-"g++ -B$(pwd)/gold"}
CWD=$(pwd)
TMP=${TMP:-/tmp}
@@ -185,7 +185,6 @@
--enable-application=browser \
--enable-default-toolkit=cairo-gtk3 \
--enable-startup-notification \
- $OPTIMIZE \
$GOOGLE_API_KEY \
--enable-strip \
--enable-cpp-rtti \
@@ -227,6 +226,10 @@
# needed for PGO.
echo ". \$topsrcdir/browser/config/mozconfig" > .mozconfig
+# Tell about the selected compiler.
+echo "export CC=\"${CC}\"" >> .mozconfig
+echo "export CXX=\"${CXX}\"" >> .mozconfig
+
# Mozilla devs enforce using an objdir for building
# https://developer.mozilla.org/en/Configuring_Build_Options#Building_with_an_objdir
mkdir obj
@@ -238,6 +241,7 @@
# Write in it the options above
for option in $OPTIONS; do echo "ac_add_options $option" >> .mozconfig; done
+echo "ac_add_options --enable-optimize=\"${OPTIMIZE}\"" >> .mozconfig
# https://developer.mozilla.org/en-US/docs/Building_with_Profile-Guided_Optimization
# Thanks to ArchLinux and Gentoo for the additional hints.
And could the same love be applied to mozilla-thunderbird.SlackBuild:
1. Plus a switch to allow disabling Lightning (which used to be disabled by default long time ago):
Code:
--- mozilla-thunderbird.SlackBuild.orig 2017-10-06 22:01:07.000000000 +0200
+++ mozilla-thunderbird.SlackBuild 2018-02-09 12:53:59.035233357 +0100
@@ -51,31 +51,38 @@
if [ "$ARCH" = "i586" ]; then
SLKCFLAGS=""
LIBDIRSUFFIX=""
- OPTIMIZE=" --enable-optimize=-O1 "
+ OPTIMIZE=${OPTIMIZE:-"-O1"}
elif [ "$ARCH" = "x86_64" ]; then
SLKCFLAGS="-fPIC"
LIBDIRSUFFIX="64"
- OPTIMIZE=" --enable-optimize=-O1 "
+ OPTIMIZE=${OPTIMIZE:-"-O1"}
elif [ "$ARCH" = "arm" ]; then
SLKCFLAGS="-march=armv4 -mtune=xscale"
LIBDIRSUFFIX=""
- OPTIMIZE=" --enable-optimize=-O1 "
+ OPTIMIZE=${OPTIMIZE:-"-O1"}
else
SLKCFLAGS=""
LIBDIRSUFFIX=""
- OPTIMIZE=" --enable-optimize=-O1 "
+ OPTIMIZE=${OPTIMIZE:-"-O1"}
fi
# Link using gold. This avoids running out of memory on 32-bit systems, and
# avoids a recurring build failure with GNU ld on other systems.
PATH="$(pwd)/gold:$PATH"
-export CC="gcc -B$(pwd)/gold"
-export CXX="g++ -B$(pwd)/gold"
+export CC=${CC:-"gcc -B$(pwd)/gold"}
+export CXX=${CXX:-"g++ -B$(pwd)/gold"}
CWD=$(pwd)
TMP=${TMP:-/tmp}
PKG=$TMP/package-mozilla-thunderbird
+# Build with or without Lightning.
+if [ "$ENABLE_CALENDAR" = no ]; then
+ ENABLE_CALENDAR="--disable-calendar"
+else
+ ENABLE_CALENDAR="--enable-calendar"
+fi
+
# If there is a private Google API key available at compile time, use
# it to enable support for Google Safe Browsing. For Slackware builds,
# we use a private key issued for the Slackware project. If you are
@@ -146,11 +153,10 @@
--with-system-zlib \
--enable-alsa \
--enable-application=mail \
- --enable-calendar \
+ $ENABLE_CALENDAR \
--enable-default-toolkit=cairo-gtk3 \
--enable-startup-notification \
--enable-ldap \
- $OPTIMIZE \
--enable-strip \
--enable-cpp-rtti \
--enable-accessibility \
@@ -189,6 +195,10 @@
# Assemble our .mozconfig:
echo > .mozconfig
+# Tell about the selected compiler.
+echo "export CC=\"${CC}\"" >> .mozconfig
+echo "export CXX=\"${CXX}\"" >> .mozconfig
+
# Mozilla devs enforce using an objdir for building
# https://developer.mozilla.org/en/Configuring_Build_Options#Building_with_an_objdir
mkdir obj
@@ -198,6 +208,7 @@
# Write in it the options above
for option in $OPTIONS; do echo "ac_add_options $option" >> .mozconfig; done
+echo "ac_add_options --enable-optimize=\"${OPTIMIZE}\"" >> .mozconfig
make -f client.mk build || exit 1
make -f client.mk install DESTDIR=$PKG || exit 1
On the subject of man-db. May I suggest commenting out the references to /usr/share/man in man_db.conf so that manpath doesn't give duplicate locations.
This will allow people to do something like MANPATH=$(manpath) in their /etc/profile without getting the duplicate locations, if they so wish.
Also, a minor consistency point. When cron.daily/mandb runs automatically it won't have a MANPATH set as crond doesn't have MANPATH in it's environment. If however the admin decides to update the database manually by running cron.daily/mandb from a root shell it will inherit MANPATH from the shell, resulting in a different scan than happens when run under cron. For the sake of consistency can I suggest unsetting MANPATH in cron.daily/mandb before the call to mandb itself so that the scan always happens the same way, regardless of how it is invoked (unless they run /usr/bin/mandb directly of course, but that can't be helped).
Seemed like a good time to mention it as there's another bump to be done.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
