Package Details: gcc49 4.9.4-3

Git Clone URL: https://aur.archlinux.org/gcc49.git (read-only, click to copy)
Package Base: gcc49
Description: The GNU Compiler Collection (4.9.x)
Upstream URL: https://gcc.gnu.org
Licenses: GPL-2.0-only, LGPL-2.1-only, GPL-3.0-only, LGPL-3.0-only, LicenseRef-custom, GFDL-1.3-only
Submitter: rubenvb
Maintainer: severach
Last Packager: severach
Votes: 22
Popularity: 0.000000
First Submitted: 2015-07-01 12:48 (UTC)
Last Updated: 2026-05-14 17:17 (UTC)

Latest Comments

1 2 3 4 5 6 .. 8 Next › Last »

nathan.vanb3 commented on 2026-07-20 19:29 (UTC)

Linux kernel v7.1+ removed linux/scc.h, resulting in the libsanitizer build failing (see dd8d4bc28ad7252610d8e79c1313a2d1e3499a51). The following patch should remove any scc.h references from libsanitizer:

diff -ura gcc-4.9.4/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc gcc-4.9.4.new/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc
--- gcc-4.9.4/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc  2026-07-20 14:06:39.163210142 -0400
+++ gcc-4.9.4.new/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc  2026-07-20 14:07:59.626530228 -0400
@@ -87,7 +87,6 @@
 #include <linux/lp.h>
 #include <linux/mroute.h>
 #include <linux/mroute6.h>
-#include <linux/scc.h>
 #include <linux/serial.h>
 #include <sys/msg.h>
 #include <sys/ipc.h>
@@ -321,8 +320,6 @@
   unsigned struct_mtconfiginfo_sz = sizeof(struct mtconfiginfo);
   unsigned struct_nr_parms_struct_sz = sizeof(struct nr_parms_struct);
   unsigned struct_ppp_stats_sz = sizeof(struct ppp_stats);
-  unsigned struct_scc_modem_sz = sizeof(struct scc_modem);
-  unsigned struct_scc_stat_sz = sizeof(struct scc_stat);
   unsigned struct_serial_multiport_struct_sz
       = sizeof(struct serial_multiport_struct);
   unsigned struct_serial_struct_sz = sizeof(struct serial_struct);

salfter commented on 2026-05-13 21:51 (UTC)

I need this to get xilinx-ise up and running, but I'm getting this error:

libtool: compile:  /home/salfter/.cache/yay/gcc49/src/gcc-4.9.4/gcc-build/./gcc/gccgo -B/home/salfter/.cache/yay/gcc49/src/gcc-4.9.4/gcc-build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include -minline-all-stringops -O2 -g -I . -c -fgo-pkgpath=syscall ../../../libgo/go/syscall/env_unix.go ../../../libgo/go/syscall/syscall_errno.go ../../../libgo/go/syscall/libcall_support.go ../../../libgo/go/syscall/libcall_posix.go ../../../libgo/go/syscall/race0.go ../../../libgo/go/syscall/socket.go ../../../libgo/go/syscall/sockcmsg_unix.go ../../../libgo/go/syscall/str.go ../../../libgo/go/syscall/syscall.go ../../../libgo/go/syscall/sockcmsg_linux.go ../../../libgo/go/syscall/syscall_unix.go ../../../libgo/go/syscall/exec_unix.go ../../../libgo/go/syscall/exec_linux.go ../../../libgo/go/syscall/libcall_wait4.go ../../../libgo/go/syscall/sleep_select.go ../../../libgo/go/syscall/errstr_linux.go ../../../libgo/go/syscall/libcall_posix_largefile.go ../../../libgo/go/syscall/socket_linux.go epoll.go ../../../libgo/go/syscall/socket_posix.go ../../../libgo/go/syscall/libcall_uname.go ../../../libgo/go/syscall/netlink_linux.go ../../../libgo/go/syscall/lsf_linux.go ../../../libgo/go/syscall/libcall_linux_utimesnano.go ../../../libgo/go/syscall/libcall_linux.go ../../../libgo/go/syscall/libcall_linux_amd64.go ../../../libgo/go/syscall/syscall_linux_amd64.go libcalls.go sysinfo.go syscall_arch.go  -fPIC -o .libs/syscall.o
sysinfo.go:7429:7: error: redefinition of ‘SYS_SECCOMP’
 const SYS_SECCOMP = _SYS_SECCOMP
       ^                                                                                                                
sysinfo.go:7187:7: note: previous definition of ‘SYS_SECCOMP’ was here
 const SYS_SECCOMP = _SYS_seccomp
       ^
