From Newsgroup: comp.os.linux.advocacy

The mantra of Linux development is "don't break user space."

It works. I have been using the same kernel configuration
and the same boot scripts for a LONG, LONG time without any
problems.

Torvalds and his cohorts are the best!

But GNU/Linux software programmers, it seems, don't follow
the same mantra.

Recently, ImageMagick and GMIC, both CLI image processing
programs that I use extensively, have changed some of their
commands and command options.

<https://imagemagick.org/>

<https://gmic.eu/>

Because of this, I am FORCED to modify literally HUNDREDS
of scripts that I have written in the past. Believe you me,
I have much better thing to do.

Bastards!

My advice to all GNU/Linux/FOSS programmers:

Don't fucking break the established commands and options!

Of course, distro lackeys couldn't give a fuck. They
will always have their pretty GUI buttons.

Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!

--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

Distro Lackey <[email protected]> news:18a745cbe5a613ab$28367$2332849$[email protected] Fri, 17 Apr 2026 22:35:20 GMT in comp.os.linux.advocacy, wrote:

Recently, ImageMagick and GMIC, both CLI image processing
programs that I use extensively, have changed some of their
commands and command options.

<https://imagemagick.org/>

<https://gmic.eu/>

Because of this, I am FORCED to modify literally HUNDREDS
of scripts that I have written in the past. Believe you me,
I have much better thing to do.

Hmm. Couldn't you write a search and replace tool to automate this process
for you?
--
Liar, lawyer; mirror show me, what's the difference?
Kangaroo done hung the guilty with the innocent
Liar, lawyer; mirror for ya', what's the difference?
Kangaroo be stoned. He's guilty as the government

--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

Gremlin <[email protected]> wrote:

Distro Lackey <[email protected]> news:18a745cbe5a613ab$28367$2332849$[email protected] Fri, 17 Apr 2026 22:35:20 GMT in comp.os.linux.advocacy, wrote:

Recently, ImageMagick and GMIC, both CLI image processing
programs that I use extensively, have changed some of their
commands and command options.

<https://imagemagick.org/>

<https://gmic.eu/>

Because of this, I am FORCED to modify literally HUNDREDS
of scripts that I have written in the past. Believe you me,
I have much better thing to do.

Hmm. Couldn't you write a search and replace tool to automate this process for you?

LOL! Didn’t you used to claim to be a coder or programmer?
--
Personal attacks from those who troll show their own insecurity. They
cannot use reason to show the message to be wrong so they try to feel
somehow superior by attacking the messenger.

They cling to their attacks and ignore the message time and time again.
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

Distro Lackey <[email protected]>wrote:

The mantra of Linux development is "don't break user space."

It works. I have been using the same kernel configuration
and the same boot scripts for a LONG, LONG time without any
problems.

Torvalds and his cohorts are the best!

But GNU/Linux software programmers, it seems, don't follow
the same mantra.

Recently, ImageMagick and GMIC, both CLI image processing
programs that I use extensively, have changed some of their
commands and command options.

<https://imagemagick.org/>

<https://gmic.eu/>

Because of this, I am FORCED to modify literally HUNDREDS
of scripts that I have written in the past. Believe you me,
I have much better thing to do.

Bastards!

My advice to all GNU/Linux/FOSS programmers:

Don't fucking break the established commands and options!

Of course, distro lackeys couldn't give a fuck. They
will always have their pretty GUI buttons.

Ha, ha, ha, ha, ha, ha, ha, ha, ha, ha, ha!

It was te same with gcc command like flags a while back.
Broke every program I released.
Some idiots, was no need for a change.

--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

On Sat, 18 Apr 2026 05:34:07 GMT, Jan Panteltje wrote:

It was te same with gcc command like flags a while back.

What exactly was changed?
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

Lawrence =?iso-8859-13?q?D=FFOliveiro?= <[email protected]d>wrote:

On Sat, 18 Apr 2026 05:34:07 GMT, Jan Panteltje wrote:

It was te same with gcc command like flags a while back.

What exactly was changed?

CFLAGS = -fcommon -O2 -Wall -D_FILE_OFFSET_BITS=64

Trying to remember
Was it to do with the -fcommon flag?

What basically happened is that all global variables declaired in a separate header C file
were no longer recognized, giving many compile errors.
As the make files were made with Imake more problems.

So had to edit all Makefiles
There was more shit with that, google shows

Much old code that I wrote for x86 ported to the raspberry pi had to be modified.
with that version of gcc.



