Arm linux gnueabihf version

Package: g++-arm-linux-gnueabihf (4:7.4.0-1ubuntu2.3 and others) [ security]

Links for g++-arm-linux-gnueabihf

Ubuntu Resources:

Maintainer:

Please consider filing a bug or asking a question via Launchpad before contacting the maintainer directly.

Original Maintainers (usually from Debian):

• Debian GCC Maintainers (Mail Archive)
• Matthias Klose

It should generally not be necessary for users to contact the original maintainer.

Similar packages:

GNU C++ compiler for the armhf architecture

Other Packages Related to g++-arm-linux-gnueabihf

depends

recommends

suggests

enhances

• dep: cpp-arm-linux-gnueabihf (>= 4:7.3.0-3ubuntu2) [arm64] GNU C preprocessor (cpp) for the armhf architecture dep: cpp-arm-linux-gnueabihf (>= 4:7.4.0-1ubuntu2.3) [not arm64]
• dep: g++-7-arm-linux-gnueabihf (>= 7.3.0-12

  ) [arm64] GNU C++ compiler (cross compiler for armhf architecture) dep: g++-7-arm-linux-gnueabihf (>= 7.4.0-1

  ) [not arm64]

• dep: gcc-arm-linux-gnueabihf (>= 4:7.3.0-3ubuntu2) [arm64] GNU C compiler for the armhf architecture dep: gcc-arm-linux-gnueabihf (>= 4:7.4.0-1ubuntu2.3) [not arm64]

Download g++-arm-linux-gnueabihf

Download for all available architectures

Architecture	Version	Package Size	Installed Size	Files
amd64	4:7.4.0-1ubuntu2.3	1.1 kB	11.0 kB	[list of files]
arm64	4:7.3.0-3ubuntu2	1.1 kB	11.0 kB	[list of files]
i386	4:7.4.0-1ubuntu2.3	1.1 kB	11.0 kB	[list of files]

This page is also available in the following languages:

Content Copyright © 2021 Canonical Ltd.; See license terms. Ubuntu is a trademark of Canonical Ltd. Learn more about this site.

Источник

Arch Linux User Repository

Search Criteria

Package Details: arm-linux-gnueabihf-gcc 11.2.0-2

Package Actions

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 (arm-linux-gnueabihf)
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=11.2.0, arm-linux-gnueabihf-gcc-stage2=11.2.0
Replaces:	arm-linux-gnueabihf-gcc-stage1, arm-linux-gnueabihf-gcc-stage2
Submitter:	tavianator
Maintainer:	razykov
Last Packager:	razykov
Votes:	75
Popularity:	1.23
First Submitted:	2015-09-14 15:41
Last Updated:	2021-10-09 08:31

Dependencies (7)

Required by (7)

• arm-linux-gnueabihf-armcl-neon(make)
• arm-linux-gnueabihf-glibc (requires arm-linux-gnueabihf-gcc-stage2) (make)
• arm-linux-gnueabihf-glibc-headers (requires arm-linux-gnueabihf-gcc-stage1) (make)
• arm-linux-gnueabihf-musl(make)
• arm-linux-gnueabihf-ncurses(make)
• arm-linux-gnueabihf-openblas-lapack-openmp(make)
• hakchi-git(make)

Sources (6)

Latest Comments

xzz53 commented on 2021-10-08 21:01

isl.gforge.inria.fr seems to be gone for good, so can’t download isl-0.24.tar.xz needed for this recipe. It’s now available via [1]. More details: [2].

aguegu commented on 2021-07-08 11:08

if building failed, try to add these two lines to PKGBUILD.

felipebalbi commented on 2021-06-30 09:21

Getting unknown key when trying to install stage1.

UPDATE: manually importing the key worked fine

smallAndSimple commented on 2021-06-05 11:52

Every single time an update comes out for this package, I need to install stage-1 -> stage-2 -> this. Is it possible to update directly without having to reinstall stage-1 and stage-2 every single time?

Edit: the problem is arm-linux-gnueabihf-glibc, which requires a newer gcc, but the newer gcc requires the newer glibc. Only way to break the cycle is to install the new stage-2, which requires the new stage-1.

mtudan commented on 2021-03-17 09:35

Got the following error with paru :

JanSurft commented on 2021-03-05 13:55

Is there a straight forward way to also provide the libstdc++.a static library together with the shared?

I can only see the *.so files of libstdc++ and I would need the static one for some cross compilation issues.

@smallAndSimple: it worked perfectly the way you described it

smallAndSimple commented on 2021-02-20 15:09

Edit: this is about the missing libctf problem.

I digged around a bit, and the actual problem lies in arm-linux-gnueabihf-binutils. I did the following as a workaround:

Cleaned up all arm-linux-gnueabihf-* related stuff completely.

Download arm-linux-gnueabihf-binutils PKGBUILD and add —disable-libctf\ to the list of ./configure parameters

makepkg -sri to install arm-linux-gnueabihf-binutils

A less thorough approach might be possible. Also, libctf apparantly can do something useful with debug sections, so you might run into trouble down the line.

smallAndSimple commented on 2021-02-20 14:37

So, since the libctf.so.0 situation will probably not be solved very soon (https://bugs.archlinux.org/task/69567 is closed because of upstream), is there a way around it? Can you compile this without libctf?

CapSel commented on 2021-02-18 11:13

Can’t compile. libctf.so.0 is missing. Here is bug for it https://bugs.archlinux.org/task/69567

tayspen72 commented on 2021-01-31 18:56

@AchmadFathoni My mistake. I pasted them in the wrong order. It should be stage 1 -> stage 2 -> gcc. I called them progressive because stage 1 is used to build stage 2, stage 2 is used to build the final gcc.

Copyright © 2004-2021 aurweb Development Team.

AUR packages are user produced content. Any use of the provided files is at your own risk.

Источник

Пакет: gcc-arm-linux-gnueabihf (4:10.2.1-1)

Ссылки для gcc-arm-linux-gnueabihf

Ресурсы Debian:

Исходный код gcc-defaults:

Сопровождающие:

Подобные пакеты:

GNU C compiler for the armhf architecture

This is the GNU C compiler, a fairly portable optimizing compiler for C.

This is a dependency package providing the default GNU C cross-compiler for the armhf architecture.

Другие пакеты, относящиеся к gcc-arm-linux-gnueabihf

зависимости

рекомендации

предложения

enhances

• dep: cpp-arm-linux-gnueabihf (= 4:10.2.1-1) GNU C preprocessor (cpp) for the armhf architecture
• dep: gcc-10-arm-linux-gnueabihf (>= 10.2.1-3

  ) GNU C compiler (cross compiler for armhf architecture)

• rec: libc6-dev-armhf-cross GNU C Library: Development Libraries and Header Files (for cross-compiling) или libc-dev-armhf-cross виртуальный пакет, предоставляемый libc6-dev-armhf-cross

• sug: autoconf automatic configure script builder
• sug: automake Tool for generating GNU Standards-compliant Makefiles
• sug: bison YACC-compatible parser generator
• sug: flex fast lexical analyzer generator
• sug: gcc-doc documentation for the GNU compilers (gcc, gobjc, g++)
• sug: gdb-arm-linux-gnueabihf Пакет недоступен
• sug: libtool Сценарий сопровождения общих библиотек
• sug: make утилита управления компиляцией
• sug: manpages-dev Manual pages about using GNU/Linux for development

Загрузка gcc-arm-linux-gnueabihf

Загрузить для всех доступных архитектур

Архитектура	Размер пакета	В установленном виде	Файлы
amd64	1,4 Кб	24,0 Кб	[список файлов]
arm64	1,4 Кб	24,0 Кб	[список файлов]
i386	1,4 Кб	24,0 Кб	[список файлов]
ppc64el	1,4 Кб	24,0 Кб	[список файлов]
x32 (неофициальный перенос)	1,4 Кб	24,0 Кб	[список файлов]

Эта страница также доступна на следующих языках (Как установить язык по умолчанию):

Чтобы сообщить о проблеме, связанной с веб-сайтом, отправьте сообщение (на английском) в список рассылки debian-www@lists.debian.org. Прочую контактную информацию см. на странице Debian Как с нами связаться.

Авторские права © 1997 — 2021 SPI Inc.; См. условия лицензии. Debian это торговый знак компании SPI Inc. Об этом сайте.

Источник

Пакет: gcc-arm-linux-gnueabihf (4:10.2.1-1)

Ссылки для gcc-arm-linux-gnueabihf

Ресурсы Debian:

Исходный код gcc-defaults:

Сопровождающие:

Подобные пакеты:

GNU C compiler for the armhf architecture

This is the GNU C compiler, a fairly portable optimizing compiler for C.

This is a dependency package providing the default GNU C cross-compiler for the armhf architecture.

Другие пакеты, относящиеся к gcc-arm-linux-gnueabihf

зависимости

рекомендации

предложения

enhances

• dep: cpp-arm-linux-gnueabihf (= 4:10.2.1-1) GNU C preprocessor (cpp) for the armhf architecture
• dep: gcc-10-arm-linux-gnueabihf (>= 10.2.1-3

  ) GNU C compiler (cross compiler for armhf architecture)

• rec: libc6-dev-armhf-cross GNU C Library: Development Libraries and Header Files (for cross-compiling) или libc-dev-armhf-cross виртуальный пакет, предоставляемый libc6-dev-armhf-cross

• sug: autoconf automatic configure script builder
• sug: automake Tool for generating GNU Standards-compliant Makefiles
• sug: bison YACC-compatible parser generator
• sug: flex fast lexical analyzer generator
• sug: gcc-doc documentation for the GNU compilers (gcc, gobjc, g++)
• sug: gdb-arm-linux-gnueabihf Пакет недоступен
• sug: libtool Сценарий сопровождения общих библиотек
• sug: make утилита управления компиляцией
• sug: manpages-dev Manual pages about using GNU/Linux for development

Загрузка gcc-arm-linux-gnueabihf

Загрузить для всех доступных архитектур

Архитектура	Размер пакета	В установленном виде	Файлы
amd64	1,4 Кб	24,0 Кб	[список файлов]
arm64	1,4 Кб	24,0 Кб	[список файлов]
i386	1,4 Кб	24,0 Кб	[список файлов]
ppc64el	1,4 Кб	24,0 Кб	[список файлов]
x32 (неофициальный перенос)	1,4 Кб	24,0 Кб	[список файлов]

Эта страница также доступна на следующих языках (Как установить язык по умолчанию):

Чтобы сообщить о проблеме, связанной с веб-сайтом, отправьте сообщение (на английском) в список рассылки debian-www@lists.debian.org. Прочую контактную информацию см. на странице Debian Как с нами связаться.

Авторские права © 1997 — 2021 SPI Inc.; См. условия лицензии. Debian это торговый знак компании SPI Inc. Об этом сайте.

Источник

How to switch the version of arm-linux-gnueabihf-gcc?

I would like to use version 5 of arm-linux-gnueabihf-gcc .

So I installed it via:

But now when I do gcc —version it will tell me it’s version 7.

How do I tell it to use the older version?

Or do I have to uninstall the newer version completely?

1 Answer 1

You can run arm-linux-gnueabihf-gcc-5 instead of gcc .

This file list includes the names of the other tools the gcc-5-arm-linux-gnueabihf package places in /usr/bin , which you may find useful. (You didn’t mention what release you’re running but I’m guessing it’s 18.04, since that release is a popular LTS and it defaults to version 7.)

Note that even if you wanted to use the default version, unless you’ve changed what /usr/bin/gcc points to (which I don’t recommend), the gcc command is running a GCC compiler that generates native executables. This won’t be an ARM compiler unless your Ubuntu system is running on ARM. To run the default version of the GCC cross compiler for armhf, use arm-linux-gnueabihf-gcc (and see this file list).

Multiple versions of both native and cross compilers can be installed on the same system at the same time. Only the default version of the native GCC compiler is typically invoked with the gcc command, however. Other commands have a toolchain prefix, a version suffix, or (in this case) both. This is the case even when that non-default compiler is the only compiler installed on the system.

If you really must make gcc call that compiler.

If you need gcc to call that compiler because some other build tool, like make is calling gcc , the best approach is usually to reconfigure that other tool or to set the CC environment variable to the compiler you want. Just making gcc run the compiler you need may also not be sufficient, because the names of other tools will still run the native versions.

With that said, assuming your your Ubuntu system is not an armhf system but you still really want gcc to run the arm-linux-gnueabihf-gcc-5 cross compiler, you have a few options. You could replace the /usr/bin/gcc symlink (which on 18.04 links to gcc-7 ), but I recommend against that. Doing that is likely to break anything that assumes gcc is a native compiler, and may either interfere with or be undone by future package management operations.

Instead, you could put a gcc symlink to arm-linux-gnueabihf-gcc-5 in your user’s private bin directory

/bin . The default per-user

/.profile file adds that directory to $PATH when you log in, if the directory exists. Automated builds (like when you run ./configure or cmake .. and then make ) that you don’t customize usually use cc , which will continue to be a symlink to a native compiler, so this shouldn’t break things.

Personally, I would not want to do even this, because I would myself become confused. I prefer that it always be immediately clear what platform my compiler targets, when it is a cross compiler.

Источник