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.
Serious question... do we have compiler packages that are not being used anywhere in the system? If Pat isn't building anything using flang or f18, I'm not sure if he would include it (but I don't know development that well, and it could very well be that he's already including development software that isn't being used in building Slackware).
But if he does package development software that isn't being used, how likely are people to use flang and f18? There doesn't even seem to be SlackBuilds for them on SBo, so it seems like it might be something that is rarely used and may not have a place to be included with Slackware itself and is to be better maintained on SBo.
Well, the answer to the first question is "yes", since nothing uses GNAT, as far as I understand. I'm also not sure about gfortran. I do use it, and BLAS uses it, but BLAS is not in the official Slackware (although it is a very serious package). Still losing Fortran would be a shame, it's a living language.
The answer to the second question is I don't know, but c++, and all name-mangling compilers tend to produce headaches. Fortran is also name-mangling.
I'm also not sure about gfortran. I do use it, and BLAS uses it, but BLAS is not in the official Slackware (although it is a very serious package). Still losing Fortran would be a shame, it's a living language.
Fortran is used often in scientific environments too, like universities and research laboratories. And I use it at home, of course.
Intel's Math Kernel Library is available too: from their website
Quote:
Uses industry-standard C and Fortran APIs for compatibility with popular BLAS, LAPACK, and FFTW functions—no code changes required
which we use with their implementation of the Fortran compiler.
You could use e.g. the serial number additionally or instead.
I checked for this, but in checking all my drives with udevadm (I had the below for loop to output them all at once), only 2 of them had an entry containing "serial".
Code:
for i in a b c d e f g h; do
udevadm info -n /dev/sd$ -a | grep serial
done
Quote:
Originally Posted by Lockywolf
Well, the answer to the first question is "yes", since nothing uses GNAT, as far as I understand. I'm also not sure about gfortran. I do use it, and BLAS uses it, but BLAS is not in the official Slackware (although it is a very serious package). Still losing Fortran would be a shame, it's a living language.
I wonder if these were used in Slackware at some point and were just left in since they were expected or if they were simply added to support the people that desire to use them.
Quote:
Originally Posted by Lockywolf
The answer to the second question is I don't know, but c++, and all name-mangling compilers tend to produce headaches. Fortran is also name-mangling.
It doesn't seem like they give too many people severe enough headaches since they nobody has taken the effort to submit a SlackBuild to SBo.
Since groff 1.22.4 (commit ff62ef6) 'configure --docdir' is hardcoded in
Makefile.am
commit 1264531 removed REVISION and VERSION
commit 5fec19d INSTALL renamed INSTALL.extra; made INSTALL a link to gnulib
PATCH actions:
* remove --docdir (its noop now)
* move creating doc/ to above the doc/ cp.
* rm REVISION and VERSION from doc/ cp args
* change INSTALL* to INSTALL.* in doc/ cp args
* rm Changlog from doc/ cp args (it is truncated and cp'ed later)
* fix removal of unwanted groff docs (they're installed to /usr/share/ now).
Code:
--- groff.SlackBuild.orig 2020-03-31 21:39:55.972055370 -0400
+++ groff.SlackBuild.new 2020-04-01 18:13:29.154555549 -0400
@@ -88,7 +88,6 @@
--with-appresdir=/etc/X11/app-defaults \
--mandir=/usr/man \
--infodir=/usr/info \
- --docdir=/usr/doc/groff-$VERSION \
--build=$ARCH-slackware-linux || exit 1
make $NUMJOBS || make || exit 1
@@ -97,11 +96,11 @@
find $PKG | xargs file | grep -e "executable" -e "shared object" \
| grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
+mkdir -p $PKG/usr/doc/groff-$VERSION/xditview
cp -a \
- BUG-REPORT COPYING* ChangeLog FDL INSTALL* LICENSES MANIFEST MORE.STUFF \
- NEWS PROBLEMS PROJECTS README* REVISION TODO VERSION \
+ BUG-REPORT COPYING* FDL INSTALL.* LICENSES MANIFEST MORE.STUFF \
+ NEWS PROBLEMS PROJECTS README* TODO \
$PKG/usr/doc/groff-$VERSION
-mkdir -p $PKG/usr/doc/groff-$VERSION/xditview
cp -a src/devices/xditview/{README,TODO} $PKG/usr/doc/groff-$VERSION/xditview
# If there's a ChangeLog, installing at least part of the recent history
@@ -112,11 +111,9 @@
touch -r ChangeLog $DOCSDIR/ChangeLog
fi
+# Since groff 1.22.4 docdir is hardcoded in Makefile.am
# If you want all this stuff, it's in the source tarball:
-rm -rf $PKG/usr/doc/groff-$VERSION/*.ps \
- $PKG/usr/doc/groff-$VERSION/examples \
- $PKG/usr/doc/groff-$VERSION/html \
- $PKG/usr/doc/groff-$VERSION/pdf
+rm -rf $PKG/usr/share/doc/
( cd $PKG/usr/man
find . -type f -exec gzip -9 {} \+
It doesn't seem like they give too many people severe enough headaches since they nobody has taken the effort to submit a SlackBuild to SBo.
They are hard (if possible) to build with already available binary versions of LLVM. (Or at least the developers believe it to be so. Quoting https://github.com/flang-compiler/f18 :
Quote:
Installing LLVM from packages is most likely not an option as it will not include MLIR and not be built following C++17 standard.
I am not super sure what they mean by this, but compilers are essentially the stuff that everyone depends upon, so it is very easy to mess up.
I can, obviously, rebuild the GNU Studio by myself. Does this mean that I'll have to rebuild everything written in C++ with every update? I remember C++ being quite nasty in not being able to link binaries built with different compilers.
I think, this patch will make it into GCC 10, but I have no idea when GCC can make it into -current, changing a major version is a huge thing.
* New API
* Added ATK_ROLE_MARK and ATK_ROLE_SUGGESTION
* Add ATK_TEX_ATTR_TEXT_POSITION to the list of possible AtkText
attributes (MR!33)
I am wondering: do we have to wait for an upgrade of at-spi2-core and at-spi2-atk to draw benefit of that? Will Orca use it without upgrading it? I will ask Joanie in the Orca mailing list.
Last edited by Didier Spaier; 04-02-2020 at 07:36 AM.
It seems like network-manager-applet will need to get switched over to meson. Per this thread, it seems like the stock package is missing some security features. Once we switched the SlackBuild to meson, the problem was solved. I am not at home and can't provide an actual patch, but this is what I used to replace the autotools section of the script.
Serious question... do we have compiler packages that are not being used anywhere in the system? If Pat isn't building anything using flang or f18, I'm not sure if he would include it (but I don't know development that well, and it could very well be that he's already including development software that isn't being used in building Slackware).
But if he does package development software that isn't being used, how likely are people to use flang and f18? There doesn't even seem to be SlackBuilds for them on SBo, so it seems like it might be something that is rarely used and may not have a place to be included with Slackware itself and is to be better maintained on SBo.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.