Package Details: libgccjit 10.2.0-2

Git Clone URL: (read-only, click to copy)
Package Base: libgccjit
Description: Just-In-Time Compilation using GCC.
Upstream URL:
Licenses: GPL3
Submitter: rubdos
Maintainer: flatwhatson (ZenTauro)
Last Packager: flatwhatson
Votes: 17
Popularity: 2.19
First Submitted: 2015-10-20 13:34
Last Updated: 2021-04-17 09:02

Latest Comments

1 2 3 4 Next › Last »

flatwhatson commented on 2021-04-17 09:04

@vorbote Thanks, I've removed the makedepends on gcc-ada.

vorbote commented on 2021-04-16 19:19

Hmmm. Here recompiling gcc for nefarious purposes I find that in modern GCC the frontend is pure C++. The official gcc PKGBUILD doesn't depend on ada anymore.

vorbote commented on 2021-04-16 16:39

Hi, Ada is not necessary as a makedepends. May you drop it? It is only needed if you are compiling Ada, because it has to bootstrap itself.

yin commented on 2020-09-27 19:35

oh right. I had a trailing colon on my PATH (/home/yin/sw/sh/links::/usr/local/sbin:/usr/local/bin:/usr/bin) because i messed up my .pam_environmnent... i haven't tested yet, but yeah, probably same issue.

nanny commented on 2020-09-27 15:41

Happy to help! That permission error is what happens when you try to execute a directory. When you mentioned that there was a directory called cp I suspected that your shell might've been trying to execute it instead of the /use/bin/cp binary. I suggest to anyone else reading here that you don't put . in your PATH because of errors like this!

iwaka commented on 2020-09-27 15:36

@nanny: Well shit XD I did have . in my PATH. I swear I have no idea how it got there. Removing it solved the issue. Thank you!

How did you know?

nanny commented on 2020-09-27 14:59

Do happen to have . in your PATH or something weird like that? What happens when you try building after logging into a shell without your .bashrc/.zshrc?

iwaka commented on 2020-09-27 07:16

@flatwatson, @nanny: I believe I have found the culprit.

The directory libgccjit/src/libgccjit-build/gcc contains a directory called cp (copied over from libgccjit/src/gcc-10.2.0/gcc). This directory prevents the cp command from being run in a Makefile in the gcc dir.

(I tested this in a separate directory with a minimal Makefile as well. If there's a subdirectory called cp in the same directory as the Makefile, the cp command will be denied permission.)

I can get the install to work if I delete the libgccjit/src/libgccjit-build/gcc/cp directory as soon as it is created, during the installation process itself (it's not used anywhere). Obviously, this is not ideal, but at least we have a lead here.

toki1990 commented on 2020-09-26 23:41

I'm trying compile gcc 10.2 and gcc 11-git. I tried lots of think but i cant success. I tried different arch linux distros. I tried lots of makepkg.conf settings. GCC 10.2 and GCC 11-git compilation error here:

ortran.lax/libbacktrace.a/fileline.o .libs/libgfortran.lax/libbacktrace.a/mmap.o .libs/libgfortran.lax/libbacktrace.a/mmapio.o .libs/libgfortran.lax/libbacktrace.a/posix.o .libs/libgfortran.lax/libbacktrace.a/print.o .libs/libgfortran.lax/libbacktrace.a/simple.o .libs/libgfortran.lax/libbacktrace.a/sort.o .libs/libgfortran.lax/libbacktrace.a/state.o libtool: link: ranlib .libs/libgfortran.a libtool: link: rm -fr .libs/libgfortran.lax .libs/libgfortran.lax libtool: link: ( cd ".libs" && rm -f "" && ln -s "../" "" ) make[6]: Leaving directory '/home/user/Genel/gcc11/gcc-git/src/gcc-build/x86_64-pc-linux-gnu/32/libgfortran' make[5]: Leaving directory '/home/user/Genel/gcc11/gcc-git/src/gcc-build/x86_64-pc-linux-gnu/32/libgfortran' make[4]: Leaving directory '/home/user/Genel/gcc11/gcc-git/src/gcc-build/x86_64-pc-linux-gnu/libgfortran' make[3]: Leaving directory '/home/user/Genel/gcc11/gcc-git/src/gcc-build/x86_64-pc-linux-gnu/libgfortran' make[2]: Leaving directory '/home/user/Genel/gcc11/gcc-git/src/gcc-build/x86_64-pc-linux-gnu/libgfortran' make[1]: Leaving directory '/home/user/Genel/gcc11/gcc-git/src/gcc-build' make: *** [Makefile:1003: all] Error 2

Sorry if my question is non related with here. I'm tried my lucky. Thanks for read.

iwaka commented on 2020-09-26 12:04

@flatwhatson: I'm sorry, I wasn't precise enough in my description the first time around. The SOURCE file does exist, and the TARGET file does not, as it should be. I mentioned this specifically because if the target file already existed, that may have been the issue with permissions (cp being unable to overwrite the file), but that is not the case. I can't tell where it lacks permissions.

I did try changing line 86 of the PKGBUILD to make -j1, but it gives the same error, so it's probably not a race condition. The log is the same as far as I can tell, so I haven't uploaded it, but I can if you think that will help.