--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

On Sat, 18 Apr 2026 02:10:06 -0000 (UTC), Gremlin wrote:

Hmm. Couldn't you write a search and replace tool to automate this process for you?

Hmm. But that's not the point, is it.

No, that's not the point. The issue is that I should not have
to do that because the programmers should not have to break things.


--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

On Sat, 18 Apr 2026 09:53:57 GMT, Jan Panteltje wrote:

Trying to remember
Was it to do with the -fcommon flag?

Good example!

The default was changed from "-fcommon" to "-fno-common."

<https://trofi.github.io/posts/245-fno-common-legacy.html>

--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

Brock McNuggets <[email protected]> wrote in news:69e301f7$0$21$[email protected]:

Gremlin <[email protected]> wrote:

Distro Lackey <[email protected]>
news:18a745cbe5a613ab$28367$2332849$[email protected]
Fri, 17 Apr 2026 22:35:20 GMT in comp.os.linux.advocacy, wrote:

Recently, ImageMagick and GMIC, both CLI image processing
programs that I use extensively, have changed some of their
commands and command options.

<https://imagemagick.org/>

<https://gmic.eu/>

Because of this, I am FORCED to modify literally HUNDREDS
of scripts that I have written in the past. Believe you me,
I have much better thing to do.

Hmm. Couldn't you write a search and replace tool to automate this
process for you?

LOL! Didn’t you used to claim to be a coder or programmer?

You do realize that what he wrote is a question?
Do you?
The giveaway is the "?" at the end of the sentence.
You seem to have reading difficulties. How old are you?

--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

On Sat, 18 Apr 2026 09:53:57 GMT, Jan Panteltje wrote:

Lawrence =?iso-8859-13?q?D=FFOliveiro?= <[email protected]d>wrote:

On Sat, 18 Apr 2026 05:34:07 GMT, Jan Panteltje wrote:

It was te same with gcc command like flags a while back.

What exactly was changed?

CFLAGS = -fcommon -O2 -Wall -D_FILE_OFFSET_BITS=64

Trying to remember Was it to do with the -fcommon flag?

What basically happened is that all global variables declaired in a
separate header C file were no longer recognized, giving many compile
errors.
As the make files were made with Imake more problems.

That was several years ago. Declaring variables in a header file was
never a good idea but changing the default was not a good idea either. I
had to change quite a few makefiles to get our legacy code to compile.

Fortunately there was a compiler flag. Finding all instances of 'foo' in
the various applications and picking one file in each to declare 'foo'
would have been a lot more work.



--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

On Apr 17, 2026 at 7:10:06 PM MST, "Gremlin" wrote <[email protected]>:

Distro Lackey <[email protected]> news:18a745cbe5a613ab$28367$2332849$[email protected] Fri, 17 Apr 2026 22:35:20 GMT in comp.os.linux.advocacy, wrote:

Recently, ImageMagick and GMIC, both CLI image processing
programs that I use extensively, have changed some of their
commands and command options.

<https://imagemagick.org/>

<https://gmic.eu/>

Because of this, I am FORCED to modify literally HUNDREDS
of scripts that I have written in the past. Believe you me,
I have much better thing to do.

Hmm. Couldn't you write a search and replace tool to automate this process for you?

The technical side of this was lost in the noise of insults (typical Usenet).

Gremlin’s suggestion is the ultimate "Hello, World!" take -- it's the kind of glib advice you get from someone who reads about coding but hasn’t actually lived in the trenches. An actual programmer knows that "just search and replace" is an unwise for a complex library like ImageMagick. If you’re naive enough to think a blind regex can handle an architectural shift without creating a thousand hard to trace bugs in the results, you aren't past the "script kiddie" level.

Bottom Line: A real programmer knows a program is a "sequence of intent". You can't fully automate the migration of intent with a "search and replace" tool. --
It's impossible for someone who is at war with themselves to be at peace with you.
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

Brock McNuggets <[email protected]> wrote in news:69e3cba2$0$25$[email protected]:

On Apr 17, 2026 at 7:10:06 PM MST, "Gremlin" wrote <[email protected]>:

Distro Lackey <[email protected]>
news:18a745cbe5a613ab$28367$2332849$[email protected]
Fri, 17 Apr 2026 22:35:20 GMT in comp.os.linux.advocacy, wrote:

Recently, ImageMagick and GMIC, both CLI image processing
programs that I use extensively, have changed some of their
commands and command options.

