How to cross compile older version of GCC under Debian? The 2019 Stack Overflow Developer Survey Results Are InHow to build the GCC cross compiler for Cross Linux From Scratch (CLFS) for Beagleboard?compile software with older version of gcc and linux kernelmake: xscale_be-gcc: Command not foundgcc installation on CentOS 6.6: configure issueinstall older version of gcc - debian sidHow to compile Solaris executable under Debian?gcc cross compilation failsChoose gcc version to compile vmware modulesHow to install a functional ARM cross-gcc toolchain on Ubuntu 18.04?How do I install newer or older versions of GCC on Devuan/Debian?

Should I use my personal or workplace e-mail when registering to external websites for work purpose?

Limit the amount of RAM Mathematica may access?

Is there a name of the flying bionic bird?

Why is Grand Jury testimony secret?

Could a US political party gain complete control over the government by removing checks & balances?

It's possible to achieve negative score?

Is domain driven design an anti-SQL pattern?

Could JWST stay at L2 "forever"?

How can I fix this gap between bookcases I made?

What do the Banks children have against barley water?

Inversion Puzzle

What does "rabbited" mean/imply in this sentence?

Dual Citizen. Exited the US on Italian passport recently

Is "plugging out" electronic devices an American expression?

What is the best strategy for white in this position?

What do hard-Brexiteers want with respect to the Irish border?

Is this food a bread or a loaf?

Can the Protection from Evil and Good spell be used on the caster?

Are USB sockets on wall outlets live all the time, even when the switch is off?

Can't find the latex code for the ⍎ (down tack jot) symbol

Does it makes sense to buy a new cycle to learn riding?

Why did Howard Stark use all the Vibranium they had on a prototype shield?

Landlord wants to switch my lease to a "Land contract" to "get back at the city"

Monty Hall variation



How to cross compile older version of GCC under Debian?



The 2019 Stack Overflow Developer Survey Results Are InHow to build the GCC cross compiler for Cross Linux From Scratch (CLFS) for Beagleboard?compile software with older version of gcc and linux kernelmake: xscale_be-gcc: Command not foundgcc installation on CentOS 6.6: configure issueinstall older version of gcc - debian sidHow to compile Solaris executable under Debian?gcc cross compilation failsChoose gcc version to compile vmware modulesHow to install a functional ARM cross-gcc toolchain on Ubuntu 18.04?How do I install newer or older versions of GCC on Devuan/Debian?



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








0















I'm trying to build an older version of GCC toolchain for ARM under x86 because there is a bug with GCC > v5 for Cortex-M0. I'm following the combination of the following instructions:



  • https://stackoverflow.com/a/10662297/1952991

  • https://stackoverflow.com/q/24559878/1952991

So my overall procedure is as follows:



# Download GCC-5.5.0 from https://gcc.gnu.org/releases.html
VERSION="5.5.0"
tar xzf gcc-$VERSION.tar.gz
cd gcc-$VERSION
./contrib/download_prerequisites
cd ..
mkdir objdir
cd objdir
../gcc-5.5.0/configure --prefix=$HOME/embedded/gcc-arm-none-eabi-5.5.0 --disable-multilib --enable-languages=c,c++ --target=arm-none-eabi
make -j$(nproc) # use all cores
make install


Then the following files are created under ~/embedded/arm-none-eabi-5.5.0/bin/:



arm-none-eabi-c++ arm-none-eabi-gcc-5.5.0 arm-none-eabi-gcov
arm-none-eabi-cpp arm-none-eabi-gcc-ar arm-none-eabi-gcov-dump
arm-none-eabi-g++ arm-none-eabi-gcc-nm arm-none-eabi-gcov-tool
arm-none-eabi-gcc arm-none-eabi-gcc-ranlib


However, the following command fails:



arm-none-eabi-gcc -c -mcpu=cortex-m0 -O0 -ggdb (......)

Compiling crt0_v6m.S
as: unrecognized option '-mcpu=cortex-m0'
make: *** [/home/ceremcem/ChibiOS/os/common/startup/ARMCMx/compilers/GCC/rules.mk:253: build/obj/crt0_v6m.o] Error 1


I can verify that the command uses newly produced binaries:



$ which arm-none-eabi-gcc
/home/ceremcem/embedded/arm-none-eabi-5.5.0/bin//arm-none-eabi-gcc


This means that the newly compiled GCC toolchain does not accept the mcpu option. What could be wrong with building the GCC toolchain phase that causes -mcpu=cortex-m0 option to fail?










share|improve this question
























  • Have you installed the appropriate cross-binutils? It’s as that’s complaining, and that’s part of binutils.

    – Stephen Kitt
    2 days ago











  • Yes and no. I'm already installed and using arm-none-eabi-gcc v7.3.1 so I assumed the rest of the dependencies are already satisfied by the v7.3.1 installation and ./contrib/download_prerequisites command. Should I build something else?

    – ceremcem
    2 days ago











  • What version of Debian are you using?

    – Stephen Kitt
    2 days ago











  • I'm using Debian Buster/sid (testing). I would like to achieve a distro agnostic solution though.

    – ceremcem
    2 days ago











  • Right, I understand that, I was wondering since Debian 9 has gcc-arm-none-eabi version 5.4.1.

    – Stephen Kitt
    2 days ago

















0















I'm trying to build an older version of GCC toolchain for ARM under x86 because there is a bug with GCC > v5 for Cortex-M0. I'm following the combination of the following instructions:



  • https://stackoverflow.com/a/10662297/1952991

  • https://stackoverflow.com/q/24559878/1952991

So my overall procedure is as follows:



# Download GCC-5.5.0 from https://gcc.gnu.org/releases.html
VERSION="5.5.0"
tar xzf gcc-$VERSION.tar.gz
cd gcc-$VERSION
./contrib/download_prerequisites
cd ..
mkdir objdir
cd objdir
../gcc-5.5.0/configure --prefix=$HOME/embedded/gcc-arm-none-eabi-5.5.0 --disable-multilib --enable-languages=c,c++ --target=arm-none-eabi
make -j$(nproc) # use all cores
make install


Then the following files are created under ~/embedded/arm-none-eabi-5.5.0/bin/:



arm-none-eabi-c++ arm-none-eabi-gcc-5.5.0 arm-none-eabi-gcov
arm-none-eabi-cpp arm-none-eabi-gcc-ar arm-none-eabi-gcov-dump
arm-none-eabi-g++ arm-none-eabi-gcc-nm arm-none-eabi-gcov-tool
arm-none-eabi-gcc arm-none-eabi-gcc-ranlib


However, the following command fails:



arm-none-eabi-gcc -c -mcpu=cortex-m0 -O0 -ggdb (......)

Compiling crt0_v6m.S
as: unrecognized option '-mcpu=cortex-m0'
make: *** [/home/ceremcem/ChibiOS/os/common/startup/ARMCMx/compilers/GCC/rules.mk:253: build/obj/crt0_v6m.o] Error 1


I can verify that the command uses newly produced binaries:



$ which arm-none-eabi-gcc
/home/ceremcem/embedded/arm-none-eabi-5.5.0/bin//arm-none-eabi-gcc


This means that the newly compiled GCC toolchain does not accept the mcpu option. What could be wrong with building the GCC toolchain phase that causes -mcpu=cortex-m0 option to fail?










share|improve this question
























  • Have you installed the appropriate cross-binutils? It’s as that’s complaining, and that’s part of binutils.

    – Stephen Kitt
    2 days ago











  • Yes and no. I'm already installed and using arm-none-eabi-gcc v7.3.1 so I assumed the rest of the dependencies are already satisfied by the v7.3.1 installation and ./contrib/download_prerequisites command. Should I build something else?

    – ceremcem
    2 days ago











  • What version of Debian are you using?

    – Stephen Kitt
    2 days ago











  • I'm using Debian Buster/sid (testing). I would like to achieve a distro agnostic solution though.

    – ceremcem
    2 days ago











  • Right, I understand that, I was wondering since Debian 9 has gcc-arm-none-eabi version 5.4.1.

    – Stephen Kitt
    2 days ago













0












0








0


1






I'm trying to build an older version of GCC toolchain for ARM under x86 because there is a bug with GCC > v5 for Cortex-M0. I'm following the combination of the following instructions:



  • https://stackoverflow.com/a/10662297/1952991

  • https://stackoverflow.com/q/24559878/1952991

So my overall procedure is as follows:



