Search Criteria
Package Details: mips-elf-gcc 12.2.0-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/mips-elf-gcc.git (read-only, click to copy) |
---|---|
Package Base: | mips-elf-gcc |
Description: | The GNU Compiler Collection - cross compiler for MIPS ELF (bare-metal) target |
Upstream URL: | https://gcc.gnu.org/ |
Licenses: | GPL |
Conflicts: | cross-mips-elf-gcc |
Replaces: | cross-mips-elf-gcc |
Submitter: | angelodalzotto |
Maintainer: | angelodalzotto |
Last Packager: | angelodalzotto |
Votes: | 5 |
Popularity: | 0.000114 |
First Submitted: | 2022-03-14 00:26 (UTC) |
Last Updated: | 2022-08-29 12:24 (UTC) |
Latest Comments
1 2 Next › Last »
angelodalzotto commented on 2023-01-25 11:23 (UTC)
To use stdio.h (and other libraries) you may compile a standard C library, such as newlib.
dhims commented on 2023-01-25 07:19 (UTC)
After installation of package I am not able to build c code as it cannot find stdio.h. Any idea how to fix it? "fatal error: stdio.h: No such file or directory"
mthfrr commented on 2021-12-26 10:49 (UTC)
I had a similar problem as philpirj. The
-Werror=format-security
flag came from the config of makepkg (/etc/makepkg.conf
).I removed it and it works !
If someone cares, the CFLAGS set by default in makepkg.conf are:
This is a fresh arch install from the 2021.12 iso.
NigelCunningham commented on 2021-10-22 22:36 (UTC)
I have been able to reproduce the issue for the last few months.
What packages & configuration might influence the build to cause this?
angelodalzotto commented on 2021-07-12 10:55 (UTC)
I can't reproduce the build error as its building just fine for me without applying any patches.
About the signature, you may import the key:
philpirj commented on 2021-06-27 14:01 (UTC)
Alright, there's https://github.com/archlinux/svntogit-packages/blob/packages/gcc/trunk/gcc11-Wno-format-security.patch in the core
gcc
package.It should be applied as well to
cross-mips-elf-gcc
like this (see https://github.com/archlinux/svntogit-packages/blob/c0c9a945c11d1868af6d4dbcef985319ee153ea3/trunk/PKGBUILD#L31):Also, add:
to
prepare()
.It is, however, still insufficient, as the error is detected in
libcpp
, while we've patched the rootconfigure.ac
.What helps is the removal of:
from
src/gcc-11.1.0/libcpp/configure
. However, I don't really understand what fromsrc/gcc-11.1.0/libcpp/configure.ac
adds it, and can't create an includable patch.After removing this nasty option, I could manually build GCC. Next:
failed with:
as it creates
usr/local/bin
, notusr/bin
:philpirj commented on 2021-06-09 08:46 (UTC)
Getting a compilation error now:
philpirj commented on 2021-06-09 08:43 (UTC) (edited on 2021-06-09 09:31 (UTC) by philpirj)
From Jakub:
Older releases I've signed are with the older key (now expired), the newer with the newer key, both have correct fingerprints on that mirrors.html and both are uploaded to multiple key servers.
There are no separate 6C35 and D3A9 keys, that is a single key with D3A9 3CAD 751C 2AF4 F8C7 AD51 6C35 B993 09B5 FA62 fingerprint. http://keys.gnupg.net/pks/lookup?op=get&search=0x6C35B99309B5FA62 is the nwer one and http://keys.gnupg.net/pks/lookup?op=get&search=0xA328C3A2C3C45C06 is the older one.
It seems to have been a problem with my user keyring. Resolved.
philpirj commented on 2021-06-08 09:56 (UTC)
https://aur.archlinux.org/packages/libgccjit/#comment-808549 suggests importing this key:
but frankly I don't understand why one do that, and why this signature should be trusted?
Checked with Jakub to update their signature on GNU FTP mirrors page.
Anyway, after importing:
philpirj commented on 2021-06-08 09:47 (UTC)
Didn't work.
It still fails the check even if I add this
6C35
key tovalidpgpkeys
(desperate mode alert).1 2 Next › Last »