Package Details: gcc48 4.8.5-1

Git Clone URL: https://aur.archlinux.org/gcc48.git (read-only, click to copy)
Package Base: gcc48
Description: The GNU Compiler Collection - C and C++ frontends (4.8.x)
Upstream URL: http://gcc.gnu.org
Licenses: GPL, custom, LGPL, FDL
Submitter: ftschindler
Maintainer: severach
Last Packager: severach
Votes: 12
Popularity: 0.000164
First Submitted: 2014-05-06 16:14 (UTC)
Last Updated: 2021-09-28 18:52 (UTC)

Latest Comments

1 2 3 4 5 Next › Last »

moormaster commented on 2024-09-14 14:05 (UTC)

The CHOST: unbound variable error is fixed for me now when building with recent version >=7.0 of makepkg/pacman.

thisisrahulg commented on 2024-08-03 16:55 (UTC) (edited on 2024-08-03 16:58 (UTC) by thisisrahulg)

The CHOST: unbound variable error

For this, Remove the CHOST entries from the PKGBUILD and re-run.

--- PKGBUILD    2024-08-03 22:27:27.011030234 +0530
+++ .cache/paru/clone/gcc48/PKGBUILD    2024-08-03 21:08:07.360976497 +0530
@@ -106,7 +106,6 @@
     cd 'gcc-build'
     # The following options are one per line, mostly sorted so they are easy to diff compare to other gcc packages.
     local _conf=(
-      --build="${CHOST}"
       --disable-libstdcxx-pch
       --disable-libunwind-exceptions
       --disable-multilib
@@ -147,7 +146,7 @@
   nice make -s

   # make documentation
-  make -s -j1 -C "${CHOST}/libstdc++-v3/doc" 'doc-man-doxygen'
+  #make -s -j1 -C "${CHOST}/libstdc++-v3/doc" 'doc-man-doxygen'
   set +u
 }

@@ -177,9 +176,9 @@
   find "${pkgdir}/" -name '*iberty*' -exec rm '{}' '+'

   # Move potentially conflicting stuff to version specific subdirectory
-  case "${CARCH}" in
-  'x86_64') mv "${pkgdir}/usr/lib/gcc/${CHOST}"/lib*/ "${pkgdir}/usr/lib/gcc/${CHOST}/${pkgver}/" ;;
-  esac
+  #case "${CARCH}" in
+  #'x86_64') mv "${pkgdir}/usr/lib/gcc/${CHOST}"/lib*/ "${pkgdir}/usr/lib/gcc/${CHOST}/${pkgver}/" ;;
+  #esac
   #mv "${pkgdir}/usr/lib"/lib* "${pkgdir}/usr/lib/gcc/${CHOST}/${pkgver}/"

   # Install Runtime Library Exception

moormaster commented on 2024-05-21 17:40 (UTC)

The CHOST: unbound variable error might be a bug in makepkg which might be fixed in the next version >6.1.0

https://gitlab.archlinux.org/pacman/pacman/-/commit/7dcf9a2b49226af8fcb43202d83260873fc11490

frazar0 commented on 2024-04-15 06:42 (UTC) (edited on 2024-04-15 06:43 (UTC) by frazar0)

I am facing an error when trying to compile the gcc48 package in a clean chroot with aurutils using

aur sync --chroot gcc48

The exact error is the following:

==> Starting build()...
/startdir/PKGBUILD: line 139: CHOST: unbound variable
==> ERROR: Build failed, check /var/lib/aurbuild/x86_64/frazar/build

moormaster commented on 2021-09-01 00:21 (UTC) (edited on 2021-09-03 18:16 (UTC) by moormaster)

I also needed to make following changes in the last patch by chn - set CPPFLAGS when it was unset before entering strict mode (makepkg.conf does not set it anymore) - remove compiler flags -fstack-clash-protection and -fcf-protection

See my new patch