# Download GCC-5.5.0 from https://gcc.gnu.org/releases.html
VERSION="5.5.0"
tar xzf gcc-$VERSION.tar.gz
cd gcc-$VERSION
./contrib/download_prerequisites
cd ..
mkdir objdir
cd objdir
../gcc-5.5.0/configure --prefix=$HOME/embedded/gcc-arm-none-eabi-5.5.0 --disable-multilib --enable-languages=c,c++ --target=arm-none-eabi
make -j$(nproc) # use all cores
make install


Then the following files are created under ~/embedded/arm-none-eabi-5.5.0/bin/:



arm-none-eabi-c++ arm-none-eabi-gcc-5.5.0 arm-none-eabi-gcov
arm-none-eabi-cpp arm-none-eabi-gcc-ar arm-none-eabi-gcov-dump
arm-none-eabi-g++ arm-none-eabi-gcc-nm arm-none-eabi-gcov-tool
arm-none-eabi-gcc arm-none-eabi-gcc-ranlib


However, the following command fails:



arm-none-eabi-gcc -c -mcpu=cortex-m0 -O0 -ggdb (......)

Compiling crt0_v6m.S
as: unrecognized option '-mcpu=cortex-m0'
make: *** [/home/ceremcem/ChibiOS/os/common/startup/ARMCMx/compilers/GCC/rules.mk:253: build/obj/crt0_v6m.o] Error 1


I can verify that the command uses newly produced binaries:



$ which arm-none-eabi-gcc
/home/ceremcem/embedded/arm-none-eabi-5.5.0/bin//arm-none-eabi-gcc


This means that the newly compiled GCC toolchain does not accept the mcpu option. What could be wrong with building the GCC toolchain phase that causes -mcpu=cortex-m0 option to fail?










share|improve this question
















I'm trying to build an older version of GCC toolchain for ARM under x86 because there is a bug with GCC > v5 for Cortex-M0. I'm following the combination of the following instructions:



  • https://stackoverflow.com/a/10662297/1952991

  • https://stackoverflow.com/q/24559878/1952991

So my overall procedure is as follows:



# Download GCC-5.5.0 from https://gcc.gnu.org/releases.html
VERSION="5.5.0"
tar xzf gcc-$VERSION.tar.gz
cd gcc-$VERSION
./contrib/download_prerequisites
cd ..
mkdir objdir
cd objdir
../gcc-5.5.0/configure --prefix=$HOME/embedded/gcc-arm-none-eabi-5.5.0 --disable-multilib --enable-languages=c,c++ --target=arm-none-eabi
make -j$(nproc) # use all cores
make install


Then the following files are created under ~/embedded/arm-none-eabi-5.5.0/bin/:



arm-none-eabi-c++ arm-none-eabi-gcc-5.5.0 arm-none-eabi-gcov
arm-none-eabi-cpp arm-none-eabi-gcc-ar arm-none-eabi-gcov-dump
arm-none-eabi-g++ arm-none-eabi-gcc-nm arm-none-eabi-gcov-tool
arm-none-eabi-gcc arm-none-eabi-gcc-ranlib


However, the following command fails:



arm-none-eabi-gcc -c -mcpu=cortex-m0 -O0 -ggdb (......)

Compiling crt0_v6m.S
as: unrecognized option '-mcpu=cortex-m0'
make: *** [/home/ceremcem/ChibiOS/os/common/startup/ARMCMx/compilers/GCC/rules.mk:253: build/obj/crt0_v6m.o] Error 1


I can verify that the command uses newly produced binaries:



$ which arm-none-eabi-gcc
/home/ceremcem/embedded/arm-none-eabi-5.5.0/bin//arm-none-eabi-gcc


This means that the newly compiled GCC toolchain does not accept the mcpu option. What could be wrong with building the GCC toolchain phase that causes -mcpu=cortex-m0 option to fail?







gcc arm compiler






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 2 days ago







ceremcem

















asked 2 days ago









ceremcemceremcem

5591622




