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)

-={ 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)

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)

-={ 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)

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)

-={ 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)

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)

-={ 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)

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)

-={ 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)

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)

-={ 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)

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)

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)

-={ 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)