You are not logged in.

#26 2021-12-07 07:01:10

Xyne
Moderator/TU
Registered: 2008-08-03
Posts: 6,802
Website

Re: What is happening with glibc and gcc packages?

So you became a lead dev on "Pacman"? It all makes sense now.


My Arch Linux StuffForum EtiquetteCommunity Ethos - Arch is not for everyone

Offline

#27 2021-12-07 08:00:26

Allan
Pacman
From: Brisbane, AU
Registered: 2007-06-09
Posts: 11,123
Website

Re: What is happening with glibc and gcc packages?

I misread what it was, and just rolled with it.

Offline

#28 2021-12-07 08:57:29

seth
Member
Registered: 2012-09-03
Posts: 26,306

Re: What is happening with glibc and gcc packages?

The why are there no ghosts in ILoveCandy ? U+1F47B
And I want Color to be respected - otherwise I'm not buying any of the story here tongue

Offline

#29 2021-12-09 19:00:13

kyak
Member
Registered: 2012-01-20
Posts: 29

Re: What is happening with glibc and gcc packages?

Thanks Allan! Finally some proper care has been taken of toolchain.

Offline

#30 2021-12-15 14:12:14

solskogen
Member
From: Norway
Registered: 2005-03-06
Posts: 90

Re: What is happening with glibc and gcc packages?

Regarding the PKGBUILD for gcc I've noticed a few things.
_libdir is not used
There a patch for adding -Wno-format-security  which is removed in CFLAGS.
--enable-lto and having lto on the language list is not necessary (lto is enabled by default)
--disable-libunwind-exceptions is not a configuration option (anymore)
--enable-shared is already default. No reason to specify it.

Offline

#31 2021-12-16 01:35:03

Allan
Pacman
From: Brisbane, AU
Registered: 2007-06-09
Posts: 11,123
Website

Re: What is happening with glibc and gcc packages?

solskogen wrote:

_libdir is not used

I'll remove - that was left over from when I merged the packages together.

solskogen wrote:

There a patch for adding -Wno-format-security  which is removed in CFLAGS.

I had a bunch of failures even with that patch.  So I disabled the flag too.  Keeping the patch because that will be the approach going forward.

solskogen wrote:

--enable-lto and having lto on the language list is not necessary (lto is enabled by default)
--disable-libunwind-exceptions is not a configuration option (anymore)
--enable-shared is already default. No reason to specify it.

I'll remove the configure flags but keep lto in the language list.  Redundancy is OK when it informs the reader.

Offline

#32 2021-12-16 14:29:35

solskogen
Member
From: Norway
Registered: 2005-03-06
Posts: 90

Re: What is happening with glibc and gcc packages?

There's really no reason to add lto to the language list either. It's been default for at least 10 years. It's possible to disable lto with --disable-lto, but is has no effect what so ever to add it.

Offline

#33 2021-12-16 22:32:42

Allan
Pacman
From: Brisbane, AU
Registered: 2007-06-09
Posts: 11,123
Website

Re: What is happening with glibc and gcc packages?

So is c, c++, and fortran...  But they are there for quick identification of what is enabled.  Specifying defaults can serve as internal documentation.

Offline

Board footer

Powered by FluxBB