5591622












  • Have you installed the appropriate cross-binutils? It’s as that’s complaining, and that’s part of binutils.

    – Stephen Kitt
    2 days ago











  • Yes and no. I'm already installed and using arm-none-eabi-gcc v7.3.1 so I assumed the rest of the dependencies are already satisfied by the v7.3.1 installation and ./contrib/download_prerequisites command. Should I build something else?

    – ceremcem
    2 days ago











  • What version of Debian are you using?

    – Stephen Kitt
    2 days ago











  • I'm using Debian Buster/sid (testing). I would like to achieve a distro agnostic solution though.

    – ceremcem
    2 days ago











  • Right, I understand that, I was wondering since Debian 9 has gcc-arm-none-eabi version 5.4.1.

    – Stephen Kitt
    2 days ago

















  • Have you installed the appropriate cross-binutils? It’s as that’s complaining, and that’s part of binutils.

    – Stephen Kitt
    2 days ago











  • Yes and no. I'm already installed and using arm-none-eabi-gcc v7.3.1 so I assumed the rest of the dependencies are already satisfied by the v7.3.1 installation and ./contrib/download_prerequisites command. Should I build something else?

    – ceremcem
    2 days ago











  • What version of Debian are you using?

    – Stephen Kitt
    2 days ago











  • I'm using Debian Buster/sid (testing). I would like to achieve a distro agnostic solution though.

    – ceremcem
    2 days ago











  • Right, I understand that, I was wondering since Debian 9 has gcc-arm-none-eabi version 5.4.1.

    – Stephen Kitt
    2 days ago
















Have you installed the appropriate cross-binutils? It’s as that’s complaining, and that’s part of binutils.

– Stephen Kitt
2 days ago





Have you installed the appropriate cross-binutils? It’s as that’s complaining, and that’s part of binutils.

– Stephen Kitt
2 days ago













Yes and no. I'm already installed and using arm-none-eabi-gcc v7.3.1 so I assumed the rest of the dependencies are already satisfied by the v7.3.1 installation and ./contrib/download_prerequisites command. Should I build something else?

– ceremcem
2 days ago





Yes and no. I'm already installed and using arm-none-eabi-gcc v7.3.1 so I assumed the rest of the dependencies are already satisfied by the v7.3.1 installation and ./contrib/download_prerequisites command. Should I build something else?

– ceremcem
2 days ago













What version of Debian are you using?

– Stephen Kitt
2 days ago





What version of Debian are you using?

– Stephen Kitt
2 days ago













I'm using Debian Buster/sid (testing). I would like to achieve a distro agnostic solution though.

– ceremcem
2 days ago





I'm using Debian Buster/sid (testing). I would like to achieve a distro agnostic solution though.

– ceremcem
2 days ago













Right, I understand that, I was wondering since Debian 9 has gcc-arm-none-eabi version 5.4.1.

– Stephen Kitt
2 days ago





Right, I understand that, I was wondering since Debian 9 has gcc-arm-none-eabi version 5.4.1.

– Stephen Kitt
2 days ago










1 Answer
1






active

oldest

votes


















2














Your GCC doesn’t appear to be using the right as, and probably wouldn’t use the right ld either; you need to add



--with-as=/usr/bin/arm-none-eabi-as --with-ld=/usr/bin/arm-none-eabi-ld


to your ./configure line.



You’re also likely to run into issues related to Debian’s multi-arch approach, which GCC 5 doesn’t support directly. Your best bet is to download the last Debian package of GCC 5.5 in source form, and use that (with patches) to build your cross-compiler. Then it will use the ARM C library which was installed as a dependency of the cross-GCC package you installed.



dget https://snapshot.debian.org/archive/debian-debug/20180412T094604Z/pool/main/g/gcc-5/gcc-5_5.5.0-12.dsc
cd gcc-5-5.5.0
debian/rules patch


then configure and build as before. (Ignore the cross-building documentation in debian/README.cross.)






share|improve this answer

























  • This didn't solve all issues but made the problem proceed to another step: Now it can't find stdint.h while compiling an application, very much like the problem I've faced 4 years ago: stackoverflow.com/q/23973971/1952991

    – ceremcem
    2 days ago












  • That’s because it’s looking for headers in the upstream location, not in the multiarch location; see my updated answer for a fix.

    – Stephen Kitt
    2 days ago











  • No luck, very same issue persists. Note that the /usr/lib/gcc/arm-none-eabi/7.3.1/include/ folder contains many *.h files but the include folder in newly compiled gcc installation location is still empty.

    – ceremcem
    2 days ago











Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f511072%2fhow-to-cross-compile-older-version-of-gcc-under-debian%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









2














Your GCC doesn’t appear to be using the right as, and probably wouldn’t use the right ld either; you need to add



