Mixing
Warning: jobserver unavailable: using -j1. Add '+' to parent make rule
0
Good evening.
I'm getting warning when run cmake.
I searched solution but found only like "replace "make" to "$(MAKE)"".
BUT!
I can't find this string.
Even grep doesn't save me.
Forgive me if this is a stupid question. I really can't find solution.
This is part of cmake code (it's not my (opensource)):
if (${CMAKE_SYSTEM_NAME} MATCHES "Linux" OR MINGW)
if (NOT CMAKE_BUILD_TYPE)
set(CMAKE_BUILD_TYPE "Release")
endif()
add_definitions(-D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE)
set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -pipe -Wall -Wno-unused-function -fvisibility=hidden -Winvalid-pch")
set(CMAKE_C_FLAGS_DEBUG "${CMAKE_C_FLAGS_DEBUG} -O0 -D_DEBUG")
set(CMAKE_C_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE} -fno-strict-aliasing -ffast-math -funroll-loops -msse2 -O2")
if (${CMAKE_SYSTEM_NAME} MATCHES "Linux")
set(CMAKE_CXX_FLAGS "${CMAKE_C_FLAGS} -std=c++11")
else()
set(CMAKE_CXX_FLAGS "${CMAKE_C_FLAGS} -std=c++11")
endif()
set(CMAKE_CXX_FLAGS_DEBUG "${CMAKE_C_FLAGS_DEBUG}")
set(CMAKE_CXX_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE}")
set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -std=gnu99 -D_POSIX_C_SOURCE=200112L -D_XOPEN_SOURCE=500")
add_common_link_flags("-Wl,--as-needed")
add_release_link_flags("-s")
if (MINGW)
add_definitions(-D_WIN32_WINNT=_WIN32_WINNT_VISTA)
set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wno-unknown-pragmas")
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wno-unknown-pragmas")
add_common_link_flags("-static -static-libgcc -static-libstdc++")
endif()
endif()
cmake
asked Nov 20 '18 at 16:04
Maxim TemnyMaxim Temny
85
add a comment |
0
Good evening.
I'm getting warning when run cmake.
I searched solution but found only like "replace "make" to "$(MAKE)"".
BUT!
I can't find this string.
Even grep doesn't save me.
Forgive me if this is a stupid question. I really can't find solution.
This is part of cmake code (it's not my (opensource)):
if (${CMAKE_SYSTEM_NAME} MATCHES "Linux" OR MINGW)
if (NOT CMAKE_BUILD_TYPE)
set(CMAKE_BUILD_TYPE "Release")
endif()
add_definitions(-D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE)
set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -pipe -Wall -Wno-unused-function -fvisibility=hidden -Winvalid-pch")
set(CMAKE_C_FLAGS_DEBUG "${CMAKE_C_FLAGS_DEBUG} -O0 -D_DEBUG")
set(CMAKE_C_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE} -fno-strict-aliasing -ffast-math -funroll-loops -msse2 -O2")
if (${CMAKE_SYSTEM_NAME} MATCHES "Linux")
set(CMAKE_CXX_FLAGS "${CMAKE_C_FLAGS} -std=c++11")
else()
set(CMAKE_CXX_FLAGS "${CMAKE_C_FLAGS} -std=c++11")
endif()
set(CMAKE_CXX_FLAGS_DEBUG "${CMAKE_C_FLAGS_DEBUG}")
set(CMAKE_CXX_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE}")
set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -std=gnu99 -D_POSIX_C_SOURCE=200112L -D_XOPEN_SOURCE=500")
add_common_link_flags("-Wl,--as-needed")
add_release_link_flags("-s")
if (MINGW)
add_definitions(-D_WIN32_WINNT=_WIN32_WINNT_VISTA)
set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wno-unknown-pragmas")
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wno-unknown-pragmas")
add_common_link_flags("-static -static-libgcc -static-libstdc++")
endif()
endif()
cmake
asked Nov 20 '18 at 16:04
Maxim TemnyMaxim Temny
85
The part of the code you provide doesn't emit any build rule, thus it is unrelated to the warning. As the project is not yours, you are better to ignore this warning - it doesn't affect on build correctness. If you want to fix it, you need to have better understanding of the code. Probably, the warning is caused byExternalProject_Addcommand invocation, like described in that question: stackoverflow.com/questions/33171335/….
– Tsyvarev
Nov 20 '18 at 21:19
Thanks for you answer, but no. I saw it and "was grep" all project. There is nothing there.
– Maxim Temny
Nov 20 '18 at 23:48
Well, I know the only reason of this warning: your project has a command which invokesmake. It could beCMakeLists.txtwhich contains such command, or it could be some other file which is included intoCMakeLists.txt. Without viewing the appropriate part of the code, we couldn't point to the string causing the warning. In that case we can only guess, but it is not how Stack Overflow works. We want Minimal, Complete, and Verifiable example which reproduces the problem. If you cannot reproduce the problem in, say, 100 lines of code (but NOT a whole project), you may report the problem to developers.
– Tsyvarev
Nov 21 '18 at 8:45
add a comment |
0
0
0
Good evening.
I'm getting warning when run cmake.
I searched solution but found only like "replace "make" to "$(MAKE)"".
BUT!
I can't find this string.
Even grep doesn't save me.
Forgive me if this is a stupid question. I really can't find solution.
This is part of cmake code (it's not my (opensource)):
if (${CMAKE_SYSTEM_NAME} MATCHES "Linux" OR MINGW)
if (NOT CMAKE_BUILD_TYPE)
set(CMAKE_BUILD_TYPE "Release")
endif()
add_definitions(-D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE)
set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -pipe -Wall -Wno-unused-function -fvisibility=hidden -Winvalid-pch")
set(CMAKE_C_FLAGS_DEBUG "${CMAKE_C_FLAGS_DEBUG} -O0 -D_DEBUG")
set(CMAKE_C_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE} -fno-strict-aliasing -ffast-math -funroll-loops -msse2 -O2")
if (${CMAKE_SYSTEM_NAME} MATCHES "Linux")
set(CMAKE_CXX_FLAGS "${CMAKE_C_FLAGS} -std=c++11")
else()
set(CMAKE_CXX_FLAGS "${CMAKE_C_FLAGS} -std=c++11")
endif()
set(CMAKE_CXX_FLAGS_DEBUG "${CMAKE_C_FLAGS_DEBUG}")
set(CMAKE_CXX_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE}")
set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -std=gnu99 -D_POSIX_C_SOURCE=200112L -D_XOPEN_SOURCE=500")
add_common_link_flags("-Wl,--as-needed")
add_release_link_flags("-s")
if (MINGW)
add_definitions(-D_WIN32_WINNT=_WIN32_WINNT_VISTA)
set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wno-unknown-pragmas")
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wno-unknown-pragmas")
add_common_link_flags("-static -static-libgcc -static-libstdc++")
endif()
endif()
cmake
asked Nov 20 '18 at 16:04
Maxim TemnyMaxim Temny
85
Good evening.
I'm getting warning when run cmake.
I searched solution but found only like "replace "make" to "$(MAKE)"".
BUT!
I can't find this string.
Even grep doesn't save me.
Forgive me if this is a stupid question. I really can't find solution.
This is part of cmake code (it's not my (opensource)):
if (${CMAKE_SYSTEM_NAME} MATCHES "Linux" OR MINGW)
if (NOT CMAKE_BUILD_TYPE)
set(CMAKE_BUILD_TYPE "Release")
endif()
add_definitions(-D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE)
set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -pipe -Wall -Wno-unused-function -fvisibility=hidden -Winvalid-pch")
set(CMAKE_C_FLAGS_DEBUG "${CMAKE_C_FLAGS_DEBUG} -O0 -D_DEBUG")
set(CMAKE_C_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE} -fno-strict-aliasing -ffast-math -funroll-loops -msse2 -O2")
if (${CMAKE_SYSTEM_NAME} MATCHES "Linux")
set(CMAKE_CXX_FLAGS "${CMAKE_C_FLAGS} -std=c++11")
else()
set(CMAKE_CXX_FLAGS "${CMAKE_C_FLAGS} -std=c++11")
endif()
set(CMAKE_CXX_FLAGS_DEBUG "${CMAKE_C_FLAGS_DEBUG}")
set(CMAKE_CXX_FLAGS_RELEASE "${CMAKE_C_FLAGS_RELEASE}")
set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -std=gnu99 -D_POSIX_C_SOURCE=200112L -D_XOPEN_SOURCE=500")
add_common_link_flags("-Wl,--as-needed")
add_release_link_flags("-s")
if (MINGW)
add_definitions(-D_WIN32_WINNT=_WIN32_WINNT_VISTA)
set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wno-unknown-pragmas")
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wno-unknown-pragmas")
add_common_link_flags("-static -static-libgcc -static-libstdc++")
endif()
endif()
cmake
cmake
asked Nov 20 '18 at 16:04
Maxim TemnyMaxim Temny
85
asked Nov 20 '18 at 16:04
Maxim TemnyMaxim Temny
85
edited Dec 4 '18 at 18:07
Maxim Temny
asked Nov 20 '18 at 16:04
Maxim TemnyMaxim Temny
85
asked Nov 20 '18 at 16:04
Maxim TemnyMaxim Temny
85
asked Nov 20 '18 at 16:04
Maxim TemnyMaxim Temny
85
85
The part of the code you provide doesn't emit any build rule, thus it is unrelated to the warning. As the project is not yours, you are better to ignore this warning - it doesn't affect on build correctness. If you want to fix it, you need to have better understanding of the code. Probably, the warning is caused byExternalProject_Addcommand invocation, like described in that question: stackoverflow.com/questions/33171335/….
– Tsyvarev
Nov 20 '18 at 21:19
Thanks for you answer, but no. I saw it and "was grep" all project. There is nothing there.
– Maxim Temny
Nov 20 '18 at 23:48
Well, I know the only reason of this warning: your project has a command which invokesmake. It could beCMakeLists.txtwhich contains such command, or it could be some other file which is included intoCMakeLists.txt. Without viewing the appropriate part of the code, we couldn't point to the string causing the warning. In that case we can only guess, but it is not how Stack Overflow works. We want Minimal, Complete, and Verifiable example which reproduces the problem. If you cannot reproduce the problem in, say, 100 lines of code (but NOT a whole project), you may report the problem to developers.
– Tsyvarev
Nov 21 '18 at 8:45
add a comment |
The part of the code you provide doesn't emit any build rule, thus it is unrelated to the warning. As the project is not yours, you are better to ignore this warning - it doesn't affect on build correctness. If you want to fix it, you need to have better understanding of the code. Probably, the warning is caused byExternalProject_Addcommand invocation, like described in that question: stackoverflow.com/questions/33171335/….
– Tsyvarev
Nov 20 '18 at 21:19
Thanks for you answer, but no. I saw it and "was grep" all project. There is nothing there.
– Maxim Temny
Nov 20 '18 at 23:48
Well, I know the only reason of this warning: your project has a command which invokesmake. It could beCMakeLists.txtwhich contains such command, or it could be some other file which is included intoCMakeLists.txt. Without viewing the appropriate part of the code, we couldn't point to the string causing the warning. In that case we can only guess, but it is not how Stack Overflow works. We want Minimal, Complete, and Verifiable example which reproduces the problem. If you cannot reproduce the problem in, say, 100 lines of code (but NOT a whole project), you may report the problem to developers.
– Tsyvarev
Nov 21 '18 at 8:45
The part of the code you provide doesn't emit any build rule, thus it is unrelated to the warning. As the project is not yours, you are better to ignore this warning - it doesn't affect on build correctness. If you want to fix it, you need to have better understanding of the code. Probably, the warning is caused by
ExternalProject_Add command invocation, like described in that question: stackoverflow.com/questions/33171335/….– Tsyvarev
Nov 20 '18 at 21:19
The part of the code you provide doesn't emit any build rule, thus it is unrelated to the warning. As the project is not yours, you are better to ignore this warning - it doesn't affect on build correctness. If you want to fix it, you need to have better understanding of the code. Probably, the warning is caused by
ExternalProject_Add command invocation, like described in that question: stackoverflow.com/questions/33171335/….– Tsyvarev
Nov 20 '18 at 21:19
Thanks for you answer, but no. I saw it and "was grep" all project. There is nothing there.
– Maxim Temny
Nov 20 '18 at 23:48
Thanks for you answer, but no. I saw it and "was grep" all project. There is nothing there.
– Maxim Temny
Nov 20 '18 at 23:48
Well, I know the only reason of this warning: your project has a command which invokes
make. It could be CMakeLists.txt which contains such command, or it could be some other file which is included into CMakeLists.txt. Without viewing the appropriate part of the code, we couldn't point to the string causing the warning. In that case we can only guess, but it is not how Stack Overflow works. We want Minimal, Complete, and Verifiable example which reproduces the problem. If you cannot reproduce the problem in, say, 100 lines of code (but NOT a whole project), you may report the problem to developers.– Tsyvarev
Nov 21 '18 at 8:45
Well, I know the only reason of this warning: your project has a command which invokes
make. It could be CMakeLists.txt which contains such command, or it could be some other file which is included into CMakeLists.txt. Without viewing the appropriate part of the code, we couldn't point to the string causing the warning. In that case we can only guess, but it is not how Stack Overflow works. We want Minimal, Complete, and Verifiable example which reproduces the problem. If you cannot reproduce the problem in, say, 100 lines of code (but NOT a whole project), you may report the problem to developers.– Tsyvarev
Nov 21 '18 at 8:45
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53396967%2fwarning-jobserver-unavailable-using-j1-add-to-parent-make-rule%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53396967%2fwarning-jobserver-unavailable-using-j1-add-to-parent-make-rule%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The part of the code you provide doesn't emit any build rule, thus it is unrelated to the warning. As the project is not yours, you are better to ignore this warning - it doesn't affect on build correctness. If you want to fix it, you need to have better understanding of the code. Probably, the warning is caused by
ExternalProject_Addcommand invocation, like described in that question: stackoverflow.com/questions/33171335/….– Tsyvarev
Nov 20 '18 at 21:19
Thanks for you answer, but no. I saw it and "was grep" all project. There is nothing there.
– Maxim Temny
Nov 20 '18 at 23:48
Well, I know the only reason of this warning: your project has a command which invokes
make. It could beCMakeLists.txtwhich contains such command, or it could be some other file which is included intoCMakeLists.txt. Without viewing the appropriate part of the code, we couldn't point to the string causing the warning. In that case we can only guess, but it is not how Stack Overflow works. We want Minimal, Complete, and Verifiable example which reproduces the problem. If you cannot reproduce the problem in, say, 100 lines of code (but NOT a whole project), you may report the problem to developers.– Tsyvarev
Nov 21 '18 at 8:45