Yeah alright, I guess I'll just remove the patch then
Search Criteria
Package Details: gcc-d-git 13.0.0_r197401.g33be3ee36a7-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/gcc-git.git (read-only, click to copy) |
---|---|
Package Base: | gcc-git |
Description: | D frontend for GCC (git version) |
Upstream URL: | https://gcc.gnu.org |
Licenses: | GFDL-1.3-or-later, GPL-3.0-with-GCC-exception |
Conflicts: | gcc-d |
Provides: | gcc-d, gdc, gdc-git |
Replaces: | gdc-git |
Submitter: | Allan |
Maintainer: | IslandC0der (ptr1337) |
Last Packager: | ptr1337 |
Votes: | 15 |
Popularity: | 0.000001 |
First Submitted: | 2013-06-26 03:43 (UTC) |
Last Updated: | 2024-03-21 19:26 (UTC) |
Dependencies (18)
- gcc-gitAUR
- libisl.so (libisl)
- binutils (make)
- doxygen (doxygen-gitAUR, doxygen-yapAUR) (make)
- gcc-ada (gcc-ada-gitAUR, gcc-ada-debugAUR, gcc-ada-snapshotAUR) (make)
- gcc-d (gcc-d-gitAUR, gcc-d-snapshotAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- lib32-gcc-libs (lib32-gcc-libs-gitAUR, lib32-gccrs-libs-gitAUR, lib32-gcc-libs-snapshotAUR) (make)
- lib32-glibc (lib32-glibc-gitAUR, lib32-glibc-linux4AUR, lib32-glibc-eacAUR, lib32-glibc-eac-binAUR, lib32-glibc-eac-rocoAUR) (make)
- libisl (libisl-gitAUR) (make)
- libmpc (libmpc-gitAUR) (make)
- python (python37AUR, python311AUR, python310AUR) (make)
- zstd (zstd-gitAUR, zstd-staticAUR) (make)
- dejagnu (dejagnu-gitAUR) (check)
- expect (check)
- inetutils (inetutils-gitAUR, busybox-coreutilsAUR) (check)
- python-pytest (check)
- tcl (tcl-fossilAUR, tcl84AUR) (check)
Required by (40)
- a7xpg (requires gcc-d)
- amalthea-gdc (requires gcc-d)
- amalthea-gdc (requires gcc-d) (make)
- cheesecutter-git (requires gcc-d) (make)
- gcc-ada-git (requires gcc-d) (make)
- gcc-ada-snapshot (requires gcc-d) (make)
- gcc-d-git (requires gcc-d) (make)
- gcc-d-snapshot (requires gcc-d) (make)
- gcc-fortran-git (requires gcc-d) (make)
- gcc-fortran-snapshot (requires gcc-d) (make)
- gcc-git (requires gcc-d) (make)
- gcc-go-git (requires gcc-d) (make)
- gcc-go-snapshot (requires gcc-d) (make)
- gcc-libs-git (requires gcc-d) (make)
- gcc-libs-snapshot (requires gcc-d) (make)
- gcc-m2-snapshot (requires gcc-d) (make)
- gcc-objc-git (requires gcc-d) (make)
- gcc-objc-snapshot (requires gcc-d) (make)
- gcc-rust-git (requires gcc-d) (make)
- gcc-rust-snapshot (requires gcc-d) (make)
- Show 20 more...
Sources (4)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 13 Next › Last »
IslandC0der commented on 2021-08-30 00:07 (UTC)
DAC324 commented on 2021-08-27 10:26 (UTC) (edited on 2021-08-27 10:26 (UTC) by DAC324)
I must admit that I was astonished as well but that's what the the gcc11-Wno-format-security.patch
ist doing:
When adding -Wno-format, also add -Wno-format-security
I am pretty sure that the setting of -Werror=format-security
in /etc/makepkg.conf
supersedes the -Wno-format-security
setting applied by the patch.
Or, in other words, gcc
, after applying the patch, is probably run with both -Wno-format-security
AND -Werror=format-security
- in that situation, -Werror=format-security
prevails.
IslandC0der commented on 2021-08-26 22:18 (UTC)
The weird thing is, I'm pretty sure gcc11-Wno-format-security.patch
should've taken care of that issue :/
IslandC0der commented on 2021-08-26 22:15 (UTC)
Awesome! Thanks, I've just added it :)
DAC324 commented on 2021-08-26 08:38 (UTC) (edited on 2021-08-26 08:39 (UTC) by DAC324)
@IslandC0der:
Thanks a lot for your work. With the latest PKGBUILD
, the packages install without complaints.
There is only one thing that might make sense to be added to PKGBUILD
:
CXXFLAGS=${CXXFLAGS/-Werror=format-security/}
This is because the Arch developers have decided to include the flag -Werror=format-security
in /etc/makepkg.conf
, and hence, it is applied to the flags used by makepkg
when compiling sources.
As gcc
does not like this flag, it is better to have it removed, at least for this package.
IslandC0der commented on 2021-08-22 18:59 (UTC)
The conflict issue should be solved now with the latest PKGBUILD version; I'm still trying to debug the other ones.
Speaking of which, if you still have those issues, would you mind emailing me your compiled gcc-*-git
packages (along with that config.log
file on your third error message)?
I can't currently build them due to hardware limitations :/
DAC324 commented on 2021-08-20 09:18 (UTC) (edited on 2021-08-20 09:52 (UTC) by DAC324)
@IslandC0der: "Similarly, even though gcc-ada-git provides GNAT support, when building for the first time, it will require some existing GNAT support (i.e. from gcc-ada)."
Problem: With gcc-ada-git
installed, I get
configure: error: GNAT is required to build ada
==> ERROR: A failure occurred in build().
Aborting...
To resolve this error, I have to install stock gcc-ada
, however, after that, I of course get
==> Checking buildtime dependencies...
==> Missing dependencies:
-> gcc-ada-git
==> ERROR: Could not resolve all dependencies.
To remedy this, I will have to change gcc-ada-git
to gcc-ada
in the makedepends line.
Same, by the way, with the installed gcc-git
itself. With gcc-git
installed, I usually get
configure: error: C compiler cannot create executables
See `config.log' for more details
==> ERROR: A failure occurred in build().
Aborting...
So, I have to reinstall stock gcc
first to get a working compiler.
Now, there seems to be one glitch remaining. When trying to install gcc-libs-git
after I have successfully built and installed gcc-git
, I get:
:: gcc-libs-git and gcc-git are in conflict (gcc). Remove gcc-git? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: gcc-libs-git and gcc-git are in conflict
IslandC0der commented on 2021-08-18 20:59 (UTC)
Hmm, do you still get that issue with the latest version of the PKGBUILD? I tweaked it a bit yesterday (I added the non -git versions to provides
).
Tip: running makepkg -i
automatically calls pacman -U
to install the built package :)
DAC324 commented on 2021-08-18 16:43 (UTC) (edited on 2021-08-18 16:48 (UTC) by DAC324)
@IslandC0der: "yes, it tries to install gcc so it can compile itself... You can't compile a compiler without a compiler already present :P
Similarly, even though gcc-ada-git provides GNAT support, when building for the first time, it will require some existing GNAT support (i.e. from gcc-ada)."
That's well understood but shouldn't the package recognize former versions of gcc-git
if already installed?
Trying to update gcc-git
, it complained about a missing gcc
dependency. Same with gcc-ada-git
; it should also provide gcc-ada
.
However, I get an error from the gcc-git
package about gcc-ada
being missing as well, even after having installed gcc-ada-git
.
Unfortunately, due to Arch's decision to include -Werror=format-security
in /etc/makepkg.conf
, I currently have to modify the PKGBUILD
so that this flag is inactivated for gcc-git
and then manually run makepkg
and sudo pacman -U gcc-git{version}
.
IslandC0der commented on 2021-08-17 21:52 (UTC)
@DAC324
Regarding the yay
error: that sounds like a problem with yay
itself, have you tried doing a clean build (or maybe removing ~/.cache/yay/gcc-git/
)?
Regarding the other problems: yes, it tries to install gcc
so it can compile itself... You can't compile a compiler without a compiler already present :P
Similarly, even though gcc-ada-git
provides GNAT support, when building for the first time, it will require some existing GNAT support (i.e. from gcc-ada
).
PS: the redirection is normal, since this is a split package.
Pinned Comments
DAC324 commented on 2021-09-17 08:04 (UTC)
In addition to the jamespharvey20's sticky comment: The current GCC 12 versions are labelled "Experimental" for a reason. Development is ongoing, and there are still significant bugs. Hence, it is not recommended to use GCC 12 as a daily driver or on production systems.
At the moment, it is not even possible to build a working Linux kernel with GCC 12, see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101941 .
jamespharvey20 commented on 2017-02-15 04:30 (UTC) (edited on 2017-02-15 11:01 (UTC) by jamespharvey20)