Re: [CMake] My previous message

[Raymond Wan]

On 4/11/2018 4:01 PM, Osman Zakir wrote:
I tried to do it before, but it won't let me clone the 
repository without sudo for some reason.



I have little experience with Docker -- actually, none.  But 
as several people have hinted to you already, this doesn't 
seem like a CMake issue.


For example, from this statement above, it sounds like you 
have a problem with why you have to use sudo to clone the 
repository.  You got around this problem by using sudo, but 
that has opened up other problems that make you believe it 
is an issue with CMake.


Personally, I have never cloned a repository using sudo. 
"sudo" is really a last resort, and every time one has to 
use it, one should ask if there is a better way.  At most, I 
would clone it with my own account and then perform the 
installation step (i.e., "make install" using sudo).  Of 
course, if you have to use "sudo" to compile, then that's 
also an issue but not related to CMake.


Anyway, in case no one else can give you better advice than 
this, I suggest you take a step back and look at why you 
have to use sudo to clone.  This might mean that you should 
ask a Docker mailing list for help.


Ray

PS:  Apologies if something I said here is incorrect. 
Honestly, I haven't followed your problem from the very 
beginning.



--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] My previous message

[Osman Zakir]

I tried to do it before, but it won't let me clone the repository without sudo 
for some reason.

From: Craig Scott 
Sent: Sunday, November 4, 2018 12:49 PM
To: osmanzaki...@hotmail.com
Cc: CMake
Subject: Re: [CMake] My previous message

You are using sudo for your git operations and to make directories, then trying 
to run cmake inside those directories without sudo. CMake won't be able to 
write to directories created (and therefore owned) by root in most cases 
(unless you have a very permissive umask set). I'd recommend not using sudo to 
do the git clone or directory creation. Running cmake under sudo would not be 
recommended.

On Sun, Nov 4, 2018 at 6:22 PM Osman Zakir 
mailto:osmanzaki...@hotmail.com>> wrote:
Did no one see my previous message here?  About the CMake errors in the Docker 
image.  I really don't know how to fix this so some help would really be 
appreciated.  It really is mainly about CMake right now, not Docker itself.  
Both the Dockerfile and the part of the build output with errors from CMake are 
attached to this message.

I don't know what I could try either, or else I really would've tried something 
before sending a message here.
--

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake


--
Craig Scott
Melbourne, Australia
https://crascit.com

New book released: Professional CMake: A Practical 
Guide
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

Re: [CMake] My previous message

[Craig Scott]

You are using sudo for your git operations and to make directories, then
trying to run cmake inside those directories without sudo. CMake won't be
able to write to directories created (and therefore owned) by root in most
cases (unless you have a very permissive umask set). I'd recommend not
using sudo to do the git clone or directory creation. Running cmake under
sudo would not be recommended.

On Sun, Nov 4, 2018 at 6:22 PM Osman Zakir  wrote:

> Did no one see my previous message here?  About the CMake errors in the
> Docker image.  I really don't know how to fix this so some help would
> really be appreciated.  It really is mainly about CMake right now, not
> Docker itself.  Both the Dockerfile and the part of the build output with
> errors from CMake are attached to this message.
>
> I don't know what I could try either, or else I really would've tried
> something before sending a message here.
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> https://cmake.org/mailman/listinfo/cmake
>


-- 
Craig Scott
Melbourne, Australia
https://crascit.com

New book released: Professional CMake: A Practical Guide

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
https://cmake.org/mailman/listinfo/cmake

[CMake] My previous message

[Osman Zakir]

Did no one see my previous message here?  About the CMake errors in the Docker 
image.  I really don't know how to fix this so some help would really be 
appreciated.  It really is mainly about CMake right now, not Docker itself.  
Both the Dockerfile and the part of the build output with errors from CMake are 
attached to this message.

I don't know what I could try either, or else I really would've tried something 
before sending a message here.


dockerfile
Description: dockerfile
Step 16/25 : RUN sudo git clone https://github.com/flexferrum/jinja2cpp && 
cd jinja2cpp && sudo git submodule -q update --init && sudo mkdir build 
&& cd build && cmake .. -DCMAKE_INSTALL_PREFIX=../install 
-DCMAKE_PREFIX_PATH:PATH=/usr/local/include -DBOOST_ROOT=/usr/local/include 
&& cmake --build . --target all && cmake --build . --target install
 ---> Running in c51ec4e921ab
Cloning into 'jinja2cpp'...
remote: Enumerating objects: 77, done.
remote: Counting objects: 100% (77/77), done.
remote: Compressing objects: 100% (62/62), done.
remote: Total 1364 (delta 31), reused 30 (delta 14), pack-reused 1287
Receiving objects: 100% (1364/1364), 400.08 KiB | 5.00 KiB/s, done.
Resolving deltas: 100% (937/937), done.
CMake Error at 
/usr/local/cmake/share/cmake-3.12/Modules/CMakeDetermineSystem.cmake:174 (file):
  file failed to open for writing (No such file or directory):

