Сравнение постов
Различия между постами
#264627 (30.08.2022 22:08)
и
#275260 (05.06.2024 18:32).
1 | [32m * [39;49;00mPackage: net-wireless/gr-gsm-20210505-r1 | |
2 | [32m * [39;49;00mRepository: wanderer | |
3 | [32m * [39;49;00mUSE: abi_x86_64 amd64 elibc_glibc kernel_linux python_single_target_python3_10 userland_GNU | |
4 | [32m * [39;49;00mFEATURES: network-sandbox preserve-libs sandbox usersandbox | |
5 | [32m*[0m Using python3.10 to build | |
6 | >>> Unpacking source... | |
7 | >>> Unpacking gr-gsm-20210505.tar.gz to /var/calculate/tmp/portage/net-wireless/gr-gsm-20210505-r1/work | |
8 | >>> Source unpacked in /var/calculate/tmp/portage/net-wireless/gr-gsm-20210505-r1/work | |
9 | >>> Preparing source in /var/calculate/tmp/portage/net-wireless/gr-gsm-20210505-r1/work/gr-gsm-2de47e28ce1fb9a518337bfc0add36c8e3cff5eb ... | |
10 | [32m*[0m Source directory (CMAKE_USE_DIR): "/var/calculate/tmp/portage/net-wireless/gr-gsm-20210505-r1/work/gr-gsm-2de47e28ce1fb9a518337bfc0add36c8e3cff5eb" | |
11 | [32m*[0m Build directory (BUILD_DIR): "/var/calculate/tmp/portage/net-wireless/gr-gsm-20210505-r1/work/gr-gsm-2de47e28ce1fb9a518337bfc0add36c8e3cff5eb_build" | |
12 | [32m*[0m Hardcoded definition(s) removed in CMakeLists.txt: | |
13 | [32m*[0m set(CMAKE_INSTALL_PREFIX $ENV{PYBOMBS_PREFIX}) | |
14 | [32m*[0m set(CMAKE_BUILD_TYPE "Release") | |
15 | [32m*[0m set(CMAKE_BUILD_TYPE ${CMAKE_BUILD_TYPE} CACHE STRING "") | |
16 | >>> Source prepared. | |
17 | >>> Configuring source in /var/calculate/tmp/portage/net-wireless/gr-gsm-20210505-r1/work/gr-gsm-2de47e28ce1fb9a518337bfc0add36c8e3cff5eb ... | |
18 | [32m*[0m Source directory (CMAKE_USE_DIR): "/var/calculate/tmp/portage/net-wireless/gr-gsm-20210505-r1/work/gr-gsm-2de47e28ce1fb9a518337bfc0add36c8e3cff5eb" | |
19 | [32m*[0m Build directory (BUILD_DIR): "/var/calculate/tmp/portage/net-wireless/gr-gsm-20210505-r1/work/gr-gsm-2de47e28ce1fb9a518337bfc0add36c8e3cff5eb_build" | |
20 | cmake -C /var/calculate/tmp/portage/net-wireless/gr-gsm-20210505-r1/work/gr-gsm-2de47e28ce1fb9a518337bfc0add36c8e3cff5eb_build/gentoo_common_config.cmake -G Ninja -DCMAKE_INSTALL_PREFIX=/usr -DENABLE_DOXYGEN=no -DPYTHON_EXECUTABLE=/usr/bin/python3.10 -DLOCAL_OSMOCOM=ON -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_TOOLCHAIN_FILE=/var/calculate/tmp/portage/net-wireless/gr-gsm-20210505-r1/work/gr-gsm-2de47e28ce1fb9a518337bfc0add36c8e3cff5eb_build/gentoo_toolchain.cmake /var/calculate/tmp/portage/net-wireless/gr-gsm-20210505-r1/work/gr-gsm-2de47e28ce1fb9a518337bfc0add36c8e3cff5eb | |
21 | loading initial cache file /var/calculate/tmp/portage/net-wireless/gr-gsm-20210505-r1/work/gr-gsm-2de47e28ce1fb9a518337bfc0add36c8e3cff5eb_build/gentoo_common_config.cmake | |
22 | -- The CXX compiler identification is GNU 11.3.0 | |
23 | -- The C compiler identification is GNU 11.3.0 | |
24 | -- Detecting CXX compiler ABI info | |
25 | -- Detecting CXX compiler ABI info - done | |
1 | За последние 25 лет были разработаны и внедрены в производство современные решения в области разработки и эксплуатации автоматики https://mosvrata.ru/remont/ | |
2 | Производитель делает упор на качество и современные решения в отрасли https://mosvrata.ru/tovar/nice-shel-75-kce-privod-dlya-garazhnyh-vorot/ | |
3 | Именно поэтому автоматика BFT занимает сегодня лидирующие позиции на рынке решений для ворот https://mosvrata.ru/tovar/alutech-kronshtejn-verhnij/ | |
4 | Она способна работать даже в самых экстремальных условиях https://mosvrata.ru/catalog/aksessuary/page/18/ | |
5 | Приводы рассчитаны на высокую интенсивность использования, что делает возможным устанавливать их на крупных логистических и промышленных предприятиях https://mosvrata.ru/catalog/page/35/ | |
6 | При этом вся продукция соответствует Европейским стандартам качества https://mosvrata.ru/tovar/nice-ankernaya-plastina-s-krepezhom-dlya-signo6-sia2/ | |
7 | ||
8 | https://mosvrata.ru/tovar/faac-maslo-gidravlicheskoe-hp-2-oil-1-l/ | |
9 | Оборудование для данного типа автоматических ворот гарантирует перемещение дверей по направляющим https://mosvrata.ru/tovar/came-k-led-lampa-signalnaya/ | |
10 | Система включает в себя электропривод для ворот, компоненты доступа и встроенные приборы управлени | |
11 | Под установку автоматических откатных ворот следует отвести специальное место, где нужно будет подготовить фундаментное основание https://mosvrata.ru/tovar/nordmotors-nbr-3000-shlagbaum-avtomaticheskij/ | |
12 | Винтовые сваи смогут обеспечить высокий уровень защиты от взлома https://mosvrata.ru/tovar/shlagbaum-avtomaticheskij-nordmotors-nbr-4000/ | |
13 | ||
14 | Распашной тип конструкции пользуется особой популярностью среди потребителей https://mosvrata.ru/tovar/blochnyj-fundament-dlya-shlagbaumov-nordmotors/ | |
15 | Такие характеризуются удобной системой монтажа, они остаются надежными на протяжении всего сроки эксплуатации https://mosvrata.ru/tovar/came-g0402-strela-4-metra-kruglaya/ | |
16 | Доступная стоимость – еще один плюс в пользу того, чтобы остановить свой выбор именно на этих конструкциях https://mosvrata.ru/tovar/faac-opora-dlya-strely/ | |
17 | ||
18 | В первую очередь, до начала работ нужно определиться, какой вид ворот наиболее предпочтителен https://mosvrata.ru/tovar/doorhan-uplotnitel-bokovoj-dlya-sektsionnyh/ | |
19 | Роллетные используются крайне редко, разве что в местностях с теплым климатом или на охраняемых участках https://mosvrata.ru/catalog/komplektuyushhie-dlya-vorot/page/6/ | |
20 | Это объясняется тем, что подобные ворота не обеспечат надежной защиты https://mosvrata.ru/tovar/doorhan-uplotnitel-bokovoj-dlya-sektsionnyh/ | |
21 | ||
22 | Это важно! Мощность автоматического привода пропорциональна расстоянию между петлей и внутренним краем ворот https://mosvrata.ru/tovar/came-rezinovye-nakladki-na-strelu-6-m/ | |
23 | Если это 150 миллиметров, можно использовать линейный привод https://mosvrata.ru/catalog/komplektuyushhie-dlya-vorot/otkatnih/page/2/ | |
24 | От 150 – рычажной https://mosvrata.ru/tovar/privod-dlya-otkatnyh-vorot-comunello-ft424/ | |
25 | ||
26 | -- Check for working CXX compiler: /usr/bin/x86_64-pc-linux-gnu-g++ - skipped | |
27 | -- Detecting CXX compile features | |
28 | -- Detecting CXX compile features - done | |
29 | -- Detecting C compiler ABI info | |
30 | -- Detecting C compiler ABI info - done | |
31 | -- Check for working C compiler: /usr/bin/x86_64-pc-linux-gnu-gcc - skipped | |
32 | -- Detecting C compile features | |
33 | -- Detecting C compile features - done | |
34 | -- Looking for pthread.h | |
35 | -- Looking for pthread.h - found | |
36 | -- Performing Test CMAKE_HAVE_LIBC_PTHREAD | |
37 | -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success | |
38 | -- Found Threads: TRUE | |
39 | -- Found PkgConfig: /usr/bin/x86_64-pc-linux-gnu-pkg-config (found version "1.8.0") | |
40 | -- Checking for module 'gmp' | |
41 | -- Found gmp, version 6.2.1 | |
42 | -- Found GMP: /usr/lib64/libgmpxx.so | |
43 | -- Using GMP. | |
44 | -- Found MPLIB: /usr/lib64/libgmpxx.so | |
45 | -- Found Boost: /usr/lib64/cmake/Boost-1.79.0/BoostConfig.cmake (found suitable version "1.79.0", minimum required is "1.79.0") found components: date_time program_options system regex thread | |
46 | -- Found Volk: Volk::volk | |
47 | -- User set python executable /usr/bin/python3.10 | |
48 | -- Found PythonInterp: /usr/bin/python3.10 (found version "3.10.6") | |
49 | -- Found PythonLibs: /usr/lib64/libpython3.10.so (found suitable exact version "3.10.6") | |
50 | -- Checking for module 'sndfile' | |
51 | -- Found sndfile, version 1.1.0 | |
52 | -- Found SNDFILE: /usr/lib64/libsndfile.so | |
53 | -- Checking for module 'fftw3f >= 3.0' | |
54 | -- Found fftw3f , version 3.3.10 | |
55 | -- Found FFTW3f: /usr/lib64/libfftw3f.so | |
56 | -- Found Git: /usr/bin/git | |
57 | -- Found Doxygen: /usr/bin/doxygen (found version "1.9.4") found components: doxygen missing components: dot | |
58 | [33mCMake Warning (dev) at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:438 (message): | |
59 | The package name passed to `find_package_handle_standard_args` (PkgConfig) | |
60 | does not match the name of the calling package (Libosmocore). This can | |
61 | lead to problems in calling code that expects `find_package` result | |
62 | variables (e.g., `_FOUND`) to follow a certain pattern. | |
63 | Call Stack (most recent call first): | |
64 | /usr/share/cmake/Modules/FindPkgConfig.cmake:99 (find_package_handle_standard_args) | |
65 | cmake/Modules/FindLibosmocore.cmake:2 (INCLUDE) | |
66 | CMakeLists.txt:132 (find_package) | |
67 | This warning is for project developers. Use -Wno-dev to suppress it. | |
68 | [0m | |
69 | -- Checking for module 'libosmocore' | |
70 | -- Found libosmocore, version 1.6.0 | |
71 | [33mCMake Warning (dev) at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:438 (message): | |
72 | The package name passed to `find_package_handle_standard_args` | |
73 | (libosmocore) does not match the name of the calling package (Libosmocore). | |
74 | This can lead to problems in calling code that expects `find_package` | |
75 | result variables (e.g., `_FOUND`) to follow a certain pattern. | |
76 | Call Stack (most recent call first): | |
77 | cmake/Modules/FindLibosmocore.cmake:32 (find_package_handle_standard_args) | |
78 | CMakeLists.txt:132 (find_package) | |
79 | This warning is for project developers. Use -Wno-dev to suppress it. | |
80 | [0m | |
81 | -- Found libosmocore: /usr/lib64/libosmocore.so | |
82 | [33mCMake Warning (dev) at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:438 (message): | |
83 | The package name passed to `find_package_handle_standard_args` (PkgConfig) | |
84 | does not match the name of the calling package (Libosmocodec). This can | |
85 | lead to problems in calling code that expects `find_package` result | |
86 | variables (e.g., `_FOUND`) to follow a certain pattern. | |
87 | Call Stack (most recent call first): | |
88 | /usr/share/cmake/Modules/FindPkgConfig.cmake:99 (find_package_handle_standard_args) | |
89 | cmake/Modules/FindLibosmocodec.cmake:1 (INCLUDE) | |
90 | CMakeLists.txt:133 (find_package) | |
91 | This warning is for project developers. Use -Wno-dev to suppress it. | |
92 | [0m | |
93 | -- Checking for module 'libosmocodec' | |
94 | -- Found libosmocodec, version 1.6.0 | |
95 | [33mCMake Warning (dev) at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:438 (message): | |
96 | The package name passed to `find_package_handle_standard_args` | |
97 | (libosmocodec) does not match the name of the calling package | |
98 | (Libosmocodec). This can lead to problems in calling code that expects | |
99 | `find_package` result variables (e.g., `_FOUND`) to follow a certain | |
100 | pattern. | |
101 | Call Stack (most recent call first): | |
102 | cmake/Modules/FindLibosmocodec.cmake:31 (find_package_handle_standard_args) | |
103 | CMakeLists.txt:133 (find_package) | |
104 | This warning is for project developers. Use -Wno-dev to suppress it. | |
105 | [0m | |
106 | -- Found libosmocodec: /usr/lib64/libosmocodec.so | |
107 | -- Checking for module 'libosmocoding' | |
108 | -- Found libosmocoding, version 1.6.0 | |
109 | [33mCMake Warning (dev) at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:438 (message): | |
110 | The package name passed to `find_package_handle_standard_args` | |
111 | (libosmocoding) does not match the name of the calling package | |
112 | (Libosmocoding). This can lead to problems in calling code that expects | |
113 | `find_package` result variables (e.g., `_FOUND`) to follow a certain | |
114 | pattern. | |
115 | Call Stack (most recent call first): | |
116 | cmake/Modules/FindLibosmocoding.cmake:31 (find_package_handle_standard_args) | |
117 | CMakeLists.txt:134 (find_package) | |
118 | This warning is for project developers. Use -Wno-dev to suppress it. | |
119 | [0m | |
120 | -- Found libosmocoding: /usr/lib64/libosmocoding.so | |
121 | [33mCMake Warning (dev) at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:438 (message): | |
122 | The package name passed to `find_package_handle_standard_args` (PkgConfig) | |
123 | does not match the name of the calling package (Libosmogsm). This can lead | |
124 | to problems in calling code that expects `find_package` result variables | |
125 | (e.g., `_FOUND`) to follow a certain pattern. | |
126 | Call Stack (most recent call first): | |
127 | /usr/share/cmake/Modules/FindPkgConfig.cmake:99 (find_package_handle_standard_args) | |
128 | cmake/Modules/FindLibosmogsm.cmake:1 (INCLUDE) | |
129 | CMakeLists.txt:135 (find_package) | |
130 | This warning is for project developers. Use -Wno-dev to suppress it. | |
131 | [0m | |
132 | -- Checking for module 'libosmogsm' | |
133 | -- Found libosmogsm, version 1.6.0 | |
134 | [33mCMake Warning (dev) at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:438 (message): | |
135 | The package name passed to `find_package_handle_standard_args` (libosmogsm) | |
136 | does not match the name of the calling package (Libosmogsm). This can lead | |
137 | to problems in calling code that expects `find_package` result variables | |
138 | (e.g., `_FOUND`) to follow a certain pattern. | |
139 | Call Stack (most recent call first): | |
140 | cmake/Modules/FindLibosmogsm.cmake:31 (find_package_handle_standard_args) | |
141 | CMakeLists.txt:135 (find_package) | |
142 | This warning is for project developers. Use -Wno-dev to suppress it. | |
143 | [0m | |
144 | -- Found libosmogsm: /usr/lib64/libosmogsm.so | |
145 | -- Loading build date Mon, 29 Aug 2022 19:56:36 into constants... | |
146 | -- Loading version v1.0-compat-xxx-xunknown into constants... | |
147 | -- Using install prefix: /usr | |
148 | -- Building for version: v1.0-compat-xxx-xunknown / 1.0.0git | |
149 | -- No C++ unit tests... skipping | |
150 | -- Found SWIG: /usr/bin/swig (found version "4.0.2") | |
151 | -- Found PythonLibs: /usr/lib64/libpython3.10.so (found version "3.10.6") | |
152 | [31mCMake Error at swig/CMakeLists.txt:37 (include): | |
153 | include could not find requested file: | |
154 | ||
155 | GrSwig | |
156 | ||
157 | [0m | |
158 | [31mCMake Error at swig/CMakeLists.txt:51 (GR_SWIG_MAKE): | |
159 | Unknown CMake command "GR_SWIG_MAKE". | |
160 | ||
161 | [0m | |
162 | -- Configuring incomplete, errors occurred! | |
163 | See also "/var/calculate/tmp/portage/net-wireless/gr-gsm-20210505-r1/work/gr-gsm-2de47e28ce1fb9a518337bfc0add36c8e3cff5eb_build/CMakeFiles/CMakeOutput.log". | |
164 | [31;01m*[0m ERROR: net-wireless/gr-gsm-20210505-r1::wanderer failed (configure phase): | |
165 | [31;01m*[0m cmake failed | |
166 | [31;01m*[0m | |
167 | [31;01m*[0m Call stack: | |
168 | [31;01m*[0m ebuild.sh, line 127: Called src_configure | |
169 | [31;01m*[0m environment, line 3281: Called cmake_src_configure | |
170 | [31;01m*[0m environment, line 1600: Called die | |
171 | [31;01m*[0m The specific snippet of code: | |
172 | [31;01m*[0m "${CMAKE_BINARY}" "${cmakeargs[@]}" "${CMAKE_USE_DIR}" || die "cmake failed"; | |
173 | [31;01m*[0m | |
174 | [31;01m*[0m If you need support, post the output of `emerge --info '=net-wireless/gr-gsm-20210505-r1::wanderer'`, | |
175 | [31;01m*[0m the complete build log and the output of `emerge -pqv '=net-wireless/gr-gsm-20210505-r1::wanderer'`. | |
176 | [31;01m*[0m The complete build log is located at '/var/calculate/tmp/portage/net-wireless/gr-gsm-20210505-r1/temp/build.log'. | |
177 | [31;01m*[0m The ebuild environment file is located at '/var/calculate/tmp/portage/net-wireless/gr-gsm-20210505-r1/temp/environment'. | |
178 | [31;01m*[0m Working directory: '/var/calculate/tmp/portage/net-wireless/gr-gsm-20210505-r1/work/gr-gsm-2de47e28ce1fb9a518337bfc0add36c8e3cff5eb_build' |