--with-as=/usr/bin/arm-none-eabi-as --with-ld=/usr/bin/arm-none-eabi-ld


to your ./configure line.



You’re also likely to run into issues related to Debian’s multi-arch approach, which GCC 5 doesn’t support directly. Your best bet is to download the last Debian package of GCC 5.5 in source form, and use that (with patches) to build your cross-compiler. Then it will use the ARM C library which was installed as a dependency of the cross-GCC package you installed.



dget https://snapshot.debian.org/archive/debian-debug/20180412T094604Z/pool/main/g/gcc-5/gcc-5_5.5.0-12.dsc
cd gcc-5-5.5.0
debian/rules patch


then configure and build as before. (Ignore the cross-building documentation in debian/README.cross.)






share|improve this answer

























  • This didn't solve all issues but made the problem proceed to another step: Now it can't find stdint.h while compiling an application, very much like the problem I've faced 4 years ago: stackoverflow.com/q/23973971/1952991

    – ceremcem
    2 days ago












  • That’s because it’s looking for headers in the upstream location, not in the multiarch location; see my updated answer for a fix.

    – Stephen Kitt
    2 days ago











  • No luck, very same issue persists. Note that the /usr/lib/gcc/arm-none-eabi/7.3.1/include/ folder contains many *.h files but the include folder in newly compiled gcc installation location is still empty.

    – ceremcem
    2 days ago















2














Your GCC doesn’t appear to be using the right as, and probably wouldn’t use the right ld either; you need to add



--with-as=/usr/bin/arm-none-eabi-as --with-ld=/usr/bin/arm-none-eabi-ld


to your ./configure line.



You’re also likely to run into issues related to Debian’s multi-arch approach, which GCC 5 doesn’t support directly. Your best bet is to download the last Debian package of GCC 5.5 in source form, and use that (with patches) to build your cross-compiler. Then it will use the ARM C library which was installed as a dependency of the cross-GCC package you installed.



dget https://snapshot.debian.org/archive/debian-debug/20180412T094604Z/pool/main/g/gcc-5/gcc-5_5.5.0-12.dsc
cd gcc-5-5.5.0
debian/rules patch


then configure and build as before. (Ignore the cross-building documentation in debian/README.cross.)






share|improve this answer

























  • This didn't solve all issues but made the problem proceed to another step: Now it can't find stdint.h while compiling an application, very much like the problem I've faced 4 years ago: stackoverflow.com/q/23973971/1952991

    – ceremcem
    2 days ago












  • That’s because it’s looking for headers in the upstream location, not in the multiarch location; see my updated answer for a fix.

    – Stephen Kitt
    2 days ago











  • No luck, very same issue persists. Note that the /usr/lib/gcc/arm-none-eabi/7.3.1/include/ folder contains many *.h files but the include folder in newly compiled gcc installation location is still empty.

    – ceremcem
    2 days ago













2












2








2







Your GCC doesn’t appear to be using the right as, and probably wouldn’t use the right ld either; you need to add



--with-as=/usr/bin/arm-none-eabi-as --with-ld=/usr/bin/arm-none-eabi-ld


to your ./configure line.



You’re also likely to run into issues related to Debian’s multi-arch approach, which GCC 5 doesn’t support directly. Your best bet is to download the last Debian package of GCC 5.5 in source form, and use that (with patches) to build your cross-compiler. Then it will use the ARM C library which was installed as a dependency of the cross-GCC package you installed.



dget https://snapshot.debian.org/archive/debian-debug/20180412T094604Z/pool/main/g/gcc-5/gcc-5_5.5.0-12.dsc
cd gcc-5-5.5.0
debian/rules patch


then configure and build as before. (Ignore the cross-building documentation in debian/README.cross.)






share|improve this answer















Your GCC doesn’t appear to be using the right as, and probably wouldn’t use the right ld either; you need to add



--with-as=/usr/bin/arm-none-eabi-as --with-ld=/usr/bin/arm-none-eabi-ld


to your ./configure line.



You’re also likely to run into issues related to Debian’s multi-arch approach, which GCC 5 doesn’t support directly. Your best bet is to download the last Debian package of GCC 5.5 in source form, and use that (with patches) to build your cross-compiler. Then it will use the ARM C library which was installed as a dependency of the cross-GCC package you installed.