/home/osman/app/jinja2cpp/build/CMakeFiles/CMakeOutput.log
Call Stack (most recent call first):
  CMakeLists.txt:2 (project)


CMake Error: Could not open file for write in copy operation 
/home/osman/app/jinja2cpp/build/CMakeFiles/3.12.4/CMakeSystem.cmake.tmp
CMake Error: : System Error: No such file or directory
CMake Error at 
/usr/local/cmake/share/cmake-3.12/Modules/CMakeDetermineSystem.cmake:186 
(configure_file):
  configure_file Problem configuring file
Call Stack (most recent call first):
  CMakeLists.txt:2 (project)


CMake Error at 
/usr/local/cmake/share/cmake-3.12/Modules/CMakeDetermineCompilerId.cmake:161 
(file):
  file problem creating directory:
  /home/osman/app/jinja2cpp/build/CMakeFiles/3.12.4/CompilerIdC
Call Stack (most recent call first):
  /usr/local/cmake/share/cmake-3.12/Modules/CMakeDetermineCompilerId.cmake:31 
(CMAKE_DETERMINE_COMPILER_ID_BUILD)
  /usr/local/cmake/share/cmake-3.12/Modules/CMakeDetermineCCompiler.cmake:112 
(CMAKE_DETERMINE_COMPILER_ID)
  CMakeLists.txt:2 (project)


CMake Error at 
/usr/local/cmake/share/cmake-3.12/Modules/CMakeDetermineCompilerId.cmake:161 
(file):
  file problem creating directory:
  /home/osman/app/jinja2cpp/build/CMakeFiles/3.12.4/CompilerIdC
Call Stack (most recent call first):
  /usr/local/cmake/share/cmake-3.12/Modules/CMakeDetermineCompilerId.cmake:31 
(CMAKE_DETERMINE_COMPILER_ID_BUILD)
  /usr/local/cmake/share/cmake-3.12/Modules/CMakeDetermineCCompiler.cmake:112 
(CMAKE_DETERMINE_COMPILER_ID)
  CMakeLists.txt:2 (project)


CMake Error at 
/usr/local/cmake/share/cmake-3.12/Modules/CMakeDetermineCompilerId.cmake:161 
(file):
  file problem creating directory:
  /home/osman/app/jinja2cpp/build/CMakeFiles/3.12.4/CompilerIdC
Call Stack (most recent call first):
  /usr/local/cmake/share/cmake-3.12/Modules/CMakeDetermineCompilerId.cmake:31 
(CMAKE_DETERMINE_COMPILER_ID_BUILD)
  /usr/local/cmake/share/cmake-3.12/Modules/CMakeDetermineCCompiler.cmake:112 
(CMAKE_DETERMINE_COMPILER_ID)
  CMakeLists.txt:2 (project)


CMake Error at 
/usr/local/cmake/share/cmake-3.12/Modules/CMakeDetermineCompilerId.cmake:161 
(file):
  file problem creating directory:
  /home/osman/app/jinja2cpp/build/CMakeFiles/3.12.4/CompilerIdC
Call Stack (most recent call first):
  /usr/local/cmake/share/cmake-3.12/Modules/CMakeDetermineCompilerId.cmake:31 
(CMAKE_DETERMINE_COMPILER_ID_BUILD)
  /usr/local/cmake/share/cmake-3.12/Modules/CMakeDetermineCCompiler.cmake:112 
(CMAKE_DETERMINE_COMPILER_ID)
  CMakeLists.txt:2 (project)


CMake Error at 
/usr/local/cmake/share/cmake-3.12/Modules/CMakeDetermineCompilerId.cmake:161 
(file):
  file problem creating directory:
  /home/osman/app/jinja2cpp/build/CMakeFiles/3.12.4/CompilerIdC
Call Stack (most recent call first):
  /usr/local/cmake/share/cmake-3.12/Modules/CMakeDetermineCompilerId.cmake:31 
(CMAKE_DETERMINE_COMPILER_ID_BUILD)
  /usr/local/cmake/share/cmake-3.12/Modules/CMakeDetermineCCompiler.cmake:112 
(CMAKE_DETERMINE_COMPILER_ID)
  CMakeLists.txt:2 (project)


CMake Error at 
/usr/local/cmake/share/cmake-3.12/Modules/CMakeDetermineCompilerId.cmake:161 
(file):
  file problem creating directory:
  /home/osman/app/jinja2cpp/build/CMakeFiles/3.12.4/CompilerIdC
Call Stack (most recent call first):
  /usr/local/cmake/share/cmake-3.12/Modules/CMakeDetermineCompilerId.cmake:31 
(CMAKE_DETERMINE_COMPILER_ID_BUILD)
  /usr/local/cmake/share/cmake-3.12/Modules/CMakeDetermineCCompiler.cmake:112 
(CMAKE_DETERMINE_COMPILER_ID)
  CMakeLists.txt:2 (project)


CMake Error at 
/usr/local/cmake/share/cmake-3.12/Modules/CMakeDetermineCompilerId.cmake:161 
(file):