Package Details: i686-elf-gcc 11.2.0-2

Git Clone URL: https://aur.archlinux.org/i686-elf-gcc.git (read-only, click to copy)
Package Base: i686-elf-gcc
Description: GNU gcc for the i686- toolchain
Upstream URL: https://www.gnu.org/software/gcc
Licenses: GPL
Submitter: andrewchen
Maintainer: c0repwn3r
Last Packager: c0repwn3r
Votes: 10
Popularity: 0.059956
First Submitted: 2014-12-02 22:57 (UTC)
Last Updated: 2022-05-13 02:24 (UTC)

Pinned Comments

c0repwn3r commented on 2022-05-13 02:26 (UTC) (edited on 2022-05-13 02:27 (UTC) by c0repwn3r)

I have taken over this package, build issues should be fixed and it has been updated to GCC 11.2.0. No makepkg.conf edits are required anymore, GCC sources are patched to fix the build problems

Latest Comments

c0repwn3r commented on 2022-05-13 02:26 (UTC) (edited on 2022-05-13 02:27 (UTC) by c0repwn3r)

I have taken over this package, build issues should be fixed and it has been updated to GCC 11.2.0. No makepkg.conf edits are required anymore, GCC sources are patched to fix the build problems

alicela1n commented on 2021-11-04 05:27 (UTC)

A workaround to build the package using Makepkg would be to remove Werror=format-security from your makepkg.conf

IPlayZed commented on 2021-08-17 13:53 (UTC)

A working solution would be to remove the Werror=format-security in the Makefile.

IPlayZed commented on 2021-08-17 13:44 (UTC) (edited on 2021-08-17 13:53 (UTC) by IPlayZed)

Werror=format-security fails for me as well.

elmazzun commented on 2021-08-10 20:43 (UTC)

I'm still having problems with this package.
Trying to compile this with makepkg -si, can't do it because of Werror=format-security.
Is there any way I can overwrite CFLAGS and remove those warning seen
as errors?

aviallon commented on 2021-06-06 18:23 (UTC)

Thanks for updating!

aviallon commented on 2021-06-06 17:03 (UTC)

I am ready to take over this package's maintainance if you want, @finlaywashere

aviallon commented on 2021-04-30 21:17 (UTC)

It looks like Arch's new makepkg.conf CFLAGS are causing build failures with GCC (with format-security errors...) Hmmm.

finlaywashere commented on 2019-08-16 14:44 (UTC)

I have taken over maintenance of this package and fixed it, also it is now updated to the latest gcc version.

colatkinson commented on 2018-04-17 09:46 (UTC)

Broken for me as well, also on x86_64. Anyone know of any fixes?

chrisf commented on 2018-02-05 20:41 (UTC)

Broken on x86_64. The built i686-elf-gcc produces 64bit objects.

rileyphone commented on 2016-09-06 16:16 (UTC)

I built this on gcc 6.1.1 by changing the pkgver to 6.2.0 and the _islver to 0.16.1 sha256sums for those: gcc - 9944589fc722d3e66308c0ce5257788ebd7872982a718aa2516123940671b7c5 isl - 412538bb65c799ac98e17e8cfcdacbb257a57362acfaaff254b0fcae970126d2

andreas303 commented on 2016-08-14 16:44 (UTC)

(I am a total newbie about cross-compilation, so this question might be slightly stupid.) I tried to build this package, but yaourt failed with the following error message. Is it because yaourt tries to build the cross-compiling gcc4.9.2 with my current native gcc (which is of version 6.1.1), or is there another probable reason? In file included from /tmp/yaourt-tmp-andreas/aur-i686-elf-gcc/src/gcc-4.9.2/gcc/cp/except.c:1013:0: cfns.gperf: In function ‘const char* libc_name_p(const char*, unsigned int)’: cfns.gperf:101:1: error: ‘const char* libc_name_p(const char*, unsigned int)’ redeclared inline with ‘gnu_inline’ attribute cfns.gperf:26:14: note: ‘const char* libc_name_p(const char*, unsigned int)’ previously declared here cfns.gperf: At global scope: cfns.gperf:26:14: warning: inline function ‘const char* libc_name_p(const char*, unsigned int)’ used but never defined make[1]: *** [Makefile:1058: cp/except.o] Error 1 make[1]: Leaving directory '/tmp/yaourt-tmp-andreas/aur-i686-elf-gcc/src/gcc-build/gcc' make: *** [Makefile:3979: all-gcc] Error 2 ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Makepkg was unable to build i686-elf-gcc.

andrewchen commented on 2015-03-29 00:18 (UTC)

Hi, I don't use this package or have time to maintain it any more. If you want, you could adopt it and fix the download links and checksums. You could reference the gcc PKGBUILD from the [core].

keystroke commented on 2015-03-29 00:12 (UTC)

Running `makepkg` failed. I had to remove the '#' from the sources list, replace the snapshot version in the PKGBUILD, and run without checksums. Worked just fine then.