Gcc Command not found in buildroot

[RakeshExaleap]

Hi everyone,

I cloned Freedom-u-SDK and built-in x86 and it's created all the images based on riscv64. Now i want to test qemu-simulator by the command make qemu, Then it gone to the qemu-simulator, i'm trying to run hello world program over there using gcc compiler but it's showing the following Error.

gcc --v

-sh: gcc: not found So how to enable gcc-compiler inside the Freedom-u-sdk and also how to add packages.

Thanks

[jim-wilson]

buildroot is a build it from scratch system. There is no package server, and hence no way to add packages. You can change the buildroot configuration if you want more packages to be built. See the buildroot documentation.

But if you just want a real OS and don't need to build it yourself, then you are probably better off using one of the linux distros, like Fedora, Debian, or OpenSuSe. I use Fedora myself. https://fedoraproject.org/wiki/Architectures/RISC-V/Installing

[RakeshExaleap]

Hi sir,

I gone through that mail, you did in Fedora but we are trying to do in Ubuntu-16.04 and next version of ubuntu. Can you please suggest me a steps to do it in ubuntu. How to enable the gcc in Freedom-u-SDK(buildroot).

Also send me the Details of Fedora version, Arch.

Thanks

---

From: Jim Wilson [email protected] Sent: 23 May 2019 11:31:26 To: sifive/freedom-u-sdk Cc: Rakesh H S; Author Subject: Re: [sifive/freedom-u-sdk] Gcc Command not found in buildroot (#110)

buildroot is a build it from scratch system. There is no package server, and hence no way to add packages. You can change the buildroot configuration if you want more packages to be built. See the buildroot documentation.

But if you just want a real OS and don't need to build it yourself, then you are probably better off using one of the linux distros, like Fedora, Debian, or OpenSuSe. I use Fedora myself. https://fedoraproject.org/wiki/Architectures/RISC-V/Installing

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/sifive/freedom-u-sdk/issues/110?email_source=notifications&email_token=AMEYHWPJA2GSQT7XHBJUUT3PW22E5A5CNFSM4HPEG2G2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWCTGWI#issuecomment-495268697, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMEYHWOD5PTCNUSJCTGY5HLPW22E5ANCNFSM4HPEG2GQ.

[tmagik]

you can try the ‘make format-demo-image’ target which will download a Debian image that you can install compilers with.

You’ll need to edit the uEnv.txt file on the first partition of the SDcard to boot from Debian instead of the buildroot initramfs.

On May 24, 2019, at 3:14 AM, RakeshExaleap [email protected] wrote:

Hi sir,

I gone through that mail, you did in Fedora but we are trying to do in Ubuntu-16.04 and next version of ubuntu. Can you please suggest me a steps to do it in ubuntu. How to enable the gcc in Freedom-u-SDK(buildroot).

Also send me the Details of Fedora version, Arch.

Thanks

---

From: Jim Wilson [email protected] Sent: 23 May 2019 11:31:26 To: sifive/freedom-u-sdk Cc: Rakesh H S; Author Subject: Re: [sifive/freedom-u-sdk] Gcc Command not found in buildroot (#110)

buildroot is a build it from scratch system. There is no package server, and hence no way to add packages. You can change the buildroot configuration if you want more packages to be built. See the buildroot documentation.

But if you just want a real OS and don't need to build it yourself, then you are probably better off using one of the linux distros, like Fedora, Debian, or OpenSuSe. I use Fedora myself. https://fedoraproject.org/wiki/Architectures/RISC-V/Installing

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/sifive/freedom-u-sdk/issues/110?email_source=notifications&email_token=AMEYHWPJA2GSQT7XHBJUUT3PW22E5A5CNFSM4HPEG2G2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWCTGWI#issuecomment-495268697, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMEYHWOD5PTCNUSJCTGY5HLPW22E5ANCNFSM4HPEG2GQ. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[tprrt]

This issue is no longer relevant.