--- a/PKGBUILD  2021-09-03 20:15:32.986534503 +0200
+++ b/PKGBUILD  2021-09-03 20:15:30.979991752 +0200
@@ -97,6 +97,11 @@
 }

 build() {
+  if [ "$CPPFLAGS" == "" ]
+  then
+    CPPFLAGS=""
+  fi
+
   set -u
   if [ ! -s "${_basedir}/gcc-build/Makefile" ]; then
     cd "${_basedir}"
@@ -108,6 +113,9 @@
     CFLAGS="${CFLAGS//-fstack-protector-strong/-fstack-protector}"
     CXXFLAGS="${CXXFLAGS//-fstack-protector-strong/-fstack-protector}"

+    CFLAGS="${CFLAGS//-Werror=format-security/}"
+    CXXFLAGS="${CXXFLAGS//-Werror=format-security/}"
+
     # using -pipe causes spurious test-suite failures
     # http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48565
     CFLAGS="${CFLAGS/-pipe/}"
@@ -120,6 +128,14 @@
     CFLAGS="${CFLAGS/-Wformat-overflow=[0-9]/}"
     CXXFLAGS="${CXXFLAGS/-Wformat-overflow=[0-9]/}"

+    CFLAGS="${CFLAGS//-fstack-clash-protection/}"
+    CXXFLAGS="${CXXFLAGS//-fstack-clash-protection/}"
+
+    CFLAGS="${CFLAGS//-fcf-protection/}"
+    CXXFLAGS="${CXXFLAGS//-fcf-protection/}"
+
+    CPPFLAGS+=" -O2 -Wno-implicit-fallthrough -Wno-expansion-to-defined -Wno-unused-result -Wno-cast-function-type -Wno-switch"
+
     cd 'gcc-build'
     # The following options are one per line, mostly sorted so they are easy to diff compare to other gcc packages.
     ../configure \
@@ -151,7 +167,8 @@
       --with-plugin-ld='ld.gold' \
       --with-ppl \
       --with-system-zlib \
-      --prefix='/usr'
+      --prefix='/usr' \
+      CXX='g++ -std=c++14'
 #      CXX='g++-4.9' CC='gcc-4.9'
   fi

chn commented on 2021-06-19 11:53 (UTC)

Build failed with gcc11, unless with the following patch:

diff --git a/PKGBUILD b/PKGBUILD
index 7b1433f..21927aa 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -120,6 +120,8 @@ build() {
     CFLAGS="${CFLAGS/-Wformat-overflow=[0-9]/}"
     CXXFLAGS="${CXXFLAGS/-Wformat-overflow=[0-9]/}"

+    CPPFLAGS+=" -O2 -Wno-implicit-fallthrough -Wno-expansion-to-defined -Wno-unused-result -Wno-cast-function-type -Wno-switch"
+
     cd 'gcc-build'
     # The following options are one per line, mostly sorted so they are easy to diff compare to other gcc packages.
     ../configure \
@@ -151,7 +153,8 @@ build() {
       --with-plugin-ld='ld.gold' \
       --with-ppl \
       --with-system-zlib \
-      --prefix='/usr'
+      --prefix='/usr' \
+      CXX='g++ -std=c++14'
 #      CXX='g++-4.9' CC='gcc-4.9'
   fi

severach commented on 2016-12-12 18:42 (UTC)

Builds fine here with gcc-multilib 6.2.1. Try enabling the LD_PRELOAD lines.

quenyen commented on 2016-12-12 15:37 (UTC)

I get a fail on building this from Manjaro Linux (current...either from gcc62 or from gcc49....this is where it goes belly up for me.... make[6]: *** [libstdc++.la] Error 139 make[5]: *** [all-recursive] Error 1 make[4]: *** [all-recursive] Error 1 make[3]: *** [all] Error 2 make[2]: *** [all-stage1-target-libstdc++-v3] Error 2 make[1]: *** [stage1-bubble] Error 2 make: *** [all] Error 2 /usr/bin/makepkg: line 729: logpipe: unbound variable ==> ERROR: Makepkg was unable to build gcc48. ==> Restart building gcc48 ? [y/N] ==> ------------------------------ ==> N I have the same problem of course just compiling the source....

severach commented on 2016-10-10 03:12 (UTC)

Updated PKGBUILD didn't work for me. Failed on gcc.texi just as mine did. Using the 4.9 PKGBUILD would cause a lot of changes that might break things for users wanting 4.8.