Package Details: arm-linux-gnueabihf-gcc 14.2.1.git+ab884fffe3f-2

Git Clone URL: https://aur.archlinux.org/arm-linux-gnueabihf-gcc.git (read-only, click to copy)
Package Base: arm-linux-gnueabihf-gcc
Description: The GNU Compiler Collection
Upstream URL: https://gcc.gnu.org
Licenses: GPL, custom, LGPL, FDL
Conflicts: arm-linux-gnueabihf-gcc-stage1, arm-linux-gnueabihf-gcc-stage2
Provides: arm-linux-gnueabihf-gcc-stage1, arm-linux-gnueabihf-gcc-stage2
Replaces: arm-linux-gnueabihf-gcc-stage1, arm-linux-gnueabihf-gcc-stage2
Submitter: tavianator
Maintainer: wgottwalt
Last Packager: wgottwalt
Votes: 81
Popularity: 1.18
First Submitted: 2015-09-14 15:41 (UTC)
Last Updated: 2024-12-05 18:03 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »

smallAndSimple commented on 2020-01-10 10:48 (UTC)

I cannot update this packet in Yay because of a weird (curcular?) thing:

I want to update arm-linux-gnueabihf-gcc to 9.2.0-4. But for that I need arm-linux-gnueabihf-glibc 2.30-3. To install linux-gnueabihf-glibc, I will need arm-linux-gnueabihf-gcc-stage2>=9.2.0-4, which arm-linux-gnueabihf-gcc does provide, but I cannot install that because of the glibc version.

How can I break this cycle, other than removing all of the arm-linux-gnueabihf packagesd and reinstalling them in order?

mikro commented on 2019-05-22 15:00 (UTC)

There is no need to mess with any order, just install arm-linux-gnueabihf-gcc and arm-linux-gnueabihf-glibc together.

However I'm getting a failure anyway, see my comment here: https://aur.archlinux.org/packages/arm-linux-gnueabihf-glibc-headers/#comment-694530

tavianator commented on 2019-02-05 01:45 (UTC)

@TheSaint: Uh because that's how you build a cross-toolchain? If you have a better way please let me know! I think it's possible to do 2 stages of GCC instead of 3 but I haven't gotten it working. At least my install.sh script should avoid wasting bandwidth, as it symlinks the glibc and gcc tarballs to avoid re-downloading them.

TheSaint commented on 2019-02-04 01:42 (UTC) (edited on 2019-02-04 02:00 (UTC) by TheSaint)

Today I got an update, but there's no order that the aur helper will respect. I currently using pikaur. So I presume that the entire update should be packaged with one only script as you mentioned, which is presumably the install.sh I followed your proposed order, but still have to discard a package because of conflicts. gcc-stage2 discards gcc-stage1 glibc discards glibc-headers gcc discards gcc-stage2

Why should we bear for such bandwidth & time wastage ?

crazySocket commented on 2019-01-27 15:04 (UTC) (edited on 2019-01-27 15:05 (UTC) by crazySocket)

Package as is does not allow for -static flag for gcc. If you try you get error "/usr/bin/arm-linux-gnueabihf-ld: cannot find -lstdc++".

The solution is to build libstdc++.a yourself. I had to inspect PKGBUILD for source url, compile as described there http://www.linuxfromscratch.org/lfs/view/stable-systemd/chapter05/gcc-libstdc++.html, then move libstdc++.a into /usr/arm-linux-gnueabihf. What could be avoided if only both shared and static version of stdlib were build by default.

I think package should have libstdc++.a included. At least I would appreciate that.

tavianator commented on 2018-08-15 15:55 (UTC) (edited on 2018-08-15 15:56 (UTC) by tavianator)

@TheSaint: The correct order can be seen here: https://github.com/tavianator/arch-rpi-cross/blob/master/install.sh

It is

arm-linux-gnueabihf-binutils
arm-linux-gnueabihf-gcc-stage1
arm-linux-gnueabihf-linux-api-headers
arm-linux-gnueabihf-glibc-headers
arm-linux-gnueabihf-gcc-stage2
arm-linux-gnueabihf-glibc
arm-linux-gnueabihf-gcc

The dependencies and provides have been set up so that AUR helpers should (hopefully) figure that out automatically.

TheSaint commented on 2018-08-15 15:49 (UTC)

To compile this package is necessary arm-linux-gnueabihf-binutils, which require arm-linux-gnueabihf-gcc-stage2. But also the arm-linux-gnueabihf-linux-api-headers is in the dependencies list, which require arm-linux-gnueabihf-gcc-stage1, but then there's a conflict with arm-linux-gnueabihf-gcc-stage2. Then also arm-linux-gnueabihf-glibc-headers are in conflict with arm-linux-gnueabihf-glibc. So what is the right one and save us to download the wrong one ?

zerofrost commented on 2018-06-27 14:39 (UTC)

For anyone having public key issues, I had to do gpg --recv-keys 16792B4EA25340F8

loadlover commented on 2018-02-09 17:45 (UTC)

Please ignore my previous comment as I have solved the issue (undeclared env variables) by removing C/C++ entries in my .bashrc.

loadlover commented on 2018-02-09 15:17 (UTC)

I'm getting the following errors. Can anyone help pls? I'm not very experienced at this..

error: ‘DEFAULT_GENERATE_ELF_STT_COMMON’ undeclared here (not in a function); did you mean ‘BFD_USE_ELF_STT_COMMON’? error: ‘TARGET_ALIAS’ undeclared (first use in this function); did you mean ‘TARGET_ARCH’? error: ‘TARGET_ALIAS’ undeclared (first use in this function); did you mean ‘TARGET_ARCH’? error: ‘TARGET_CANONICAL’ undeclared (first use in this function); did you mean ‘TARGET_ALIAS’? error: ‘TARGET_CPU’ undeclared (first use in this function); did you mean ‘TARGET_ARCH’?

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »