Re: Request:How to install gcc in ubuntu18.04 int the way of offline?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



What is MCU? Microcontroller unit? What's the relationship to apt-get?

The problem is just as the error message says. You can't build gcc without
an existing C compiler. Perhaps your real problem is getting "apt-get
install" to work, and not building gcc from scratch without an existing
compiler.

On Fri, Oct 15, 2021 at 1:27 PM 李金龙 via Gcc-help <gcc-help@xxxxxxxxxxx>
wrote:

> Dear Ladies or Gentelman:
>
>     My MCU can’t connect to the ubuntu’s apt-source(like Ubuntu,aliyun,163
> etc). So It certainly can’t use the command “sudo apt-get install gcc" to
> make it all right.
>     So I want to know how to install gcc in the way of offline in
> ubuntu18.04.
>     I search the solution from the internet then find one:
> https://blog.csdn.net/weixin_40671425/article/details/92762839. But
> unfortunately, it worked wrong on the steps: " ./configure
> --disable-multilib --prefix=/data2/upchen/MyPackages/gcc/gcc-5.4.0
> --enable-add-ons ". The result is as follows:
> ---------------------linux@test:~/gcc-5.4.0$ ./configure
> --disable-multilib --prefix=/data2/upchen/MyPackages/gcc/gcc-5.4.0
> --enable-add-ons
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
> checking target system type... x86_64-unknown-linux-gnu
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether ln works... yes
> checking whether ln -s works... yes
> checking for a sed that does not truncate output... /bin/sed
> checking for gawk... gawk
> checking for libatomic support... yes
> checking for libcilkrts support... yes
> checking for libitm support... yes
> checking for libsanitizer support... yes
> checking for libvtv support... yes
> checking for gcc... no
> checking for cc... no
> checking for cl.exe... no
> configure: error: in `/home/linux/gcc-5.4.0':
> configure: error: no acceptable C compiler found in $PATH
> See `config.log' for more details.
>
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> the config.log is in attachment.
> Thanks for the kind of selfless help in good faith.
>
>
>




[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux