build

How to make a “light” build of GCC with language supports etc. pruned?

断了今生、忘了曾经 提交于 2021-01-20 17:13:00
问题 Basically I would like to make a light build of GCC with only C/C++ support. Can this be done easily or does it require manual tinkering with source? 回答1: This is covered in Installing GCC and Configuration --enable-languages=lang1,lang2,... Specify that only a particular subset of compilers and their runtime libraries should be built. For a list of valid values for langN you can issue the following command in the gcc directory of your GCC source tree: grep language= */config-lang.in

Can't compile Artifactory 7.10.2

Deadly 提交于 2021-01-03 07:26:25
问题 After JFrog released the source code for Artifactory 7.10.2, I tried to build it, without success. The project seems to be a maven one (there is a pom.xml in the root project, so I guess so). From the root of the project I gave the usual mvn package , but this resulted in an error: $ mvn package [INFO] Scanning for projects... [ERROR] [ERROR] Some problems were encountered while processing the POMs: [FATAL] Non-resolvable parent POM for org.artifactory:artifactory-parent:7.10.2: Failure to

Swift linking error: type metadata accessor for Module.Class

断了今生、忘了曾经 提交于 2021-01-02 06:30:09
问题 While working in Swift project, I have two modules, let's say Base Feature Base has a SHService class from where I am calling a function of Feature module (of class SHCommon ). Feature module is building without error but Base raises error in linking phase. Snapshot of workspace: Base.SHService import Foundation import Feature class SHService { public func printMe(printString: String){ SHCommon().printMe(printString: printString) } } Feature.SHCommon import Foundation public class SHCommon {

gradle: disable creation of the build folder at root in multi-projects application

我是研究僧i 提交于 2021-01-02 05:40:46
问题 My gradle project is a multi-project structure. It consists of two subprojects. My build.gradle in root project as following: allprojects { apply plugin: 'eclipse' } subprojects { apply plugin: 'java' apply plugin: 'maven-publish' publishing { repositories { maven { name 'myMaven' def suffix = project.version.endsWith("SNAPSHOT") ? "snapshots" : "releases" url baseUrl + suffix } } publications { core(MavenPublication) { artifactId project.name artifact jar } } } } project(':projectA') { ext {

What does the clang compiler's `-Weverything` option include and where is it documented?

╄→尐↘猪︶ㄣ 提交于 2021-01-01 09:59:48
问题 clang, but NOT gcc, has a -Weverything option which appears to include things such as -Wpedantic . You can test it here: https://godbolt.org/z/qcYKd1. See the top-right of the window for where I have typed in -Weverything as an explicit compiler option. Notice the -Wvla-extension warning we get since we are relying on a C99 extension in C++ in this case, and we have -Weverything set. We get the same warning if we just use -Wpedantic , as shown here: https://godbolt.org/z/M9ahE4, indicating

What does the clang compiler's `-Weverything` option include and where is it documented?

浪尽此生 提交于 2021-01-01 09:59:27
问题 clang, but NOT gcc, has a -Weverything option which appears to include things such as -Wpedantic . You can test it here: https://godbolt.org/z/qcYKd1. See the top-right of the window for where I have typed in -Weverything as an explicit compiler option. Notice the -Wvla-extension warning we get since we are relying on a C99 extension in C++ in this case, and we have -Weverything set. We get the same warning if we just use -Wpedantic , as shown here: https://godbolt.org/z/M9ahE4, indicating

pkg_config_path error on building with docker

人走茶凉 提交于 2021-01-01 07:50:31
问题 When I am building an image for my Go application through docker, I am getting the following error: # pkg-config --cflags oci8 Package oci8 was not found in the pkg-config search path. Perhaps you should add the directory containing `oci8.pc' to the PKG_CONFIG_PATH environment variable No package 'oci8' found pkg-config: exit status 1 I have set the environment variable in my Dockerfile also. But still the issue persists. My Dockerfile is: *FROM golang:1.9 ARG app_env ENV APP_ENV $app_env ENV

pkg_config_path error on building with docker

﹥>﹥吖頭↗ 提交于 2021-01-01 07:50:25
问题 When I am building an image for my Go application through docker, I am getting the following error: # pkg-config --cflags oci8 Package oci8 was not found in the pkg-config search path. Perhaps you should add the directory containing `oci8.pc' to the PKG_CONFIG_PATH environment variable No package 'oci8' found pkg-config: exit status 1 I have set the environment variable in my Dockerfile also. But still the issue persists. My Dockerfile is: *FROM golang:1.9 ARG app_env ENV APP_ENV $app_env ENV

Go 1.5+ : Error - imports runtime: C source files not allowed when not using cgo or SWIG

前提是你 提交于 2020-12-29 02:47:07
问题 My program was building perfectly with go 1.4.2. After installing go 1.5, I am getting following error. imports runtime: C source files not allowed when not using cgo or SWIG: atomic_amd64x.c defs.c float.c heapdump.c lfstack.c malloc.c mcache.c mcentral.c mem_linux.c mfixalloc.c mgc0.c mheap.c msize.c os_linux.c panic.c parfor.c proc.c runtime.c signal.c signal_amd64x.c signal_unix.c stack.c string.c sys_x86.c vdso_linux_amd64.c The error is not program dependent. Even a "Hello world"

Go 1.5+ : Error - imports runtime: C source files not allowed when not using cgo or SWIG

若如初见. 提交于 2020-12-29 02:47:06
问题 My program was building perfectly with go 1.4.2. After installing go 1.5, I am getting following error. imports runtime: C source files not allowed when not using cgo or SWIG: atomic_amd64x.c defs.c float.c heapdump.c lfstack.c malloc.c mcache.c mcentral.c mem_linux.c mfixalloc.c mgc0.c mheap.c msize.c os_linux.c panic.c parfor.c proc.c runtime.c signal.c signal_amd64x.c signal_unix.c stack.c string.c sys_x86.c vdso_linux_amd64.c The error is not program dependent. Even a "Hello world"