After further investigation, the problem is indeed with the C compiler as one would expect from original error message.
So I tried to compile a simple c file:
helloworld.c
#include<stdio.h> main() { printf("Hello World"); }
In file included from /usr/include/features.h:447:0,
from /usr/include/bits/libc-header-start.h:33,
from /usr/include/stdio.h:27,
from helloword.c:1:
/usr/include/gnu/stubs.h:10:11: fatal error: gnu/stubs-64.h: No such file or directory
# include <gnu/stubs-64.h>
^~~~~~~~~~~~~~~~
compilation terminated.
Let’s confirm the file is not there
libc-version.h lib-names-32.h lib-names.h stubs-32.h stubs.h
One way to figure out what package provides a specific file is to run dnf provides:
sudo dnf provides /usr/include/gnu/stubs-64.h
Last metadata expiration check: 0:36:06 ago on Mon 15 Jan 2018 06:55:28 PM EST.
glibc-devel-2.26-21.fc27.x86_64 : Object files for development using standard C
: libraries.
Repo : updates
Matched from:
Filename : /usr/include/gnu/stubs-64.h
glibc-devel-2.26-15.fc27.x86_64 : Object files for development using standard C
: libraries.
Repo : fedora
Matched from:
Filename : /usr/include/gnu/stubs-64.h
I do have that package installed, maybe reinstalling it could fix somehting:
sudo dnf reinstall -y glibc-devel
but /usr/include/gnu/stubs-64.h is still not present.
sudo dnf list | grep glibc-devel
glibc-devel.i686 2.26-21.fc27 @updates
glibc-devel.x86_64 2.26-21.fc27 updates
According to provides command, my current version should provide that file, but I ran ls /usr/include/gnu/stubs-64.h and it’s still missing.
The system is a 64bit system:
Linux hpbenlocalhost 4.14.11-300.fc27.x86_64 #1 SMP Wed Jan 3 13:52:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Continuing investigation.
how to fix configure: error: C compiler cannot create executables
and this is the config.log
my system is ubuntu 14.04 and the system details say the os is 32 bit. any help would be great as the compiler fails on anytime I try to use it, not just with this install.
5 Answers 5
My guess would be that you have the basic C compiler installed, but not the headers for the standard library. Try:
[Edit: this produces similar symptoms, but wasn’t the case here. The CFLAGS answers appear to be correct.]
From the config.log :
The option is -O3 with the letter O , not the number 0 (zero). So, you should run, as given in the README:
Looks like your CFLAGS has a zero instead of capital O. That is invalid, and causing the compilation to fail. You can fix it, but really, look for a later version of the package which has been fixed.
I was having this exact same problem trying to install tivodecode on a base build of Linux Mint 17.3. I tried the:
command but with no effect. So I tried:
to install the latest C headers. I tried the ./configure command again with no variables and all went well. The make and make install commands also completed successfully. My recommendation is to make sure the latest C headers are installed and then run your ./configure command.
Источник
Unable to install a python version using pyenv on Fedora 27 with message ‘configure:4018: error: C compiler cannot create executables’ #1076
Comments
GabLeRoux commented Jan 15, 2018 •
install command
output
/python-fix/Python-3.4.2 Installing Python-3.4.2. patching file ./Lib/ssl.py patching file ./Modules/_ssl.c checking build system type. x86_64-unknown-linux-gnu checking host system type. x86_64-unknown-linux-gnu checking for —enable-universalsdk. no checking for —with-universal-archs. no checking MACHDEP. linux checking for —without-gcc. no checking for gcc. gcc checking whether the C compiler works. no configure: error: in `/tmp/python-build.20180115180746.18522/Python-3.4.2′: configure: error: C compiler cannot create executables See `config.log’ for more details BUILD FAILED (Fedora 27 using python-build 20160602) Inspect or clean up the working tree at /tmp/python-build.20180115180746.18522 Results logged to /tmp/python-build.20180115180746.18522.log Last 10 log lines: checking host system type. x86_64-unknown-linux-gnu checking for —enable-universalsdk. no checking for —with-universal-archs. no checking MACHDEP. linux checking for —without-gcc. no checking for gcc. gcc checking whether the C compiler works. no configure: error: in `/tmp/python-build.20180115180746.18522/Python-3.4.2′: configure: error: C compiler cannot create executables See `config.log’ for more details»>
I installed using pyenv/pyenv-installer and added the env flags to my
/.zshrc as mentioned after installation and restarted the shell.
I also installed all the required packages as mentioned in wiki’s home suggested-build-environment:
Note that it differs one from an other, I think this is also an issue, packages should be the same for both sections.
Источник
C++ compiler cannot create executables #738
Comments
thw1021 commented Jul 22, 2019
Dear developers,
I am trying to install SU2 in docker ubuntu 18.04 container so that I can easily share with partner. But I failed to compile the code with following errors:
I am sure that I have installed gcc/g++ successfully. You can see
I have uploaded the config.log file. Could you give me some suggestions, please?
config.log
The text was updated successfully, but these errors were encountered:
18.04.1) 7.4.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. (base) root@a5502ebdff64:/home# g++ -o hello hello.cc (base) root@a5502ebdff64:/home# ./hello Hello, World! I have uploaded the config.log file. Could you give me some suggestions, please? config.log — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub , or mute the thread .
thw1021 commented Jul 22, 2019
Yes. I did have installed g++.
vdweide commented Jul 22, 2019
What about mpicc and mpicxx? You are trying to build a parallel executable, so is MPI installed?
thw1021 commented Jul 22, 2019
I install OpenMPI following the instructions with commands:
and I can see the version
vdweide commented Jul 22, 2019
Are the compiler wrappers, mpicc and mpicxx, also installed? When I look in your log file it mentions
./configure: line 3362: /usr/bin/mpicxx: No such file or directory
talbring commented Jul 22, 2019
Below you can find the steps I used to build a singularity container using ubuntu 19.04. For pure docker and ubuntu 18.04 the steps should be the same I guess.
thw1021 commented Jul 22, 2019
Sorry. Do you mean that although I have installed OpenMPI, I still have to install mpicc and mpicxx ? I am not familiar with such problems.
When I run which mpicc and which mpicxx in the container, there is no outputs. But on the host machine, I can see /usr/bin/mpicc and /usr/bin/mpicxx . Maybe this the reason.
talbring commented Jul 22, 2019
And btw in case you want to really use MPI with containers, you should use singularity (https://sylabs.io/) as it is exactly designed for this.
thw1021 commented Jul 22, 2019 •
Yes. Thank you all. I installed libopenmpi-dev and openmpi-common. I don’t know which one is the key but I can see SU2_RUN and SU2_HOME environment variables displayed at the conclusion of configure.
thw1021 commented Jul 22, 2019
Thank you. I will close this issue after I make sure that I have installed successfully.
thw1021 commented Jul 22, 2019
@talbring
Could you give me more instructions about parallel computing in docker container, please ? I can commit the container to an image, so is there any difference ?
thw1021 commented Jul 22, 2019 •
Thank you all.
When I run the tutorial case with mpirun , there are some warnings:
Should I directly ignore such warnings ? Any suggestion would be grateful.
talbring commented Jul 22, 2019
OpenMPI is not officially supported when using a docker container. See my comment above and open-mpi/ompi#3625 (comment)
talbring commented Jul 22, 2019
Here is the full definition file for singularity:
Store it in file called su2.def and run
You can then run it like that:
The only thing to note is that the OpenMPI version you use inside the container and on the machine you want to run it should be similar. I tried it with OpenMPI v3 in the container and OpenMPI v4 outside and it worked.
Источник
Configure error c compiler cannot create executables python
Calculating dependencies. done!
[ebuild N ] dev-libs/elfutils-0.183 USE=»bzip2 nls utils -lzma -static-libs -test (-threads) -valgrind -zstd» ABI_X86=»(64) -32 (-x32)»
[ebuild N ] sys-devel/bc-1.07.1-r3 USE=»readline -libedit -static»
[ebuild N ] virtual/libelf-3 ABI_X86=»(64) -32 (-x32)»
[ebuild N ] sys-kernel/gentoo-sources-5.10.27 USE=»-build -experimental -symlink»
Would you like to merge these packages? [Yes/No] y
>>> Verifying ebuild manifests
>>> Emerging (1 of 4) dev-libs/elfutils-0.183::gentoo
* Fetching files in the background.
* To view fetch progress, run in another terminal:
* tail -f /var/log/emerge-fetch.log
* elfutils-0.183.tar.bz2 BLAKE2B SHA512 size 😉 . [ ok ]
>>> Unpacking source.
>>> Unpacking elfutils-0.183.tar.bz2 to /var/tmp/portage/dev-libs/elfutils-0.183/work
>>> Source unpacked in /var/tmp/portage/dev-libs/elfutils-0.183/work
>>> Preparing source in /var/tmp/portage/dev-libs/elfutils-0.183/work/elfutils-0.183 .
* Applying elfutils-0.175-disable-biarch-test-PR24158.patch . [ ok ]
* Applying elfutils-0.177-disable-large.patch . [ ok ]
* Applying elfutils-0.180-PaX-support.patch . [ ok ]
* Applying elfutils-0.183-CC-quote.patch . [ ok ]
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-libs/elfutils-0.183/work/elfutils-0.183 .
* abi_x86_64.amd64: running multilib-minimal_abi_src_configure
* econf: updating elfutils-0.183/config/config.sub with /usr/share/gnuconfig/config.sub
* econf: updating elfutils-0.183/config/config.guess with /usr/share/gnuconfig/config.guess
/var/tmp/portage/dev-libs/elfutils-0.183/work/elfutils-0.183/configure —prefix=/usr —build=x86_64-pc-linux-gnu —host=x86_64-pc-linux-gnu —mandir=/usr/share/man —infodir=/usr/share/info —datadir=/usr/share —sysconfdir=/etc —localstatedir=/var/lib —disable-dependency-tracking —disable-silent-rules —docdir=/usr/share/doc/elfutils-0.183 —htmldir=/usr/share/doc/elfutils-0.183/html —libdir=/usr/lib64 —enable-nls —disable-thread-safety —disable-valgrind —disable-debuginfod —disable-libdebuginfod —program-prefix=eu- —with-zlib —with-bzlib —without-lzma —without-zstd
checking for a BSD-compatible install. /usr/lib/portage/python3.8/ebuild-helpers/xattr/install -c
checking whether build environment is sane. yes
checking for a thread-safe mkdir -p. /bin/mkdir -p
checking for gawk. gawk
checking whether make sets $(MAKE). yes
checking whether make supports nested variables. yes
checking whether to enable maintainer-specific portions of Makefiles. no
checking whether make supports nested variables. (cached) yes
checking build system type. x86_64-pc-linux-gnu
checking host system type. x86_64-pc-linux-gnu
checking for x86_64-pc-linux-gnu-gcc. x86_64-pc-linux-gnu-gcc
checking whether the C compiler works. no
configure: error: in `/var/tmp/portage/dev-libs/elfutils-0.183/work/elfutils-0.183-abi_x86_64.amd64′:
configure: error: C compiler cannot create executables
See `config.log’ for more details
. Please attach the following file when seeking support:
. /var/tmp/portage/dev-libs/elfutils-0.183/work/elfutils-0.183-abi_x86_64.amd64/config.log
* ERROR: dev-libs/elfutils-0.183::gentoo failed (configure phase):
* econf failed
*
* Call stack:
* ebuild.sh, line 125: Called src_configure
* environment, line 2111: Called multilib-minimal_src_configure
* environment, line 1461: Called multilib_foreach_abi ‘multilib-minimal_abi_src_configure’
* environment, line 1714: Called multibuild_foreach_variant ‘_multilib_multibuild_wrapper’ ‘multilib-minimal_abi_src_configure’
* environment, line 1391: Called _multibuild_run ‘_multilib_multibuild_wrapper’ ‘multilib-minimal_abi_src_configure’
* environment, line 1389: Called _multilib_multibuild_wrapper ‘multilib-minimal_abi_src_configure’
* environment, line 411: Called multilib-minimal_abi_src_configure
* environment, line 1455: Called multilib_src_configure
* environment, line 1926: Called econf ‘—enable-nls’ ‘—disable-thread-safety’ ‘—disable-valgrind’ ‘—disable-debuginfod’ ‘—disable-libdebuginfod’ ‘—program-prefix=eu-‘ ‘—with-zlib’ ‘—with-bzlib’ ‘—without-lzma’ ‘—without-zstd’
* phase-helpers.sh, line 680: Called __helpers_die ‘econf failed’
* isolated-functions.sh, line 112: Called die
* The specific snippet of code:
* die «$@»
*
* If you need support, post the output of `emerge —info ‘=dev-libs/elfutils-0.183::gentoo’`,
* the complete build log and the output of `emerge -pqv ‘=dev-libs/elfutils-0.183::gentoo’`.
* The complete build log is located at ‘/var/tmp/portage/dev-libs/elfutils-0.183/temp/build.log’.
* The ebuild environment file is located at ‘/var/tmp/portage/dev-libs/elfutils-0.183/temp/environment’.
* Working directory: ‘/var/tmp/portage/dev-libs/elfutils-0.183/work/elfutils-0.183-abi_x86_64.amd64’
* S: ‘/var/tmp/portage/dev-libs/elfutils-0.183/work/elfutils-0.183’
>>> Failed to emerge dev-libs/elfutils-0.183, Log file:
* Messages for package dev-libs/elfutils-0.183:
* ERROR: dev-libs/elfutils-0.183::gentoo failed (configure phase):
* econf failed
*
* Call stack:
* ebuild.sh, line 125: Called src_configure
* environment, line 2111: Called multilib-minimal_src_configure
* environment, line 1461: Called multilib_foreach_abi ‘multilib-minimal_abi_src_configure’
* environment, line 1714: Called multibuild_foreach_variant ‘_multilib_multibuild_wrapper’ ‘multilib-minimal_abi_src_configure’
* environment, line 1391: Called _multibuild_run ‘_multilib_multibuild_wrapper’ ‘multilib-minimal_abi_src_configure’
* environment, line 1389: Called _multilib_multibuild_wrapper ‘multilib-minimal_abi_src_configure’
* environment, line 411: Called multilib-minimal_abi_src_configure
* environment, line 1455: Called multilib_src_configure
* environment, line 1926: Called econf ‘—enable-nls’ ‘—disable-thread-safety’ ‘—disable-valgrind’ ‘—disable-debuginfod’ ‘—disable-libdebuginfod’ ‘—program-prefix=eu-‘ ‘—with-zlib’ ‘—with-bzlib’ ‘—without-lzma’ ‘—without-zstd’
* phase-helpers.sh, line 680: Called __helpers_die ‘econf failed’
* isolated-functions.sh, line 112: Called die
* The specific snippet of code:
* die «$@»
*
* If you need support, post the output of `emerge —info ‘=dev-libs/elfutils-0.183::gentoo’`,
* the complete build log and the output of `emerge -pqv ‘=dev-libs/elfutils-0.183::gentoo’`.
* The complete build log is located at ‘/var/tmp/portage/dev-libs/elfutils-0.183/temp/build.log’.
* The ebuild environment file is located at ‘/var/tmp/portage/dev-libs/elfutils-0.183/temp/environment’.
* Working directory: ‘/var/tmp/portage/dev-libs/elfutils-0.183/work/elfutils-0.183-abi_x86_64.amd64’
* S:
* ‘/var/tmp/portage/dev-libs/elfutils-0.183/work/elfutils-0.183’
Then I ran this: «ls -l /usr/src/linux» and it produced this:
| Код: |
| ls: cannot access ‘/usr/src/linux’: No such file or directory |
Then I ran this: «dispatch-conf»
Then I ran this again: «ls -l /usr/src/linux» which produced the same result as the first few times, as seen here:
| Код: |
| ‘/usr/src/linux’: No such file or directory’/usr/src/linux’ |
I’m kind of stuck here, so any help or advise would be greatly appreciated, and rewarded with 1000 karma tokens(fully redeemable in the next life ).
[Moderator edit: changed [q uote] tags to [c ode] tags to preserve output layout. -Hu] Вернуться к началу
pietinger
Moderator
Зарегистрирован: 17 окт 2006
Сообщений: 2280
Откуда: Bavaria
| Добавлено: пн апр 26, 2021 11:54 pm Заголовок сообщения: | ||||
| Hello JHannon,
Welcome to Gentoo ! The most important information you got is:
This means you have probably a problem in your make.conf. The most often error was typing a wrong statement for:
(It is NOT zero-two; it is the alphabetic character «O») If this is not your problem, we need the output of your «emerge —info». |
Вернуться к началу
figueroa
Advocate
Зарегистрирован: 14 авг 2005
Сообщений: 2722
Откуда: Edge of the Marsh USA
| Добавлено: вт апр 27, 2021 3:14 am Заголовок сообщения: | ||
Once you DO get gentoo-sources installed, by default, YOU have to create the symbolic link (symlink) /usr/src/linux to point to the directory containing the new sources, i.e., as root, from within the the /usr/src directory, do:
Only then can you enter /usr/src/linux and configure, compile, and install a kernel. |
Вернуться к началу
Tony0945
Watchman
Зарегистрирован: 25 июл 2006
Сообщений: 5127
Откуда: Illinois, USA
| Добавлено: вт апр 27, 2021 6:52 am Заголовок сообщения: | ||||||||
Or use «eselect kernel» which sets the link. On a new insall I suppose the link won’t be there.
Best to do this as root instead of sudo. Solely because you probably want to procede with actually building the kernel. $ ls -l /usr/src/linux |
Вернуться к началу
NeddySeagoon
Administrator
Зарегистрирован: 05 июл 2003
Сообщений: 51807
Откуда: 56N 3W
| Добавлено: вт апр 27, 2021 9:32 am Заголовок сообщения: | ||
| JHannon,
Welcome to Gentoo
Notice the USE=-symlink. You did not ask for a symlink so you don’t have one. The symlink is only used by the system to build external kernel modules. It points to the kernel that the modules are to be built for. Unless you have external kernel modules, its not actually required. Computer users fall into two groups:- |
Вернуться к началу
pietinger
Moderator
Зарегистрирован: 17 окт 2006
Сообщений: 2280
Откуда: Bavaria
| Добавлено: вт апр 27, 2021 10:00 am Заголовок сообщения: | |
| @Neddy and @Tony: Please dont forget, he didnt installed the gentoo-sources right now, because of another problem. Linking the directory comes later (for this I recommend Tonys «eselect kernel list»). But before we have to find out why his emerge could not find the compiler. |
Вернуться к началу
NeddySeagoon
Administrator
Зарегистрирован: 05 июл 2003
Сообщений: 51807
Откуда: 56N 3W
| Добавлено: вт апр 27, 2021 10:14 am Заголовок сообщения: | |
| pietinger,
Agreed. The symlink would not be there anyway. Computer users fall into two groups:- |
Вернуться к началу
Hu
Moderator
Зарегистрирован: 06 мар 2007
Сообщений: 19658
| Добавлено: вт апр 27, 2021 5:55 pm Заголовок сообщения: Re: C compiler cannot create executables | ||
Always read in full the output you post here, looking for advice printed by the system itself. In this case, it told you certain things to post, and you did not provide them. As a result, the first responses to your thread were people asking you to provide that information. If you had posted that information initially, the first response to your post could have been a solution to your problem. |
Вернуться к началу
JHannon
n00b
Зарегистрирован: 25 апр 2021
Сообщений: 2
| Добавлено: ср апр 28, 2021 11:56 pm Заголовок сообщения: | ||||
@pietinger, At first I it reported back, that no such file or directory exists. I was working from a terminal that is chrooted, within the mounted partition. I opened another that wasn’t, then navigated to the file here: /mnt/gentoo/etc/portage/make.conf within the live ubuntu spin. I’m not sure if not being able to see or access it from where I’m chrooted has anything to do with my issue. This what it showed:
@Neddy and @Tony, If I’m trying to establish a symbolic link, should I do it under chroot, or does it not matter? Or is it as what I believe Pietinger is saying, as in I’m not at that step yet? @Hu, You’ll have to excuse my ignorance, but is this what I should be posting?
Thanks to all of you, and the use of your time. Please excuse my slow response, along with my ignorance. If you think I’m missing something about the theory of what I’m trying to do, let me know. [Moderator edit: changed [q uote] tags to [c ode] tags to preserve output layout. -Hu] |
Вернуться к началу
Buffoon
Veteran
Зарегистрирован: 17 июн 2015
Сообщений: 1369
Откуда: EU or US
| Добавлено: чт апр 29, 2021 12:20 am Заголовок сообщения: | |
| Correct is ‘-march=native’, you have ‘march=native’. Fix it and try emerging gentoo-sources again. _________________ Life is a tragedy for those who feel and a comedy for those who think. |
Вернуться к началу
Hu
Moderator
Зарегистрирован: 06 мар 2007
Сообщений: 19658
| Добавлено: чт апр 29, 2021 1:15 am Заголовок сообщения: | ||||
A symlink can be created from within or without, since the link can point to a target that does not exist yet, but will exist by the time it is needed. Either way, take care to point the symlink to the correct target. A dangling symlink is (usually) not useful for anything.
It is one of the things, yes. The output also referred you to config.log , which you have not shared. (You will usually need a pastebin for that type of log, due to the sheer size.) Fortunately, the output you shared in the post I am quoting was sufficient to spot a problem. As Buffoon says, your CFLAGS are incorrect, so any attempt to invoke a C compiler will fail. His advice looks correct to me. Please try it and report back. |
Вернуться к началу
Вы не можете начинать темы
Вы не можете отвечать на сообщения
Вы не можете редактировать свои сообщения
Вы не можете удалять свои сообщения
Вы не можете голосовать в опросах
Copyright 2001-2023 Gentoo Foundation, Inc. Designed by Kyle Manna © 2003; Style derived from original subSilver theme. | Hosting by Gossamer Threads Inc. © | Powered by phpBB 2.0.23-gentoo-p11 © 2001, 2002 phpBB Group
Privacy Policy
Источник
Adblock
detector
- Печать
Страницы: [1] Вниз
Тема: Ошибка при выполнении ./configure (Прочитано 4795 раз)
0 Пользователей и 1 Гость просматривают эту тему.
Shlepov
При выполнении ./configure выходит ошибка «configure: error: C compiler cannot create executables». Переустановил libc6-dev и все его зависимости. Система 14.04
Вылоп ./configure
config.log
Что еще можно попробовать?
ТС не появлялся на Форуме более полугода по состоянию на 09/09/2019 (последняя явка: 11/02/2019). Модератором раздела принято решение закрыть тему.
—zg_nico
« Последнее редактирование: 09 Сентября 2019, 18:26:04 от zg_nico »
hesoyamatogun
А о чем это вы сейчас, точнее что это за программа, что делает, что конфигурирует, с какой целью вы её запускаете и что xотите получить?
Shlepov
hesoyamatogun
Может ты не заметил, у тебя error’ы не только в конце но и в середине парочка, которые объясняют причину а не только извещают что «error: C compiler cannot create executables»
victor00000
gcc: error: unrecognized command line option ‘-fstack-protector-strong’
что опять версии пропустили gcc пакеты в ubuntu?
a@a:~$
a@a:~$ cat 3.c
#include <stdio.h>
int main()
{
char *str; // [] = "hello";
printf ((const char*)str);
}
a@a:~$
a@a:~$
a@a:~$
a@a:~$ LANG=C gcc-4.9 -fstack-protector-strong -c 3.c || echo "Ошибка"
a@a:~$
a@a:~$ LANG=C gcc-4.8 -fstack-protector-strong -c 3.c || echo "Ошибка"
gcc-4.8: error: unrecognized command line option '-fstack-protector-strong'
Ошибка
a@a:~$
в шоке. 
Shlepov
Нет, не заметил. Спасибо!
Насколько я понял требуется версия gcc >5?
configure:5032: gcc -V >&5
gcc: error: unrecognized command line option '-V'
gcc: fatal error: no input files
Я обновил gcc до 5.4.1 20160904, и этот момент прошел успешно.
Теперь борюсь со следующей ошибкой:
configure: error: Basic auth helper getpwnam ... found but cannot be built
victor00000
gcc --version
Пользователь добавил сообщение 20 Июля 2017, 17:49:59:
Я обновил gcc до 5.4.1 20160904, и этот момент прошел успешно.
не а, плохо Ubuntu от сборки для пакеты gcc.
Пользователь добавил сообщение 21 Июля 2017, 02:51:08:
14.04
sudo apt-get install gccgo-4.9 g++-4.8
sudo rm -f /usr/local/bin/{gcc,g++}
sudo ln -s /usr/bin/gcc-4.9 /usr/local/bin/gcc
sudo ln -s /usr/bin/g++-4.8 /usr/local/bin/g++
exit
16.04
sudo apt-get install gccgo-6 g++-5
sudo rm -f /usr/local/bin/{gcc,g++}
sudo ln -s /usr/bin/gcc-6 /usr/local/bin/gcc
sudo ln -s /usr/bin/g++-5 /usr/local/bin/g++
exit
« Последнее редактирование: 21 Июля 2017, 02:51:08 от victor00000 »
Shlepov
shlepov@it:~$ gcc --version
gcc (Ubuntu 5.4.1-2ubuntu1~14.04) 5.4.1 20160904
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
обновлял по этой инструкции.
Не пойму что за ошибка вылетает:
getpwnam это вроде обращение к файлу с паролями. На кой вообще свиду пароли? Я что-то запутался.
« Последнее редактирование: 21 Июля 2017, 09:06:19 от Shlepov »
victor00000
смотри мою посту «16.04» и команды.
- Печать
Страницы: [1] Вверх