• Linux Mint 20.1 issue

    From Mark Seifert@1:120/457 to All on Sat Feb 6 19:53:07 2021
    Hey all,

    I have been a user of both Windows and Linux/Unix for a while.. I have 2 questions..

    1) Any one possibly tell me why everytime I try to "make" I get errors, snap, flatpack, appimage, .deb and rpm work fine but if I have to try to "make" it fails. Any suggestions..?

    2) Does/Did anyone else upgrade to Linux Mint only to have it tell you that your network cable is unplugged when the live cd found it as connected, but the actual install fails.

    I'm currently using Mint 18.3.. am looking at moving to 20.1 so it is supported until 2025 as 18.3 ends it support in April 2021.. :(

    Otherwise I love Mint, been using it exclusively as my primary OS for 5 years... Some people are gamers, I've always been a software tester instead.. I've tried most varients of Unix/Linux and most other OS's.. I've been using a computer since I was 15 and I'm 53 now.




    ... A nickel for your thoughts; $200 or more to act it out.
    ___ MultiMail/Linux v0.49

    --- Mystic BBS/QWK v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Communication Connection 1:120/457 (1:120/457)
  • From Aaron Thomas@1:275/99 to Mark Seifert on Sat Feb 6 21:06:06 2021
    2) Does/Did anyone else upgrade to Linux Mint only to have it tell you that your network cable is unplugged when the live cd found it as connected, but the actual install fails.

    When Mint released 20.0 (Ulyana or something) I upgraded from an existing installation and had a hardware issue (I think it was my Wifi adapater) but then I did a fresh install and had the same problem.

    To get around it, I installed the latest Ubuntu and the hardware issue was gone. It seems to me like Mint has omitted support for certain hardware with that big bad release.

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: CompuBBS | Ashburn VA | cfbbs.scinet-ftn.org (1:275/99)
  • From Nicholas Boel@1:154/10 to Mark Seifert on Sun Feb 7 00:26:06 2021
    Hello Mark,

    On Sat Feb 06 2021 19:53:06, Mark Seifert wrote to All:

    I have been a user of both Windows and Linux/Unix for a while.. I have
    2 questions..

    1) Any one possibly tell me why everytime I try to "make" I get
    errors, snap, flatpack, appimage, .deb and rpm work fine but if I have
    to try to "make" it fails. Any suggestions..?

    You probably don't have the coreutils package installed, and if it doesn't come with it, gcc.

    I'm currently using Mint 18.3.. am looking at moving to 20.1 so it is supported until 2025 as 18.3 ends it support in April 2021.. :(

    Sorry, no experience with that. But I would think they will fix that issue by April. ;)

    Otherwise I love Mint, been using it exclusively as my primary OS for
    5 years... Some people are gamers, I've always been a software tester instead.. I've tried most varients of Unix/Linux and most other OS's.. I've been using a computer since I was 15 and I'm 53 now.

    Have you really tried most variants? Theres so many out there I don't even want to try them all.

    I'm a fan of Archlinux. So, if you want to try a GUI version of it you can take a look at Manjaro. It's probably more "bleeding edge" than any debian based distro. I've used this for over 5 years and never had to reinstall the whole damn system, like I had to do with Debian based crap in the past (Ubuntu, Kubuntu, etc).

    Sorry, Debian based stuff got on my bad side early years ago. However I commend Ubuntu on their work to switch Windows users over and trying to make it as easy as possible.

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- GoldED+/LNX 1.1.5-b20181215
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Anna Christina Nass@2:240/5824.1 to Mark Seifert on Sun Feb 7 10:17:00 2021
    Am 06.02.21 schrieb Mark Seifert@1:120/457 in LINUX:

    Hallo Mark,

    1) Any one possibly tell me why everytime I try to "make" I get errors, snap, flatpack, appimage, .deb and rpm work fine but if I have to try to "make" it fails. Any suggestions..?

    When make fails, you should be able to see an error message that could
    tell you "why" it failed.
    If some .h files are missing, you could search for the corresponding -dev package and install it.
    Also, the meta-package "build-essential" is helpful when compiling
    packages.

    2) Does/Did anyone else upgrade to Linux Mint only to have it tell you
    that your network cable is unplugged when the live cd found it as connected, but the actual install fails.

    Maybe a package containing firmware files for the network hardware is
    missing in the installation?

    Regards,
    Anna

    --- OpenXP 5.0.48
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Richard Falken@1:123/115 to Mark Seifert on Sun Feb 7 04:39:03 2021
    Re: Linux Mint 20.1 issue
    By: Mark Seifert to All on Sat Feb 06 2021 07:53 pm

    Hey all,

    I have been a user of both Windows and Linux/Unix for a while.. I have 2 questions..

    1) Any one possibly tell me why everytime I try to "make" I get errors, snap, flatpack, appimage, .deb and rpm work fine but
    I have to try to "make" it fails. Any suggestions..?

    Not a Mint user here, but in order to know why "make" is failing we'd need more information. Specifically:

    * which program are you trying to compile.
    * which steps are you following to do it.

    Most times "make" fails it is because you are missing some dependency that was not tested by the ./configure script, there are
    version missmatches, or the program you are trying to compile is just bogus.

    --
    gopher://gopher.richardfalken.com/1/richardfalken
    --- SBBSecho 3.12-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)
  • From Alexey Vissarionov@2:5020/545 to Anna Christina Nass on Sun Feb 7 18:30:00 2021
    Good ${greeting_time}, Anna!

    07 Feb 2021 10:17:00, you wrote to Mark Seifert:

    1) Any one possibly tell me why everytime I try to "make" I get
    errors, snap, flatpack, appimage, .deb and rpm work fine but if I
    have to try to "make" it fails. Any suggestions..?
    When make fails, you should be able to see an error message that
    could tell you "why" it failed. If some .h files are missing, you
    could search for the corresponding -dev package and install it.

    In a properly designed systems you'd never need to install the development packages: they should be installed only inside of a clean build environment.

    Also, the meta-package "build-essential" is helpful when compiling packages.

    I'd never use the system where such package does really exist...

    2) Does/Did anyone else upgrade to Linux Mint only to have it tell
    you that your network cable is unplugged when the live cd found it
    as connected, but the actual install fails.
    Maybe a package containing firmware files for the network hardware
    is missing in the installation?

    Or the kernel was built improperly.


    --
    Alexey V. Vissarionov aka Gremlin from Kremlin
    gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii

    ... :wq!
    --- /bin/vi
    * Origin: ::1 (2:5020/545)
  • From Mark Seifert@1:120/457 to Aaron Thomas on Sun Feb 7 14:30:18 2021
    Quoting Aaron Thomas, who said to mseifert <-(:

    When Mint released 20.0 (Ulyana or something) I upgraded from an
    existing installation and had a hardware issue (I think it was my Wifi adapater) but then I did a fresh install and had the same problem.

    To get around it, I installed the latest Ubuntu and the hardware issue
    was gone. It seems to me like Mint has omitted support for certain hardware with that big bad release.

    I have tried Ubuntu, kbuntu and even xbuntu none of which seemed close enough for me to finally let go of my windows branch before going completely to Unix.. Mint filled that need.



    ... Any sufficiently advanced bug will become a feature.
    ___ MultiMail/Linux v0.49

    --- Mystic BBS/QWK v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Communication Connection 1:120/457 (1:120/457)
  • From Mark Seifert@1:120/457 to Nicholas Boel on Sun Feb 7 14:30:18 2021
    (: Quoting Nicholas Boel, who said to mseifert <-:)


    You probably don't have the coreutils package installed, and if it
    doesn't come with it, gcc.

    I checked in the Synptec Package Manager, it said it was install, so I re-installed it.. lets see if that helps...

    I'm currently using Mint 18.3.. am looking at moving to 20.1 so it is supported until 2025 as 18.3 ends it support in April 2021.. :(

    Sorry, no experience with that. But I would think they will fix that
    issue by April. ;)

    I hope it's fixed soon.. I'd hate to start over, and could switch to Ubuntu but prefer Mint.

    Otherwise I love Mint, been using it exclusively as my primary OS for
    5 years... Some people are gamers, I've always been a software tester instead.. I've tried most varients of Unix/Linux and most other OS's.. I've been using a computer since I was 15 and I'm 53 now.

    Have you really tried most variants? Theres so many out there I don't
    even want to try them all.

    I'm a fan of Archlinux. So, if you want to try a GUI version of it you
    can take a look at Manjaro. It's probably more "bleeding edge" than any debian based distro. I've used this for over 5 years and never had to reinstall the whole damn system, like I had to do with Debian based
    crap in the past (Ubuntu, Kubuntu, etc).

    I've heard in a couple of Linux podcasts that Archlinux was more for people who compiled (make) their applications, which is something I have no interest in and no luck at..

    I may have to go back to Ubuntu. I wish Mandrake still existed.

    I've tried most common *nix varients, and others Beos, Skyos, OS/2 pretty much if it had a GUI I've probably played with it at some point.. some people play games, I play with software/OS's.


    ... A truly wise man never plays leapfrog with a moose.
    ___ MultiMail/Linux v0.49

    --- Mystic BBS/QWK v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Communication Connection 1:120/457 (1:120/457)
  • From Mark Seifert@1:120/457 to Anna Christina Nass on Sun Feb 7 14:30:18 2021
    Quoting Anna Christina Nass, who said to mseifert <-(:

    Am 06.02.21 schrieb Mark Seifert@1:120/457 in LINUX:

    Hallo Mark,

    When make fails, you should be able to see an error message that could tell you "why" it failed.
    If some .h files are missing, you could search for the corresponding
    -dev package and install it.
    Also, the meta-package "build-essential" is helpful when compiling packages.

    I have checked and build-essential is installed in the Synaptec Package Manager, so I told it to re-install.

    2) Does/Did anyone else upgrade to Linux Mint only to have it tell you that your network cable is unplugged when the live cd found it as connected, but the actual install fails.

    Maybe a package containing firmware files for the network hardware is missing in the installation?

    I don't know, but would hate to have to switch from Linux Mint to something else because they decided to stop supporting my motherboards built in network adapter..especially since the live cd has no issues.

    thanks.



    ... Strength of mind: Person who can eat one salted peanut.
    ___ MultiMail/Linux v0.49

    --- Mystic BBS/QWK v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Communication Connection 1:120/457 (1:120/457)
  • From Mark Seifert@1:120/457 to Richard Falken on Sun Feb 7 14:30:18 2021
    Not a Mint user here, but in order to know why "make" is failing we'd
    need more information. Specifically:

    * which program are you trying to compile.
    * which steps are you following to do it.

    Most times "make" fails it is because you are missing some dependency
    that was not tested by the ./configure script, there are version missmatches,

    This happens for anthing where the programmer says just type make and that's it. Only once did it ever work. Handrolling a program may be a rite of passage in Linux, but it's a pain in the ass if you're going blind but don't like Windows.



    ... The worst thing about censorship is .
    ___ MultiMail/Linux v0.49

    --- Mystic BBS/QWK v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Communication Connection 1:120/457 (1:120/457)
  • From Mike Powell@1:2320/105 to MARK SEIFERT on Sun Feb 7 10:47:00 2021
    1) Any one possibly tell me why everytime I try to "make" I get errors, snap, flatpack, appimage, .deb and rpm work fine but if I have to try to "make" it fails. Any suggestions..?

    Depends on what errors you are getting. As someone already pointed out,
    you could be missing coreutils, or you could be missing some other pre-requisite that is specific to the program you are trying to compile.

    Mike


    * SLMR 2.1a * It's as easy as 3.14159265358979323846...
    --- SBBSecho 3.12-Linux
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)
  • From Richard Falken@1:123/115 to Mark Seifert on Sun Feb 7 16:21:07 2021
    Re: Re: Linux Mint 20.1 issue
    By: Mark Seifert to Nicholas Boel on Sun Feb 07 2021 02:30 pm

    I've heard in a couple of Linux podcasts that Archlinux was more for people compiled (make) their applications, which is something I have no interest in and no luck at..

    I may have to go back to Ubuntu. I wish Mandrake still existed.

    I've tried most common *nix varients, and others Beos, Skyos, OS/2 pretty mu if it had a GUI I've probably played with it at some point.. some people pla games, I play with software/OS's.

    YOu could try MX Linux. It is quite ok for an easy distribution and it is close to the top (or directly in the top) at Distrowatch at the moment.

    Not sure what you are looking for in a distribution exactly.

    --
    gopher://gopher.richardfalken.com/1/richardfalken
    --- SBBSecho 3.12-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)
  • From Aaron Thomas@1:275/99 to Mark Seifert on Sun Feb 7 16:10:25 2021
    I have tried Ubuntu, kbuntu and even xbuntu none of which seemed close enough for me to finally let go of my windows branch before going completely to Unix.. Mint filled that need.

    I was the same way. I used Mint for 9 years until 20.something came out and lacked hardware support that I needed. Ubuntu 20.04 LTS w/KDE desktop is much more beautiful and smooth than Ubuntu of 10 years ago w/GNOME desktop.

    Anyone else have a suggestion for him? He upgraded Mint and it's no longer recognizing his built-in ethernet card. ("Network cable unplugged.")

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: CompuBBS | Ashburn VA | cfbbs.scinet-ftn.org (1:275/99)
  • From Mark Seifert@1:120/457 to Mike Powell on Sun Feb 7 19:40:03 2021
    Quoting Mike Powell, who said to mseifert <-(:

    1) Any one possibly tell me why everytime I try to "make" I get errors,
    snap,
    flatpack, appimage, .deb and rpm work fine but if I have to try to "make" it fails. Any suggestions..?

    Depends on what errors you are getting. As someone already pointed
    out, you could be missing coreutils, or you could be missing some other pre-requisite that is specific to the program you are trying to
    compile.

    Ok, as I previously replied both coreutils and the other essentil-whatever were installed but I reinstalled them anyway. As for what it is I'm trying to make.. it doesn't matter NOTHING ever gets made.. I'll need to copy the output next time since people thing it might help.

    Sorry if I sound a bit touchy but I'm not that new to linux and am not completely helpless and should be able to resolve this without assistance but can't.. so please understand the frustration of the issue is only compunded by the fact everyone keeps saying the same things. Sorry but keep in mind I'm 53 and have been using computers for 38 years, programming for 30 years and using linux as my OS for about 12 years.

    Which is why I'm asking for help ... I SHOULD be able to resolve this.. damn ego.. down boy down...!!



    ... Synonym: A word you use when you can't spell the other.
    ___ MultiMail/Linux v0.49

    --- Mystic BBS/QWK v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Communication Connection 1:120/457 (1:120/457)
  • From Mark Seifert@1:120/457 to Richard Falken on Sun Feb 7 19:40:03 2021
    Quoting Richard Falken, who said to mseifert <-(:

    I've tried most common *nix varients, and others Beos, Skyos, OS/2 pretty mu if it had a GUI I've probably played with it at some point.. some people pla games, I play with software/OS's.

    YOu could try MX Linux. It is quite ok for an easy distribution and it
    is close to the top (or directly in the top) at Distrowatch at the
    moment.

    Not sure what you are looking for in a distribution exactly.

    I know that most linux distros are pretty much the same, with the major differences being the desktop (kde, gnome, xfce, mate, cinnamon, etc.. and the applications included. Not to mention any special instuctions in the Kernal. But all in all I want an OS that's free, won't crash all the time, is easy to update and won't force me to get OS specific software (for example going from Windows to Linux)


    ... Nothing is so smiple that it can't get screwed up.
    ___ MultiMail/Linux v0.49

    --- Mystic BBS/QWK v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Communication Connection 1:120/457 (1:120/457)
  • From Richard Falken@1:123/115 to Mark Seifert on Sun Feb 7 19:57:06 2021
    Re: Re: Linux Mint 20.1 issue
    By: Mark Seifert to Richard Falken on Sun Feb 07 2021 07:40 pm

    I know that most linux distros are pretty much the same, with the major differences being the desktop (kde, gnome, xfce, mate, cinnamon, etc.. and t applications included. Not to mention any special instuctions in the Kernal But all in all I want an OS that's free, won't crash all the time, is easy t update and won't force me to get OS specific software (for example going fro Windows to Linux)

    Those are very generic needs.

    "Easy to update" discards Slackware, which is what I would usually recommend. It is not that it is "hard" to update but it is a bit more involved than apt-get upgrade.

    My next suggestion would be Debian or Devuan. There were some stats in the latter Linux Magazine issue from which I draw the conclussion that the Debian ecosystem is becoming the default in Desktops.

    If you need something more modern MX Linux is workable. I have an install around which I use for testing random stuff. I personally don't think that "easy to use" Debian derivatives have such a big of an edge compared to their daddy, at least nowadays, but I can see MX working for people familiar with Mints and *buntus.

    Just my two cents. In the end of the day people sticks with what feels better for them.

    --
    gopher://gopher.richardfalken.com/1/richardfalken
    --- SBBSecho 3.12-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)
  • From Dan Clough@1:123/115 to Mark Seifert on Sun Feb 7 21:35:00 2021
    Mark Seifert wrote to Nicholas Boel <=-

    I may have to go back to Ubuntu. I wish Mandrake still existed.

    I've tried most common *nix varients, and others Beos, Skyos,
    OS/2 pretty much if it had a GUI I've probably played with it at
    some point.. some people play games, I play with software/OS's.

    And yet..... you can't compile something?

    Install "build-essential" and get on with it, FFS.

    Or at least provide some ACTUAL error lines/messages from a compiling attempt, it's likely a very easy thing to fix.


    ... Apathy Error: Strike any key...or none, for that matter.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.12-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)
  • From Kai Richter@2:240/77 to Mark Seifert on Mon Feb 8 16:10:14 2021
    Hello Mark!

    07 Feb 21, Mark Seifert wrote to Mike Powell:

    Ok, as I previously replied both coreutils and the other
    essentil-whatever were installed but I reinstalled them anyway.

    There is a chance for a hit if you throw a stone into the fog.

    As for what it is I'm trying to make.. it doesn't matter NOTHING ever
    gets made.. I'll need to copy the output next time since people thing
    it might help.

    things. Sorry but keep in mind I'm 53 and have been using computers
    for 38 years, programming for 30 years and using linux as my OS for
    about 12 years.

    I'm surprised. You should know the usual way to approach this. Main rule for computers is garbage in = garbage out. Linux is silent if everthing is fine and should be verbose in case of an error. This error report should give a pointer to what's going on. Your re-installation is based on guesses instead of facts.

    If you could tell which software you want to compile and what the output of make is some of us may be capable to pick up the trail.

    Which is why I'm asking for help ... I SHOULD be able to resolve

    Calm down. ;) If you really like Mint you shouldn't give up easily. If the live CD does boot but fails with an internet connection there should be some information in /var/log/ or dmesg.

    Regards

    Kai

    --- GoldED+/LNX 1.1.4.7
    * Origin: Monobox (2:240/77)
  • From Anna Christina Nass@2:240/5824.1 to Alexey Vissarionov on Mon Feb 8 15:37:00 2021
    Am 07.02.21 schrieb Alexey Vissarionov@2:5020/545 in LINUX:

    Hallo Alexey,

    1) Any one possibly tell me why everytime I try to "make" I get
    errors, snap, flatpack, appimage, .deb and rpm work fine but if I
    have to try to "make" it fails. Any suggestions..?
    When make fails, you should be able to see an error message that
    could tell you "why" it failed. If some .h files are missing, you
    could search for the corresponding -dev package and install it.

    In a properly designed systems you'd never need to install the development packages: they should be installed only inside of a clean build environment.

    ?!?!?!?
    The original poster wants to install software via "make" and I guess this means to compile the program which indeed needs development programs.

    What you do on your systems was not the question - or do you have a better solution with your "properly designed system"?

    Also, the meta-package "build-essential" is helpful when compiling
    packages.
    I'd never use the system where such package does really exist...

    Then stay away from everything that is derived from Debian GNU/Linux.

    Anna

    --- OpenXP 5.0.48
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Anna Christina Nass@2:240/5824.1 to Mark Seifert on Mon Feb 8 15:43:00 2021
    Am 07.02.21 schrieb Mark Seifert@1:120/457 in LINUX:

    Hallo Mark,

    When make fails, you should be able to see an error message that could ACN>> tell you "why" it failed.
    If some .h files are missing, you could search for the corresponding ACN>> -dev package and install it.
    Also, the meta-package "build-essential" is helpful when compiling
    packages.

    I have checked and build-essential is installed in the Synaptec Package Manager, so I told it to re-install.

    Could you elaborate a little more on the error messages that you are
    getting when using "make" to install the (which??) program?

    Maybe a package containing firmware files for the network hardware is ACN>> missing in the installation?

    I don't know, but would hate to have to switch from Linux Mint to
    something else because they decided to stop supporting my motherboards built in network adapter..especially since the live cd has no issues.

    If you start from the live cd, try runnung "lspci -v" and search for the
    part that starts with ".... Ethernet controller:"
    In this section, you see the lines "Kernel driver in use" and "Kernel modules".
    Which driver/module is it?
    Also, you could try googling the name of the NIC (the part behind
    "Ethernet controller:") together with "firmware linux" or "firmware
    ubuntu", which might tell you the name of the firmware package you need.

    Regards,
    Anna

    --- OpenXP 5.0.48
    * Origin: Imzadi Box Point (2:240/5824.1)
  • From Alexey Vissarionov@2:5020/545 to Anna Christina Nass on Mon Feb 8 20:05:00 2021
    Good ${greeting_time}, Anna!

    08 Feb 2021 15:37:00, you wrote to me:

    1) Any one possibly tell me why everytime I try to "make" I get
    errors, snap, flatpack, appimage, .deb and rpm work fine but if I
    have to try to "make" it fails. Any suggestions..?
    When make fails, you should be able to see an error message that
    could tell you "why" it failed. If some .h files are missing, you
    could search for the corresponding -dev package and install it.
    In a properly designed systems you'd never need to install the
    development packages: they should be installed only inside of a
    clean build environment.
    ?!?!?!?
    The original poster wants to install software via "make" and I
    guess this means to compile the program which indeed needs
    development programs.

    Any and all software should (as in FTA-1006 and RFC-2119) be built as the packages and installed with a package management system. Otherwise your favourite system would turn into a Slackware regardless of your will.

    What you do on your systems was not the question - or do you have a better solution with your "properly designed system"?

    Yes, two. First is "hasher", which prepares a clean build environment and runs it in a container using unshare() system call. Second is "gear", which solves the compile-time dependencies, installs them into a build container, creates source package from a git commit-id and feeds all this stuff to the hasher.

    So the rebuild becomes as simple as

    alias gh 'time gear-hsh --commit --verbose'

    running as an unprivileged user, and the result is the RPM packages.

    Also, the meta-package "build-essential" is helpful when compiling
    packages.
    I'd never use the system where such package does really exist...
    Then stay away from everything that is derived from Debian GNU/Linux.

    I do (and recommend) that since CVE-2008-0166 :-)


    --
    Alexey V. Vissarionov aka Gremlin from Kremlin
    gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii

    ... GPG: 8832FE9FA791F7968AC96E4E909DAC45EF3B1FA8 @ hkp://keys.gnupg.net
    --- /bin/vi
    * Origin: ::1 (2:5020/545)
  • From Mark Seifert@1:120/457 to Mike Powell on Mon Feb 8 12:05:59 2021
    Quoting Mike Powell, who said to mseifert <-(:

    1) Any one possibly tell me why everytime I try to "make" I get errors,
    snap,
    flatpack, appimage, .deb and rpm work fine but if I have to try to "make" it fails. Any suggestions..?

    Depends on what errors you are getting. As someone already pointed
    out, you could be missing coreutils, or you could be missing some other pre-requisite that is specific to the program you are trying to
    compile.

    Ok, as I previously replied both coreutils and the other essentil-whatever were installed but I reinstalled them anyway. As for what it is I'm trying to make.. it doesn't matter NOTHING ever gets made.. I'll need to copy the output next time since people thing it might help.

    Sorry if I sound a bit touchy but I'm not that new to linux and am not completely helpless and should be able to resolve this without assistance but can't.. so please understand the frustration of the issue is only compunded by the fact everyone keeps saying the same things. Sorry but keep in mind I'm 53 and have been using computers for 38 years, programming for 30 years and using linux as my OS for about 12 years.

    Which is why I'm asking for help ... I SHOULD be able to resolve this.. damn ego.. down boy down...!!



    ... Synonym: A word you use when you can't spell the other.
    ___ MultiMail/Linux v0.49

    --- Mystic BBS/QWK v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Communication Connection 1:120/457 (1:120/457)
  • From Mark Seifert@1:120/457 to Richard Falken on Mon Feb 8 12:05:59 2021
    Quoting Richard Falken, who said to mseifert <-(:

    I've tried most common *nix varients, and others Beos, Skyos, OS/2 pretty mu if it had a GUI I've probably played with it at some point.. some people pla games, I play with software/OS's.

    YOu could try MX Linux. It is quite ok for an easy distribution and it
    is close to the top (or directly in the top) at Distrowatch at the
    moment.

    Not sure what you are looking for in a distribution exactly.

    I know that most linux distros are pretty much the same, with the major differences being the desktop (kde, gnome, xfce, mate, cinnamon, etc.. and the applications included. Not to mention any special instuctions in the Kernal. But all in all I want an OS that's free, won't crash all the time, is easy to update and won't force me to get OS specific software (for example going from Windows to Linux)


    ... Nothing is so smiple that it can't get screwed up.
    ___ MultiMail/Linux v0.49

    --- Mystic BBS/QWK v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Communication Connection 1:120/457 (1:120/457)
  • From Mark Seifert@1:120/457 to Richard Falken on Mon Feb 8 14:06:28 2021
    Richard Falken said to mseifert <-

    Those are very generic needs.

    "Easy to update" discards Slackware, which is what I would usually recommend. It is not that it is "hard" to update but it is a bit more involved than apt-get upgrade.

    My next suggestion would be Debian or Devuan. There were some stats in
    the latter Linux Magazine issue from which I draw the conclussion that
    the Debian ecosystem is becoming the default in Desktops.

    If you need something more modern MX Linux is workable. I have an
    install around which I use for testing random stuff. I personally don't think that "easy to use" Debian derivatives have such a big of an edge compared to their daddy, at least nowadays, but I can see MX working
    for people familiar with Mints and *buntus.

    Just my two cents. In the end of the day people sticks with what feels better for them.

    Thanks, I like the fact that with *most* linux distros today they are pretty easy to use but still give me the terminal where I can create a .sh file to do things from the command line, like I used to do in Dos many many, many moons ago. If it wasn't for the fact that the "support" for it runs out I'd not bother with the idea of upgrading.. I like the way my Mint works.

    I'll have to look at MX or bite the bullet and go Ubunu, but will keep an eye on LM just incase they fix this issue.

    ... OK, I'm weird! But I'm saving up to become eccentric.
    ___ MultiMail/Linux v0.49

    --- Mystic BBS/QWK v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Communication Connection 1:120/457 (1:120/457)
  • From Mike Powell@1:2320/105 to MARK SEIFERT on Mon Feb 8 14:51:00 2021
    Which is why I'm asking for help ... I SHOULD be able to resolve this.. damn >ego.. down boy down...!!

    LOL, you've been at it about as long as I have (using linux, that is).

    When it happens to me, it usually means I am missing a prerequisite package
    for the package I am trying to compile, *OR* I don't have some part of the linux kernal source installed (like it is installed but it is a mis-match
    for my version).

    That may be a repeat of things you've already heard, but those are the two things that nearly 100% bite me regularly. ;)


    * SLMR 2.1a * Only XT users know that January 1, 1980 was a Tuesday.
    --- SBBSecho 3.12-Linux
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)
  • From Joe Phigan@1:305/3 to Aaron Thomas on Mon Feb 8 20:59:04 2021
    On 07 Feb 2021, Aaron Thomas said the following...

    Anyone else have a suggestion for him? He upgraded Mint and it's no

    As of 20.04, Kubuntu uses the Plasma Desktop instead of KDE. It's pretty nice.

    --- Mystic BBS v1.12 A46 2020/03/02 (Windows/32)
    * Origin: 8-Bit Boyz BBS! -=[ bbs.8bitboyz.com port:6502 ]=- (1:305/3)
  • From Aaron Thomas@1:275/99 to Joe Phigan on Tue Feb 9 09:10:05 2021
    Anyone else have a suggestion for him? He upgraded Mint and it's no

    As of 20.04, Kubuntu uses the Plasma Desktop instead of KDE. It's pretty nice.

    Aren't Plasma & KDE the same thing?

    I installed Ubuntu with KDE and then everything is referred to as "Plasma."

    But yea, it sure is nice! Everything is easy to customize too.

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: CompuBBS | Ashburn VA | cfbbs.scinet-ftn.org (1:275/99)
  • From Richard Falken@1:123/115 to Aaron Thomas on Tue Feb 9 12:11:20 2021
    Re: Re: Linux Mint 20.1 issue
    By: Aaron Thomas to Joe Phigan on Tue Feb 09 2021 09:10 am

    Anyone else have a suggestion for him? He upgraded Mint and it's no

    As of 20.04, Kubuntu uses the Plasma Desktop instead of KDE. It's pretty nice.

    Aren't Plasma & KDE the same thing?

    I installed Ubuntu with KDE and then everything is referred to as "Plasma."

    But yea, it sure is nice! Everything is easy to customize too.

    There is some confussion because of one of those silly decisions regarding corporate branding.

    As of today, KDE is the name of the organization that develops the software. Plasma is the name of the desktop.


    --
    gopher://gopher.richardfalken.com/1/richardfalken
    --- SBBSecho 3.12-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)
  • From Mark Seifert@1:120/457 to Richard Falken on Tue Feb 9 15:11:39 2021
    Richard Falken said to mseifert <-

    Those are very generic needs.

    "Easy to update" discards Slackware, which is what I would usually recommend. It is not that it is "hard" to update but it is a bit more involved than apt-get upgrade.

    My next suggestion would be Debian or Devuan. There were some stats in
    the latter Linux Magazine issue from which I draw the conclussion that
    the Debian ecosystem is becoming the default in Desktops.

    If you need something more modern MX Linux is workable. I have an
    install around which I use for testing random stuff. I personally don't think that "easy to use" Debian derivatives have such a big of an edge compared to their daddy, at least nowadays, but I can see MX working
    for people familiar with Mints and *buntus.

    Just my two cents. In the end of the day people sticks with what feels better for them.

    Thanks, I like the fact that with *most* linux distros today they are pretty easy to use but still give me the terminal where I can create a .sh file to do things from the command line, like I used to do in Dos many many, many moons ago. If it wasn't for the fact that the "support" for it runs out I'd not bother with the idea of upgrading.. I like the way my Mint works.

    I'll have to look at MX or bite the bullet and go Ubunu, but will keep an eye on LM just incase they fix this issue.

    ... OK, I'm weird! But I'm saving up to become eccentric.
    ___ MultiMail/Linux v0.49

    --- Mystic BBS/QWK v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Communication Connection 1:120/457 (1:120/457)
  • From Mark Seifert@1:120/457 to Mike Powell on Tue Feb 9 15:55:10 2021
    Mike Powell said to mseifert <-

    Which is why I'm asking for help ... I SHOULD be able to resolve this.. damn
    ego.. down boy down...!!

    LOL, you've been at it about as long as I have (using linux, that is).

    When it happens to me, it usually means I am missing a prerequisite package for the package I am trying to compile, *OR* I don't have some part of the linux kernal source installed (like it is installed but it
    is a mis-match for my version).

    That may be a repeat of things you've already heard, but those are the
    two things that nearly 100% bite me regularly. ;)

    Thank you for your reply and not asking a question I've already answered, or sounding condescending, or asking first year support questions..

    For a while I though this echo was a friendly as a chili fart in an elevator.. So far most replies have been farts in the wind.

    I did find a temporary fix for the network cable issue, applied the suggested change and it fixed it until I did the updates... If they fix this before April great, if not I'll probably go to Ubuntu and leave Linux Mint behind.



    ... Boys will be boys, and so will a lot of middle-aged men.
    ___ MultiMail/Linux v0.49

    --- Mystic BBS/QWK v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Communication Connection 1:120/457 (1:120/457)
  • From Aaron Thomas@1:275/99 to Richard Falken on Tue Feb 9 13:42:39 2021
    As of today, KDE is the name of the organization that develops the software. Plasma is the name of the desktop.

    Thanks for that explanation. I think I installed it perhaps minutes before it got re-branded.

    --- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
    * Origin: CompuBBS | Ashburn VA | cfbbs.scinet-ftn.org (1:275/99)
  • From Joe Phigan@1:105/5 to Aaron Thomas on Thu Feb 11 01:36:50 2021
    I installed Ubuntu with KDE and then everything is referred to as "Plasma."

    KDE was a different window manager before. The new Plasma desktop took its place. I'm quite glad, because I hated old KDE. It always felt like it was
    held together by strings. I think it was loosely based on CDE, an old window manager for Solaris, which was much better.

    --- Mystic BBS v1.12 A47 2020/09/27 (Linux/64)
    * Origin: Mike's Mansion - Pdx,Or - mansion.dynv6.net:2323 (1:105/5)
  • From Andrew Alt@1:261/38 to Mark Seifert on Mon Mar 1 11:53:10 2021
    Mark Seifert wrote to All <=-

    Hey all,

    I have been a user of both Windows and Linux/Unix for a while.. I have
    2 questions..

    1) Any one possibly tell me why everytime I try to "make" I get errors, snap, flatpack, appimage, .deb and rpm work fine but if I have to try
    to "make" it fails. Any suggestions..?

    Can you try it with this small program I maintain?

    https://remove-to-waste.info/

    It should only take a few seconds to build. If it fails to build, please post the
    output from make and we'll see if we can pinpoint the cause.

    --
    -Andy


    ... DalekDOS v(overflow): (I)Obey (V)ision impaired (E)xterminate
    -+- MultiMail/Linux v0.52

    --- BBBS/Li6 v4.10 Toy-5
    * Origin: Prism bbs (1:261/38)
  • From Maurice Kinal@1:153/7001 to Andrew Alt on Mon Mar 1 17:54:39 2021
    -={ 2021-03-01 17:54:39.246915930+00:00 }=-

    Hey Andrew!

    It should only take a few seconds to build.

    # time make -j6
    real 0m0.197s
    user 0m0.728s
    sys 0m0.090s

    Under 2 milliseconds.

    If it fails to build, please post the output from make and we'll
    see if we can pinpoint the cause.

    Even though it successfully compiled here is the output anyhow;

    -={ output from 'make -j6 &> results.txt' starts }=-
    Making all in src
    make[1]: Entering directory '/mnt/archives/git-schtuff/rmw/src'
    make all-am
    make[2]: Entering directory '/mnt/archives/git-schtuff/rmw/src'
    CC globals.o
    CC main.o
    CC restore_rmw.o
    CC config_rmw.o
    CC parse_cli_options.o
    CC strings_rmw.o
    CC purging_rmw.o
    restore_rmw.c: In function 'restore':
    restore_rmw.c:76:38: warning: '%s' directive output may be truncated writing up to 8 bytes into a region of size between 1 and 4097 [-Wformat-truncation=]
    76 | snprintf (file.info, req_len, "%s%s%s%s", file.relative_path, file.relative_info_path,
    | ^~ ~~~~~~~~~~~~~~~~~~~~~~~
    restore_rmw.c:76:5: note: 'snprintf' output 11 or more bytes (assuming 4115) into a destination of size 4097
    76 | snprintf (file.info, req_len, "%s%s%s%s", file.relative_path, file.relative_info_path,
    | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    77 | file.base_name, TRASHINFO_EXT);
    | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    CC messages_rmw.o
    CC time_rmw.o
    CC trashinfo_rmw.o
    CC utils_rmw.o
    CC bst.o
    utils_rmw.c: In function 'human_readable_size':
    utils_rmw.c:143:44: warning: ' B' directive output may be truncated writing 2 bytes into a region of size between 0 and 19 [-Wformat-truncation=]
    143 | snprintf (buffer, sizeof (buffer), "%ld B", (long) size);
    | ^~
    utils_rmw.c:143:5: note: 'snprintf' output between 4 and 23 bytes into a destination of size 20
    143 | snprintf (buffer, sizeof (buffer), "%ld B", (long) size);
    | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ utils_rmw.c:140:44: warning: '.' directive output may be truncated writing 1 byte into a region of size between 0 and 19 [-Wformat-truncation=]
    140 | snprintf (buffer, sizeof (buffer), "%ld.%d %ciB", (long) size,
    | ^
    utils_rmw.c:140:40: note: directive argument in the range [-320, 319]
    140 | snprintf (buffer, sizeof (buffer), "%ld.%d %ciB", (long) size,
    | ^~~~~~~~~~~~~
    utils_rmw.c:140:5: note: 'snprintf' output between 8 and 30 bytes into a destination of size 20
    140 | snprintf (buffer, sizeof (buffer), "%ld.%d %ciB", (long) size,
    | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    141 | (remainder * 10) / 1024, prefix[power]);
    | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    CCLD ../rmw
    make[2]: Leaving directory '/mnt/archives/git-schtuff/rmw/src'
    make[1]: Leaving directory '/mnt/archives/git-schtuff/rmw/src'
    Making all in man
    make[1]: Entering directory '/mnt/archives/git-schtuff/rmw/man'
    make[1]: Nothing to be done for 'all'.
    make[1]: Leaving directory '/mnt/archives/git-schtuff/rmw/man'
    Making all in test
    make[1]: Entering directory '/mnt/archives/git-schtuff/rmw/test'
    make[1]: Nothing to be done for 'all'.
    make[1]: Leaving directory '/mnt/archives/git-schtuff/rmw/test'
    Making all in po
    make[1]: Entering directory '/mnt/archives/git-schtuff/rmw/po'
    make[1]: Nothing to be done for 'all'.
    make[1]: Leaving directory '/mnt/archives/git-schtuff/rmw/po'
    make[1]: Entering directory '/mnt/archives/git-schtuff/rmw'
    make[1]: Nothing to be done for 'all-am'.
    make[1]: Leaving directory '/mnt/archives/git-schtuff/rmw'
    -={ output from 'make -j6 &> results.txt' ends }=-

    # ldd rmw | tr -d '\t'
    linux-vdso.so.1 (0x00007ffd877dd000)
    libmenuw.so.6 => /usr/lib/libmenuw.so.6 (0x00007fc8becea000)
    libncursesw.so.6 => /lib/libncursesw.so.6 (0x00007fc8bec8f000)
    libc.so.6 => /lib/libc.so.6 (0x00007fc8beb09000)
    /lib/ld-linux-x86-64.so.2 (0x00007fc8becf5000)

    # file rmw
    rmw: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, not stripped

    The above was done on my custom pure 64-bit nondistribution rootfs (aka motorshed) using gcc-10.2.0/glibc-2.33 and friends.

    Does this help any?

    Life is good,
    Maurice

    ... Ich habe Eichhörnchen in meiner Hose!
    --- GNU bash, version 5.1.4(1)-release (x86_64-motorshed-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Andrew Alt@1:261/38 to Maurice Kinal on Wed Mar 3 11:15:20 2021
    Maurice Kinal wrote to Andrew Alt <=-

    -={ 2021-03-01 17:54:39.246915930+00:00 }=-

    Hey Andrew!

    The above was done on my custom pure 64-bit nondistribution rootfs (aka motorshed) using gcc-10.2.0/glibc-2.33 and friends.

    Does this help any?

    Hi, Maurice!

    On Debian with gcc 8 I wasn't getting any warnings. So.. that reminds me I might have
    to make some changes to get rid of those warnings. :) I'm not really sure of the best
    way to fix those though. I have mixed feelings about using snprintf(). I have redundant checks in place to check string lengths before concatenating, and I don't
    want strings to just get truncated. rmw is designed to exit (without a segfault) with
    a message if a buffer overflow is attempted. I think I should just change all my
    snprintf() statements to sprintf()... Which probably won't fix the warnings you

    mentioned, lol ;)


    I can get even more if I use CFLAGS="-Wformat -Wstringop-truncation -Wformat-overflow=2 -pedantic -Wextra -Wformat-truncation=2" :)

    Any suggestions? Probably if don't set fixed lengths in the structures and instead
    use calloc() at the time when I concatenate and write the final string, that would
    get rid of some of these annoying messages I get when I use the flags mentioned

    above. Seems like that would require a lot of extra manual memory management though.
    Things are working fine right now so I'm reluctant to change the code until I really
    understand well how best to fix those warnings.

    CC main.o
    ../../rmw/src/main.c: In function Γ  remove_to_wasteΓ ╓: ../../rmw/src/main.c:422:101: warning: Γ  %sΓ ╓ directive output between 0 and 4096 bytes may exceed minimum required size of 4095 [-Wformat-truncation=]
    tf (st_file_properties.waste_dest_name, sizeof (st_file_properties.waste_dest_name), "%s%s",

    ^~

    ../../rmw/src/main.c:422:100: note: assuming directive output of 1 byte
    tf (st_file_properties.waste_dest_name, sizeof (st_file_properties.waste_dest_name), "%s%s",

    ^~~~~~

    ../../rmw/src/main.c:422:9: note: Γ  snprintfΓ ╓ output 1 or more bytes (assuming 4098) into a destination of size 4097
    snprintf (st_file_properties.waste_dest_name, sizeof (st_file_properties.waste_dest_name), "%s%s",

    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~
    waste_curr->files, st_file_properties.base_name);
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    CC restore_rmw.o
    ../../rmw/src/restore_rmw.c: In function Γ  restoreΓ ╓: ../../rmw/src/restore_rmw.c:72:47: warning: Γ  %sΓ ╓ directive output between 0 and 4096 bytes may exceed minimum required size of 4095 [-Wformat-truncation=]
    snprintf (file.info, sizeof (file.info), "%s%s%s%s", file.relative_path, file.relative_info_path,
    ^~ ~~~~~~~~~~~~~~~~~~ ../../rmw/src/restore_rmw.c:72:46: note: assuming directive output of 1 byte
    snprintf (file.info, sizeof (file.info), "%s%s%s%s", file.relative_path, file.relative_info_path,
    ^~~~~~~~~~ ../../rmw/src/restore_rmw.c:72:5: note: Γ  snprintfΓ ╓ output 11 or more bytes (assuming 4116) into a destination of size 4097
    snprintf (file.info, sizeof (file.info), "%s%s%s%s", file.relative_path, file.relative_info_path,

    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~
    file.base_name, TRASHINFO_EXT);
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ../../rmw/src/restore_rmw.c: In function Γ  restore_selectΓ ╓: ../../rmw/src/restore_rmw.c:364:59: warning: Γ  %sΓ ╓ directive output between 0 and 4096 bytes may exceed minimum required size of 4095 [-Wformat-truncation=]
    snprintf (recover_file, sizeof (recover_file), "%s%s", waste_curr->files, item_name (items[i]));
    ^~ ../../rmw/src/restore_rmw.c:364:58: note: assuming directive output of 1 byte
    snprintf (recover_file, sizeof (recover_file), "%s%s", waste_curr->files, item_name (items[i]));
    ^~~~~~ ../../rmw/src/restore_rmw.c:364:11: note: Γ  snprintfΓ ╓ output 1 or more bytes (assuming 4098) into a destination of size 4097
    snprintf (recover_file, sizeof (recover_file), "%s%s", waste_curr->files, item_name (items[i]));

    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~
    ../../rmw/src/restore_rmw.c:244:38: warning: Γ  %sΓ ╓ directive output between 0 and 4096 bytes may exceed minimum required size of 4095 [-Wformat-truncation=]
    snprintf (full_path, req_len, "%s%s", waste_curr->files, entry->d_name);
    ^~
    CC config_rmw.o
    ../../rmw/src/config_rmw.c: In function Γ  parse_line_wasteΓ ╓: ../../rmw/src/config_rmw.c:306:42: warning: Γ  %sΓ ╓ directive output between 0 and 4096 bytes may exceed minimum required size of 4095 [-Wformat-truncation=]
    snprintf (waste_curr->files, req_len, "%s%s", waste_curr->parent, "/files/");
    ^~
    ../../rmw/src/config_rmw.c:324:41: warning: Γ  %sΓ ╓ directive output between 0 and 4096 bytes may exceed minimum required size of 4095 [-Wformat-truncation=]
    snprintf (waste_curr->info, req_len, "%s%s", waste_curr->parent, "/info/");
    ^~
    CC parse_cli_options.o
    CC strings_rmw.o
    CC purging_rmw.o
    ../../rmw/src/purging_rmw.c: In function Γ  purgeΓ ╓: ../../rmw/src/purging_rmw.c:332:18: warning: Γ  %sΓ ╓ directive output between 0 and 4096 bytes may exceed minimum required size of 4095 [-Wformat-truncation=]
    "%s%s", waste_curr->info, st_trashinfo_dir_entry->d_name);
    ^~
    ../../rmw/src/purging_rmw.c: In function Γ  orphan_maintΓ ╓: ../../rmw/src/purging_rmw.c:562:46: warning: Γ  %sΓ ╓ directive output between 0 and 4096 bytes may exceed minimum required size of 4095 [-Wformat-truncation=]
    snprintf (path_to_trashinfo, req_len, "%s%s%s", waste_curr->info,
    ^~ ../../rmw/src/purging_rmw.c:562:45: note: assuming directive output of 1 byte
    snprintf (path_to_trashinfo, req_len, "%s%s%s", waste_curr->info,
    ^~~~~~~~ ../../rmw/src/purging_rmw.c:574:57: warning: Γ  %sΓ ╓ directive output between 0 and 4096 bytes may exceed minimum required size of 4095 [-Wformat-truncation=]
    snprintf (st_file_properties.real_path, req_len, "%s%s%s",
    ^~ ../../rmw/src/purging_rmw.c:574:56: note: assuming directive output of 1 byte
    snprintf (st_file_properties.real_path, req_len, "%s%s%s",
    ^~~~~~~~
    CC messages_rmw.o
    CC time_rmw.o
    CC trashinfo_rmw.o
    ../../rmw/src/trashinfo_rmw.c:31:36: warning: initializer element is not a constant expression [-Wpedantic]
    const int LEN_MAX_TRASHINFO_LINE = (PATH_MAX * 3 + strlen ("Path=") + 1);
    ^
    ../../rmw/src/trashinfo_rmw.c: In function Γ  create_trashinfoΓ ╓: ../../rmw/src/trashinfo_rmw.c:47:40: warning: Γ  %sΓ ╓ directive output between 0 and 4096 bytes may exceed minimum required size of 4095 [-Wformat-truncation=]
    snprintf (final_info_dest, req_len, "%s%s", waste_curr->info, st_f_props->base_name);
    ^~
    ../../rmw/src/trashinfo_rmw.c:47:39: note: assuming directive output of 1 byte
    snprintf (final_info_dest, req_len, "%s%s", waste_curr->info, st_f_props->base_name);
    ^~~~~~
    CC utils_rmw.o
    ../../rmw/src/utils_rmw.c: In function Γ  unescape_urlΓ ╓: ../../rmw/src/utils_rmw.c:317:35: warning: format Γ  %hhxΓ ╓ expects argument of type Γ  unsigned char *Γ ╓, but argument 3 has type Γ  char *Γ ╓ [-Wformat=]
    sscanf (str + pos_str, "%2hhx", dest + pos_dest);
    ~~~~^ ~~~~~~~~~~~~~~~
    %2hhx
    ../../rmw/src/utils_rmw.c: In function Γ  human_readable_sizeΓ ╓: ../../rmw/src/utils_rmw.c:143:44: warning: Γ   BΓ ╓ directive output may be truncated writing 2 bytes into a region of size between 0 and 19 [-Wformat-truncation=]
    snprintf (buffer, sizeof (buffer), "%ld B", (long) size);
    ^~
    ../../rmw/src/utils_rmw.c:143:5: note: Γ  snprintfΓ ╓ output between 4 and 23 bytes into a destination of size 20
    snprintf (buffer, sizeof (buffer), "%ld B", (long) size);
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ../../rmw/src/utils_rmw.c:140:44: warning: Γ  .Γ ╓ directive output may be truncated writing 1 byte into a region of size between 0 and 19 [-Wformat-truncation=]
    snprintf (buffer, sizeof (buffer), "%ld.%d %ciB", (long) size,
    ^
    ../../rmw/src/utils_rmw.c:140:5: note: Γ  snprintfΓ ╓ output between 8 and 37 bytes into a destination of size 20
    snprintf (buffer, sizeof (buffer), "%ld.%d %ciB", (long) size,
    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    (remainder * 10) / 1024, prefix[power]);
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    CC bst.o
    CCLD ../rmw

    --
    -Andy


    ... A few feathers short of a whole duck.
    -+- MultiMail/Linux v0.52

    --- BBBS/Li6 v4.10 Toy-5
    * Origin: Prism bbs (1:261/38)
  • From Maurice Kinal@1:153/7001 to Andrew Alt on Wed Mar 3 16:41:54 2021
    -={ 2021-03-03 16:41:54.152677967+00:00 }=-

    Hey Andrew!

    On Debian with gcc 8 I wasn't getting any warnings.

    No surprise here. Of all the different versions of gcc over the years gcc 4 was my favourite. That was the last release I was able to stick with pure C. Almost everything has gone downhill since.

    Any suggestions?

    Other than sticking with what you feel comfortable with, no. It works here despite the warnings so you don't really have much to sweat.

    Things are working fine right now so I'm reluctant to change the
    code until I really understand well how best to fix those
    warnings.

    An excellent plan.

    Right now I am wrestling with the rustc/firefox breakage and whether or not to continue on this latest so-called upgrade into extreme overbloating of something I never ever cared about (ie gui/web crap).

    Kis these days eh? :::sigh:::

    Life is good,
    Maurice

    ... Monig mon hæfð micel feax on foran heafde, 7 wyrð færlice calu.
    Many a man has plenty of hair on his head, and suddenly goes bald.
    --- GNU bash, version 5.1.4(1)-release (x86_64-motorshed-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Andrew Alt@1:261/38 to Maurice Kinal on Fri Mar 5 19:51:02 2021
    Maurice Kinal wrote to Andrew Alt <=-

    -={ 2021-03-03 16:41:54.152677967+00:00 }=-

    Hey Andrew!

    On Debian with gcc 8 I wasn't getting any warnings.

    No surprise here. Of all the different versions of gcc over the years
    gcc 4 was my favourite. That was the last release I was able to stick with pure C. Almost everything has gone downhill since.

    Any suggestions?

    Other than sticking with what you feel comfortable with, no. It works here despite the warnings so you don't really have much to sweat.

    That's great. Thank you for trying it out and for the feedback. And for the reminder not to look for problems when there aren't any. ;) I certainly don't need
    to sweat any more than I already do!

    Right now I am wrestling with the rustc/firefox breakage and whether or not to continue on this latest so-called upgrade into extreme
    overbloating of something I never ever cared about (ie gui/web crap).

    Is the breakage related to the release of rust 2021 or something else?

    Have a great weekend, Maurice... :) Always nice to chat with you...


    --
    -Andy


    ... I am not Paul.
    -+- MultiMail/Linux v0.52

    --- BBBS/Li6 v4.10 Toy-5
    * Origin: Prism bbs (1:261/38)
  • From Maurice Kinal@1:153/7001 to Andrew Alt on Sat Mar 6 01:52:51 2021
    -={ 2021-03-06 01:52:51.262321332+00:00 }=-

    Hey Andrew!

    Thank you for trying it out and for the feedback.

    I had the feeling that is what you were really fishing for in your original post. ;-)

    And for the reminder not to look for problems when there aren't
    any.

    Yep. I hear you there, especially when there are real problems that are getting ignored. :::shrugging shoulders:::

    Is the breakage related to the release of rust 2021 or something
    else?

    Right now I am using rustc-1.50.0, which I believe to be the latest and greatest, but the breakage in firefox happened earlier. I suspect firefox to be the culprit given that what little else I am using that requires rust are doing fine. The last successful firefox build was firefox-78.0.2esr but I don't recall which rust although rustc-1.42-ish comes to mind. I can backtrack to find out for sure if it matters any. However my plan is to wait and see what happens before doing anything serious about it. I do have a working seamonkey-2.53.6 which doesn't have issues with rustc-1.50.0 so not all is lost ... yet. The trouble with firefox is that it isn't all that informative as to why it is crapping out when compiling.

    Anyhow, given that slackware-current is seeing the same problem and have yet to fix it tells me that backing off for awhile is probably the right idea for now.

    Have a great weekend, Maurice... :) Always nice to chat with
    you...

    Agreed. Take care of yourself and I am sure we will be chatting in the near future.

    Life is good,
    Maurice

    ... Hit byð dysig þæt man speca ær þone he þænce.
    It's foolish for a man to speak before he thinks.
    --- GNU bash, version 5.1.4(1)-release (x86_64-motorshed-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Benny Pedersen@2:230/0 to Maurice Kinal on Sun Mar 7 00:20:26 2021
    Hello Maurice!

    06 Mar 2021 01:52, Maurice Kinal wrote to Andrew Alt:

    Have a great weekend, Maurice... :) Always nice to chat with
    you...

    Agreed. Take care of yourself and I am sure we will be chatting in
    the near future.

    i recovered my sluckware :)

    blacklisted slackpkg update and kernel* updates, hope not to see it again with any breakage from precompiled problems


    Regards Benny

    ... too late to die young :)

    --- Msged/LNX 6.1.2 (Linux/5.11.3-gentoo-x86_64 (x86_64))
    * Origin: I will always keep a PC running CPM 3.0 (2:230/0)
  • From Maurice Kinal@1:153/7001 to Benny Pedersen on Sun Mar 7 00:50:25 2021
    -={ 2021-03-07 00:50:25.589378748+00:00 }=-

    Hey Benny!

    i recovered my sluckware :)

    A very good idea. Myself I am toying with the idea of installing slackware64-14.0 on a virtual drive and redoing it as a pure C, pure 64-bit nondistribution just for fun. Either that or doing something similar with the 15.0 alpha except in that case it will have to be C/C++. Either way {,usr}/lib64 has to go.

    blacklisted slackpkg update and kernel* updates, hope not to see
    it again with any breakage from precompiled problems

    I'll have to take your word on that as I've never used any of that before and have no plans to use it in the future. Everyone I know that uses slackware also builds their own kernel as the first step after booting to a fresh install.

    As for other distributions who cares?

    Life is good,
    Maurice

    ... Hærfest [byð] hreðeadegost, hæleðum bringeð geres wæstmas.
    Harvest is most glory-blessed; it brings to men the year's fruits.
    --- GNU bash, version 5.1.4(1)-release (x86_64-motorshed-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Benny Pedersen@2:230/0 to Maurice Kinal on Sun Mar 7 02:35:02 2021
    Hello Maurice!

    07 Mar 2021 00:50, Maurice Kinal wrote to Benny Pedersen:

    i recovered my sluckware :)

    A very good idea. Myself I am toying with the idea of installing slackware64-14.0 on a virtual drive and redoing it as a pure C, pure 64-bit nondistribution just for fun. Either that or doing something similar with the 15.0 alpha except in that case it will have to be
    C/C++. Either way {,usr}/lib64 has to go.

    if i just could compile amiga os 64bit, we wont be here :)

    blacklisted slackpkg update and kernel* updates, hope not to see
    it again with any breakage from precompiled problems

    I'll have to take your word on that as I've never used any of that
    before and have no plans to use it in the future. Everyone I know
    that uses slackware also builds their own kernel as the first step
    after booting to a fresh install.

    yes i belive slackware really need gentoo portage, not just precompile build converters to ebuilds from slackbuild scripts, its sad to see notes on blacklist what not to blacklist, was a hint on what to do if it breaks from 14.x to 15.x :)

    install this tarball, and do a ldconfig solved it for me, it have to be done fully without slackpkg in the first place, then after ldconfig all should work again

    then do the remaining part as

    slackpkg update

    edit mirror file and make sure we keep 64bit !!!!!

    slackpkg upgrade-all
    slackpkg install-new
    slackpkg clean-system

    if new kernel do

    lilo

    reboot

    As for other distributions who cares?

    gentoo is more simple :)


    Regards Benny

    ... too late to die young :)

    --- Msged/LNX 6.1.2 (Linux/5.11.3-gentoo-x86_64 (x86_64))
    * Origin: I will always keep a PC running CPM 3.0 (2:230/0)
  • From Maurice Kinal@1:153/7001 to Benny Pedersen on Sun Mar 7 03:36:35 2021
    -={ 2021-03-07 03:36:35.841743557+00:00 }=-

    Hey Benny!

    if i just could compile amiga os 64bit, we wont be here :)

    It's just pining for the fjørds.

    gentoo is more simple :)

    gentoo is okay but it isn't slackware.

    Life is good,
    Maurice

    ... Scyle monna gehwylc mid gemete healdan a wiþ leofne ond wið laþne.
    Every man should act with moderation both to friends and foes.
    --- GNU bash, version 5.1.4(1)-release (x86_64-motorshed-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Richard Falken@1:123/115 to Maurice Kinal on Sun Mar 7 03:46:05 2021
    Re: rmw compile warnings
    By: Maurice Kinal to Benny Pedersen on Sun Mar 07 2021 03:36 am

    -={ 2021-03-07 03:36:35.841743557+00:00 }=-

    Hey Benny!

    if i just could compile amiga os 64bit, we wont be here :)

    It's just pining for the fjørds.

    gentoo is more simple :)

    gentoo is okay but it isn't slackware.

    Life is good,
    Maurice

    ... Scyle monna gehwylc mid gemete healdan a wiþ leofne ond wið laþne.
    Every man should act with moderation both to friends and foes.

    Gentoo is cool but it is not simpler by any means.

    --
    gopher://gopher.richardfalken.com/1/richardfalken
    --- SBBSecho 3.12-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)
  • From Maurice Kinal@1:153/7001 to Richard Falken on Sun Mar 7 15:35:26 2021
    -={ 2021-03-07 15:35:26.546243552+00:00 }=-

    Hey Richard!

    Gentoo is cool but it is not simpler by any means.

    I think in the case of comparing linux distributions it is a relative term and often comes down to what an individual is familiar with. In my case I started with Slackware back in the mid 1990's which was before Gentoo and others even existed.

    Life is good,
    Maurice

    ... Eadig bið se þe in his eðle geþihð.
    Fortunate is he who prospers in his homeland.
    --- GNU bash, version 5.1.4(1)-release (x86_64-motorshed-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Benny Pedersen@2:230/0 to Maurice Kinal on Sun Mar 7 18:46:50 2021
    Hello Maurice!

    07 Mar 2021 03:36, Maurice Kinal wrote to Benny Pedersen:

    if i just could compile amiga os 64bit, we wont be here :)
    It's just pining for the fj|⌐rds.

    your cat typed that ? :)

    gentoo is more simple :)
    gentoo is okay but it isn't slackware.

    gentoo can use precompiled aswell if its needed, with slackware its just reversed in a bad way imho


    Regards Benny

    ... too late to die young :)

    --- Msged/LNX 6.1.2 (Linux/5.11.3-gentoo-x86_64 (x86_64))
    * Origin: I will always keep a PC running CPM 3.0 (2:230/0)
  • From Benny Pedersen@2:230/0 to Richard Falken on Sun Mar 7 18:48:38 2021
    Hello Richard!

    07 Mar 2021 03:46, Richard Falken wrote to Maurice Kinal:

    Gentoo is cool but it is not simpler by any means.

    how can i help then ?


    Regards Benny

    ... too late to die young :)

    --- Msged/LNX 6.1.2 (Linux/5.11.3-gentoo-x86_64 (x86_64))
    * Origin: I will always keep a PC running CPM 3.0 (2:230/0)
  • From Maurice Kinal@1:153/7001 to Benny Pedersen on Sun Mar 7 20:39:47 2021
    -={ 2021-03-07 20:39:47.870753969+00:00 }=-

    Hey Benny!

    your cat typed that ? :)

    Obviously my cat did a better job of it than you did with your so-called latin-1 defective reply. :::shame on you:::

    gentoo can use precompiled aswell if its needed, with slackware
    its just reversed in a bad way

    How so? They appear to have gone above and beyond what is called for and much sooner than the gentoo people did. If anything is reversed it would be whatever approach you and possibly gentoo itself is advocating as being the hallmark of a linux distribution.

    Life is good,
    Maurice

    ... Getreowan freond... deorweorðeste ðyng eallra þissa woruldgesælþa.
    True friends are the most precious of all this world's joys.
    --- GNU bash, version 5.1.4(1)-release (x86_64-motorshed-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)