dget https://snapshot.debian.org/archive/debian-debug/20180412T094604Z/pool/main/g/gcc-5/gcc-5_5.5.0-12.dsc
cd gcc-5-5.5.0
debian/rules patch


then configure and build as before. (Ignore the cross-building documentation in debian/README.cross.)







share|improve this answer














share|improve this answer



share|improve this answer








edited 2 days ago

























answered 2 days ago









Stephen KittStephen Kitt

181k25413492




181k25413492












  • This didn't solve all issues but made the problem proceed to another step: Now it can't find stdint.h while compiling an application, very much like the problem I've faced 4 years ago: stackoverflow.com/q/23973971/1952991

    – ceremcem
    2 days ago












  • That’s because it’s looking for headers in the upstream location, not in the multiarch location; see my updated answer for a fix.

    – Stephen Kitt
    2 days ago











  • No luck, very same issue persists. Note that the /usr/lib/gcc/arm-none-eabi/7.3.1/include/ folder contains many *.h files but the include folder in newly compiled gcc installation location is still empty.

    – ceremcem
    2 days ago

















  • This didn't solve all issues but made the problem proceed to another step: Now it can't find stdint.h while compiling an application, very much like the problem I've faced 4 years ago: stackoverflow.com/q/23973971/1952991

    – ceremcem
    2 days ago












  • That’s because it’s looking for headers in the upstream location, not in the multiarch location; see my updated answer for a fix.

    – Stephen Kitt
    2 days ago











  • No luck, very same issue persists. Note that the /usr/lib/gcc/arm-none-eabi/7.3.1/include/ folder contains many *.h files but the include folder in newly compiled gcc installation location is still empty.

    – ceremcem
    2 days ago
















This didn't solve all issues but made the problem proceed to another step: Now it can't find stdint.h while compiling an application, very much like the problem I've faced 4 years ago: stackoverflow.com/q/23973971/1952991

– ceremcem
2 days ago






This didn't solve all issues but made the problem proceed to another step: Now it can't find stdint.h while compiling an application, very much like the problem I've faced 4 years ago: stackoverflow.com/q/23973971/1952991

– ceremcem
2 days ago














That’s because it’s looking for headers in the upstream location, not in the multiarch location; see my updated answer for a fix.

– Stephen Kitt
2 days ago





That’s because it’s looking for headers in the upstream location, not in the multiarch location; see my updated answer for a fix.

– Stephen Kitt
2 days ago













No luck, very same issue persists. Note that the /usr/lib/gcc/arm-none-eabi/7.3.1/include/ folder contains many *.h files but the include folder in newly compiled gcc installation location is still empty.

– ceremcem
2 days ago





No luck, very same issue persists. Note that the /usr/lib/gcc/arm-none-eabi/7.3.1/include/ folder contains many *.h files but the include folder in newly compiled gcc installation location is still empty.

– ceremcem
2 days ago

















draft saved

draft discarded
















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f511072%2fhow-to-cross-compile-older-version-of-gcc-under-debian%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-arm, compiler, gcc

Popular posts from this blog

Frič See also Navigation menuinternal link

Identify plant with long narrow paired leaves and reddish stems Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?What is this plant with long sharp leaves? Is it a weed?What is this 3ft high, stalky plant, with mid sized narrow leaves?What is this young shrub with opposite ovate, crenate leaves and reddish stems?What is this plant with large broad serrated leaves?Identify this upright branching weed with long leaves and reddish stemsPlease help me identify this bulbous plant with long, broad leaves and white flowersWhat is this small annual with narrow gray/green leaves and rust colored daisy-type flowers?What is this chilli plant?Does anyone know what type of chilli plant this is?Help identify this plant

fontconfig warning: “/etc/fonts/fonts.conf”, line 100: unknown “element blank” The 2019 Stack Overflow Developer Survey Results Are In“tar: unrecognized option --warning” during 'apt-get install'How to fix Fontconfig errorHow do I figure out which font file is chosen for a system generic font alias?Why are some apt-get-installed fonts being ignored by fc-list, xfontsel, etc?Reload settings in /etc/fonts/conf.dTaking 30 seconds longer to boot after upgrade from jessie to stretchHow to match multiple font names with a single <match> element?Adding a custom font to fontconfigRemoving fonts from fontconfig <match> resultsBroken fonts after upgrading Firefox ESR to latest Firefox