<https://imagemagick.org/>

<https://gmic.eu/>

Because of this, I am FORCED to modify literally HUNDREDS
of scripts that I have written in the past. Believe you me,
I have much better thing to do.

Hmm. Couldn't you write a search and replace tool to automate this
process for you?

The technical side of this was lost

on a functional idiot with poor reading comprehension skills like you
Brock McNuggets.
--

Rigor Mortis
Axe me a question.
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

On Apr 18, 2026 at 11:43:44 AM MST, "Rigor Mortis" wrote <69e3d0e0$0$25$[email protected]>:

Brock McNuggets <[email protected]> wrote in news:69e3cba2$0$25$[email protected]:

On Apr 17, 2026 at 7:10:06 PM MST, "Gremlin" wrote
<[email protected]>:

Distro Lackey <[email protected]>
news:18a745cbe5a613ab$28367$2332849$[email protected]
Fri, 17 Apr 2026 22:35:20 GMT in comp.os.linux.advocacy, wrote:

Recently, ImageMagick and GMIC, both CLI image processing
programs that I use extensively, have changed some of their
commands and command options.

<https://imagemagick.org/>

<https://gmic.eu/>

Because of this, I am FORCED to modify literally HUNDREDS
of scripts that I have written in the past. Believe you me,
I have much better thing to do.

Hmm. Couldn't you write a search and replace tool to automate this
process for you?

The technical side of this was lost in the noise of insults (typical Usenet).

Gremlin’s suggestion is the ultimate "Hello, World!" take -- it's the kind of
glib advice you get from someone who reads about coding but hasn’t actually
lived in the trenches. An actual programmer knows that "just search and
replace" is an unwise for a complex library like ImageMagick. If you’re naive
enough to think a blind regex can handle an architectural shift without
creating a thousand hard to trace bugs in the results, you aren't past the >> "script kiddie" level.

Bottom Line: A real programmer knows a program is a "sequence of intent". You
can't fully automate the migration of intent with a "search and replace" tool.

You could have just said the above went over your head. :)

on a functional idiot with poor reading comprehension skills like you
Brock McNuggets.

--
It's impossible for someone who is at war with themselves to be at peace with you.
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

On Sat, 18 Apr 2026 09:53:57 GMT, Jan Panteltje wrote:

On Sat, 18 Apr 2026 07:03:54 -0000 (UTC), Lawrence D’Oliveiro wrote:

On Sat, 18 Apr 2026 05:34:07 GMT, Jan Panteltje wrote:

It was te same with gcc command like flags a while back.

What exactly was changed?

CFLAGS = -fcommon -O2 -Wall -D_FILE_OFFSET_BITS=64

Trying to remember
Was it to do with the -fcommon flag?

What basically happened is that all global variables declaired in a
separate header C file were no longer recognized, giving many
compile errors.

From
<https://gcc.gnu.org/onlinedocs/gcc-15.2.0/gcc/Code-Gen-Options.html>:

The default is -fno-common, which specifies that the compiler
places uninitialized global variables in the BSS section of the
object file. This inhibits the merging of tentative definitions by
the linker so you get a multiple-definition error if the same
variable is accidentally defined in more than one compilation
unit.

The setting “-fcommon” makes global variables behave like Fortran
COMMON blocks, which I think is how K&R C did it. If there was a
change in the default setting, I suspect it didn’t happen in this
century.
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

On Sat, 18 Apr 2026 22:33:28 -0000 (UTC), Lawrence D’Oliveiro wrote:

The setting “-fcommon” makes global variables behave like Fortran
COMMON blocks, which I think is how K&R C did it. If there was a
change in the default setting, I suspect it didn’t happen in this
century.

The Kiwi cocksucker makes his idiocy known again.

Now LISTEN, fucking ignoramus.

GCC changed the default which caused lots of problems.

Now get back into your lackey armchair and shut the fuck up.

--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

On Sat, 18 Apr 2026 22:33:28 -0000 (UTC), Lawrence D’Oliveiro wrote:

The setting “-fcommon” makes global variables behave like Fortran COMMON blocks, which I think is how K&R C did it. If there was a change in the default setting, I suspect it didn’t happen in this century.

Your suspicion is incorrect.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85678


David Brown 2020-07-22 13:12:16 UTC
This has been implemented in gcc 10, and -fno-common is now the default.
This "bug" can presumably now be closed.

Many thanks to the gcc developers here.


You can follow the entire discussion. When I installed Debian Bullseye
that used gcc 10 I had to modify the makefiles.
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

rbowman <[email protected]>wrote:

On Sat, 18 Apr 2026 09:53:57 GMT, Jan Panteltje wrote:

Lawrence =?iso-8859-13?q?D=FFOliveiro?= <[email protected]d>wrote:

On Sat, 18 Apr 2026 05:34:07 GMT, Jan Panteltje wrote:

It was te same with gcc command like flags a while back.

What exactly was changed?

CFLAGS = -fcommon -O2 -Wall -D_FILE_OFFSET_BITS=64

Trying to remember Was it to do with the -fcommon flag?

What basically happened is that all global variables declaired in a
separate header C file were no longer recognized, giving many compile
errors.
As the make files were made with Imake more problems.

That was several years ago. Declaring variables in a header file was
never a good idea

Well have been doing that since moving to Linux around 1993 with Soft Landing System Linux
https://en.wikipedia.org/wiki/Softlanding_Linux_System
Never a problem.
To change a default and fucking up more than 20 years of other peoples code / releases
because you gcc tinkerers have no clue and never wrote code yourself is a crime!
I refuse to make new releases of my code, you idiots fix gcc!

And it is not only gcc, many 'maintainers' screw up things, libraries.
On top of that all the various silly distros and systems and stuff
useless crap like dbus...
Mostly because they cannot really code and this is their first go at it and so screw up good things.

Maybe just ask AI to write code that does what you want.
But then 'What do you want?' the clueless could not even think about flying
as we were heavier than birds..
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

On Sun, 19 Apr 2026 06:57:52 GMT, Jan Panteltje wrote:

I refuse to make new releases of my code, you idiots fix gcc!

Does your code work with other compilers, like clang?

Maybe you shouldn’t be putting all your eggs in the GCC basket.
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

Lawrence =?iso-8859-13?q?D=FFOliveiro?= <[email protected]d>wrote:

On Sun, 19 Apr 2026 06:57:52 GMT, Jan Panteltje wrote:

I refuse to make new releases of my code, you idiots fix gcc!

Does your code work with other compilers, like clang?

It is C code, wokrs with original gcc

Maybe you shouldn’t be putting all your eggs in the GCC basket.

I once wrote my own Z80 CP/M clone. in asm,
designed and build the hardware too:
https://panteltje.nl/panteltje/z80/index.html

And I once wrote my own multitasker in C just for fun.

Coding in asm is fun too:
https://panteltje.nl/panteltje/pic/index.html
at least you have to know about bits and hardware

And lots of C stuff,
https://panteltje.nl/panteltje/newsflex/download.html

including this NewsFleX Usenet newsreader I am posting this with, from a Raspberry Pi4
yes compiled with that gcc flag.

You will have to modifiy the NewsFleX makefile after downloading the tgz for it to compile,
likely also for several other releases on my site.

Old saying:
If it works do not fix it

Take note gcc tinkerers!!!


I was in electronics since the fifties... at work since the eighties.
Almost 80 years old now.

Changing gcc is like changing the mains voltage
:-)



--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

On Sun, 19 Apr 2026 07:19:44 GMT, Jan Panteltje wrote:

On Sun, 19 Apr 2026 07:02:18 -0000 (UTC), Lawrence D’Oliveiro wrote:

On Sun, 19 Apr 2026 06:57:52 GMT, Jan Panteltje wrote:

I refuse to make new releases of my code, you idiots fix gcc!

Does your code work with other compilers, like clang?

It is C code, wokrs with original gcc

But if you insist on GCC being the arbiter of what is C code, then if
your code doesn’t compile with GCC any more, then you must concede
that, by your own criteria, it is no longer actually C code, mustn’t
you?
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

W dniu 18.04.2026 o 00:35, Distro Lackey pisze:

Recently, ImageMagick and GMIC, both CLI image processing
programs that I use extensively, have changed some of their
commands and command options.

<https://imagemagick.org/>

<https://gmic.eu/>

Because of this, I am FORCED to modify literally HUNDREDS
of scripts that I have written in the past.

This is the way Linux roling distros works. Nothing new nor unusual.
--
Jacek Marcin Jaworski, Pruszcz Gd., woj. Pomorskie, Polska 🇵🇱, EU 🇪🇺;
tel.: +48-609-170-742, najlepiej w godz.: 5:00-5:55 lub 16:00-17:25; <[email protected]>, gpg: 4A541AA7A6E872318B85D7F6A651CC39244B0BFA;
Domowa s. WWW: <https://energokod.gda.pl>;
Mini Netykieta: <https://energokod.gda.pl/MiniNetykieta.html>;
Mailowa Samoobrona: <https://emailselfdefense.fsf.org/pl>.
UWAGA:
NIE ZACIĄGAJ "UKRYTEGO DŁUGU"! PŁAĆ ZA PROG. FOSS I INFO. INTERNETOWE! CZYTAJ DARMOWY: "17. Raport Totaliztyczny - Patroni Kontra Bankierzy": <https://energokod.gda.pl/raporty-totaliztyczne/17.%20Patroni%20Kontra%20Bankierzy.pdf>

--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

On 2026/4/17 6:35 PM, Distro Lackey wrote:

The mantra of Linux development is "don't break user space."

It works. I have been using the same kernel configuration
and the same boot scripts for a LONG, LONG time without any
problems.

Torvalds and his cohorts are the best!

But GNU/Linux software programmers, it seems, don't follow
the same mantra.

Recently, ImageMagick and GMIC, both CLI image processing
programs that I use extensively, have changed some of their
commands and command options.

<https://imagemagick.org/>

<https://gmic.eu/>

Because of this, I am FORCED to modify literally HUNDREDS
of scripts that I have written in the past. Believe you me,
I have much better thing to do.

If you have "better things to do", why are you running Linux?

For someone who claims to be a great programmer, you sure do whine a lot
when you have to do some actual programming. Yes, maintenance IS
actual programming.

A few months ago you wanted Intel to hold your hand because you had so
much trouble installing their C compiler.

I have news for you. Are you sitting down? Linux is written BY
programmers FOR programmers. Its all about "being in control". Its a
"way of life". Its a "total philosophy".

Do you remember all of that? Well, "being in control" means you
sometimes have to manually fix broken shit.

Do you want some cheese to go with that whine? Suck it up, buttercup.

Distro Lackey indeed.
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

Lawrence =?iso-8859-13?q?D=FFOliveiro?= <[email protected]d>wrote:

On Sun, 19 Apr 2026 07:19:44 GMT, Jan Panteltje wrote:

On Sun, 19 Apr 2026 07:02:18 -0000 (UTC), Lawrence D’Oliveiro wrote:

On Sun, 19 Apr 2026 06:57:52 GMT, Jan Panteltje wrote:

I refuse to make new releases of my code, you idiots fix gcc!

Does your code work with other compilers, like clang?

No idea, I have used the C80 compiler for Z80 systems in the past.

It is C code, wokrs with original gcc

But if you insist on GCC being the arbiter of what is C code, then if
your code doesn’t compile with GCC any more, then you must concede
that, by your own criteria, it is no longer actually C code, mustn’t
you?

Have you ever read
https://en.wikipedia.org/wiki/The_C_Programming_Language
?
Arbiter!

If nothing works I write it in asm
Done a lot of asm coding, also for x86.


I am quite sure that any decent C compiler will work with my code.
Fucking up command line switches for the millions of coders and programs written in C is stupid

The whole issue is 'know the hardware'
Lots of programs are bloat linking in huge libraries, what not. to do the simplest things.
But C (and C libraries) has a high portability from one hardware system to the other,
so that is a plus.
I did not like the move to Alsa either, had written a lot of multi-channel audio C code for the old system,

It is all so silly, most things seem to have been added just to facilitate more advertising

Else ask AI to write the code!
I was just testing deepseek.com today, asked it to write a simple C program that writes 'Hello World'
Result was OK!




--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

On Sun, 19 Apr 2026 07:02:18 -0000 (UTC), Lawrence D’Oliveiro wrote:

On Sun, 19 Apr 2026 06:57:52 GMT, Jan Panteltje wrote:

I refuse to make new releases of my code, you idiots fix gcc!

Does your code work with other compilers, like clang?

Maybe you shouldn’t be putting all your eggs in the GCC basket.

The code compiled Windows using CL.exe. It wasn't until gcc 10 that a maintainer decided to make no-common the default. I do not know if the
flag was there in the 1987 gcc 1.0 release but common was the default
until 2020.

Since the code built on AIX until we phased out those releases XL
presumably defaulted to common too.

--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

On Sun, 19 Apr 2026 14:00:59 GMT, Jan Panteltje wrote:

On Sun, 19 Apr 2026 07:44:36 -0000 (UTC), Lawrence D’Oliveiro wrote:

On Sun, 19 Apr 2026 07:19:44 GMT, Jan Panteltje wrote:

On Sun, 19 Apr 2026 07:02:18 -0000 (UTC), Lawrence D’Oliveiro wrote:

On Sun, 19 Apr 2026 06:57:52 GMT, Jan Panteltje wrote:

I refuse to make new releases of my code, you idiots fix gcc!

Does your code work with other compilers, like clang?

No idea, I have used the C80 compiler for Z80 systems in the past.

It is C code, wokrs with original gcc

But if you insist on GCC being the arbiter of what is C code, then
if your code doesn’t compile with GCC any more, then you must
concede that, by your own criteria, it is no longer actually C
code, mustn’t you?

I am quite sure that any decent C compiler will work with my code.

Have you actually confirmed that?
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

On Sun, 19 Apr 2026 09:56:54 -0400, Nick Charles wrote:

Linux is written BY programmers FOR programmers.

Do you want to tell Apple that? Because they are now embracing it. You
don’t want actual “programmers” to be attracted to the Mac platform
now, do you?

Do you remember all of that? Well, "being in control" means you
sometimes have to manually fix broken shit.

“Shit” would seem to be a more apt description for the platforms that
are currently undergoing enshittification. Which we all know don’t
include Linux. Because Linux users have a choice, while the users of
those other platforms can complain all they like, their platform
owners don’t have to take any notice.
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

Phil Da' Lick <[email protected]> wrote:

Brock McNuggets <[email protected]> wrote in news:69e301f7$0$21$[email protected]:

Gremlin <[email protected]> wrote:

Distro Lackey <[email protected]>
news:18a745cbe5a613ab$28367$2332849$[email protected]
Fri, 17 Apr 2026 22:35:20 GMT in comp.os.linux.advocacy, wrote:

Recently, ImageMagick and GMIC, both CLI image processing
programs that I use extensively, have changed some of their
commands and command options.

<https://imagemagick.org/>

<https://gmic.eu/>

Because of this, I am FORCED to modify literally HUNDREDS
of scripts that I have written in the past. Believe you me,
I have much better thing to do.

Hmm. Couldn't you write a search and replace tool to automate this
process for you?

LOL! Didn’t you used to claim to be a coder or programmer?

You do realize that what he wrote is a question?

What made you question this?

Do you?
The giveaway is the "?" at the end of the sentence.

Good to see you share your current growth. You’re learning!

You seem to have reading difficulties. How old are you?

You’re the only one struggling to understand the meaning of the question mark.
--
Personal attacks from those who troll show their own insecurity. They
cannot use reason to show the message to be wrong so they try to feel
somehow superior by attacking the messenger.

They cling to their attacks and ignore the message time and time again.
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

rbowman <[email protected]>wrote:

On Sun, 19 Apr 2026 07:02:18 -0000 (UTC), Lawrence D’Oliveiro wrote:

On Sun, 19 Apr 2026 06:57:52 GMT, Jan Panteltje wrote:

I refuse to make new releases of my code, you idiots fix gcc!

Does your code work with other compilers, like clang?

Maybe you shouldn’t be putting all your eggs in the GCC basket.

The code compiled Windows using CL.exe. It wasn't until gcc 10 that a >maintainer decided to make no-common the default. I do not know if the
flag was there in the 1987 gcc 1.0 release but common was the default
until 2020.

Since the code built on AIX until we phased out those releases XL
presumably defaulted to common too.

I see it this way, was thinking this this morning:
It is an ego thing to change the default in gcc.
It is very much like YouAsh precedent tramp calling the Gulf of Mexico
Gulf of America

He does not give a shit if every map and app and globe has to be reprinted or re-made.
Just an ego trip to show he is so great again.
Same for changing defaults that millions!!! use!!

--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: comp.os.linux.advocacy

On Mon, 20 Apr 2026 06:41:08 GMT, Jan Panteltje wrote:

It is an ego thing to change the default in gcc.

Section 6.9 of the C spec, under “Semantics”:

An *external definition* is an external declaration that is also a
definition of a function or an object. If an identifier declared
with external linkage is used in an expression (other than as part
of the operand of a `sizeof` operator), somewhere in the entire
program there shall be exactly one external definition for the
identifier; otherwise, there shall be no more than one.

So, no multiple external definitions allowed.
--- Synchronet 3.21f-Linux NewsLink 1.2