make[4]: *** [Makefile:5641: syscall.lo] Error 1                           

manuel-baez commented on 2026-04-23 05:09 (UTC) (edited on 2026-04-23 05:25 (UTC) by manuel-baez)

I trayed to build this package using pamac and it return the next error code in termial

libtool: link: ranlib .libs/libgfortran.a
libtool: link: ( cd ".libs" && rm -f "libgfortran.la" && ln -s "../libgfortran.la" "libgfortran.la" )
make: *** [Makefile:896: all] Error 2
/usr/share/makepkg/util/message.sh: línea 84: RED: variable sin asignar
/usr/bin/makepkg: línea 129: logpipe: variable sin asignar
Fallo al construir gcc49

vitaliikuzhdin commented on 2025-07-17 20:14 (UTC)

/home/vitalii/.cache/yay/gcc49/PKGBUILD: line 57: MAKEFLAGS: unbound variable
/usr/bin/makepkg: line 133: logpipe: unbound variable
 -> error making: gcc49-exit status 1

severach commented on 2023-02-22 04:55 (UTC)

I pulled in the c++11 fix @bartus noted from gcc49-multilib.

GloW commented on 2023-02-21 10:04 (UTC)

Do not build:

/home/glow/.cache/yay/gcc49/src/gcc-4.9.4/gcc/reload1.c: In function ‘void init_reload()’:
/home/glow/.cache/yay/gcc49/src/gcc-4.9.4/gcc/reload1.c:89:24: error: use of an operand of type ‘bool’ in ‘operator++’ is forbidden in C++17
   89 |   (this_target_reload->x_spill_indirect_levels)

bartus commented on 2021-07-07 17:39 (UTC)

Fix build against gcc:11 sanitize FLAGS to prevent mishaps with future gcc releases. http://ix.io/3seU/diff

Apply with git am -s < <(curl -s http://ix.io/3seU )

gnaggnoyil commented on 2021-05-30 16:06 (UTC)

GCC 11 upgrades its default language standard mode from gnu++14 to gnu++17, meanwhile GCC 4.9 src contains code that is no longer valid since C++17.

Thus, building this package with GCC 11 reports the following error:

/home/gnaggnoyil/.cache/yay/gcc49/src/gcc-4.9.4/gcc/reload1.c: 在函数‘void init_reload()’中:
/home/gnaggnoyil/.cache/yay/gcc49/src/gcc-4.9.4/gcc/reload1.c:89:24: 错误:use of an operand of type ‘bool’ in ‘operator++’ is forbidden in C++17
   89 |   (this_target_reload->x_spill_indirect_levels)
      |   ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~
/home/gnaggnoyil/.cache/yay/gcc49/src/gcc-4.9.4/gcc/reload1.c:444:7: 附注:in expansion of macro ‘spill_indirect_levels’
  444 |       spill_indirect_levels++;
      |       ^~~~~~~~~~~~~~~~~~~~~
/home/gnaggnoyil/.cache/yay/gcc49/src/gcc-4.9.4/gcc/reload1.c: 在函数‘void elimination_effects(rtx, machine_mode)’中:
/home/gnaggnoyil/.cache/yay/gcc49/src/gcc-4.9.4/gcc/reload1.c:3044:31: 警告:this statement may fall through [-Wimplicit-fallthrough=]
 3044 |       if (code == POST_MODIFY || code == PRE_MODIFY)
      |           ~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~
/home/gnaggnoyil/.cache/yay/gcc49/src/gcc-4.9.4/gcc/reload1.c:3048:5: 附注:here
 3048 |     case STRICT_LOW_PART:
      |     ^~~~
make[3]: *** [Makefile:1058:reload1.o] 错误 1

petronny commented on 2020-10-28 07:47 (UTC) (edited on 2020-10-28 07:48 (UTC) by petronny)

version numbering in GCC changed starting from version 5

I see. Thanks for your explanations.

rubenvb commented on 2020-10-28 07:46 (UTC)

@petronny: No, for one because there is also a gcc43, gcc44, gcc45, gcc46, gcc47, and gcc48 in the AUR which all represent distinct versions that may be required by various tools like Matlab or older CUDA or ICC versions. Aside from that, the version numbering in GCC changed starting from version 5, where the first release was 5.1, and subsequent bugfix releases came out as 5.2, 5.3, etc. in contrast to 4.X.Y starting at 4.X.0 and bugfix releases for as 4.X.1, 4.X.2, etc.