cc: error: ProvideDirectories: No such file or directory

Sysprogs forums Forums VisualGDB cc: error: ProvideDirectories: No such file or directory

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #9255
    slavav
    Participant

    Hi,

    source: VS2015; target: Ubuntu, virtual, hyper-V

    simple static lib – 1-2 files – not problem – compiled fantastic.

    after adding several files into project (using d-n-d from explorer) – this error:

    1>—— Rebuild All started: Project: sqlite, Configuration: Debug VisualGDB ——

    1> VisualGDB: Run “rm -rf “/tmp/VisualGDB/c/Git/Archive-Dashboard-WxWin/vpacs/linux/sqlite/VisualGDB/Debug”” in directory “” on slava@192.168.0.100 (SSH)

    1> VisualGDB: Sending 56 updated source files to build machine…

    1> VisualGDB: Run “make -f “VisualGDB/Debug/sqlite.msbuild-mak”” in directory “/tmp/VisualGDB/c/Git/Archive-Dashboard-WxWin/vpacs/linux/sqlite” on slava@192.168.0.100 (SSH)

    1> os.c

    1> sqlite.cpp

    1> cc build.c ProvideDirectories UpdateRSP/VisualGDB/Debug/os.o UpdateRSP/VisualGDB/Debug/sqlite.o UpdateRSP/../VisualGDB/Debug/sqlite.ar.rsp ../VisualGDB/Debug/sqlite.a -o build

    1> cc: error: ProvideDirectories: No such file or directory

    1> cc: error: UpdateRSP/VisualGDB/Debug/os.o: No such file or directory

    1> cc: error: UpdateRSP/VisualGDB/Debug/sqlite.o: No such file or directory

    1> cc: error: UpdateRSP/../VisualGDB/Debug/sqlite.ar.rsp: No such file or directory

    1> <builtin>: recipe for target ‘build’ failed

    1> make: *** [build] Error 1

    1> ————————————————————-

    1> Command exited with code 2

    1> Executable: make

    1> Arguments: -f “VisualGDB/Debug/sqlite.msbuild-mak”

    1> Directory: /tmp/VisualGDB/c/Git/Archive-Dashboard-WxWin/vpacs/linux/sqlite

    1> VisualGDB: Error: Command-line action failed

    1> error: Build has failed. See the Output window for more details.

    1>C:\Program Files (x86)\Sysprogs\VisualGDB\MSBuild\Targets\remote.targets(15,2): error : Build failed. Please examine the build output (View->Output) for details.

    ========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========

     

    Thanks.

    Is maybe some option exists to use absolute path and not relative via RSP?

    Due to files exists on target system

    #9258
    support
    Keymaster

    Hi,

    This looks like the Makefile got corrupt somehow. Could you please attach it so that we could quicky check for common problems?

    #9261
    slavav
    Participant

    I couldn’t understand how to insert sqlite.msbuild-mak file. Thus content:

     

     

    #This file is generated by VisualGDB from your MSBuild project.

    #Do not edit it manually as it will be regenerated on each build.

    #You can build this project manually by running the following command line:

    # make -f <path to this file>

    #The ‘prepare’ target needs to be built before the ‘build’ target to ensure all

    #response files are up-to-date

     

    ifneq ($(VERBOSE),1)

    _V := @

    endif

     

    build:

     

    ProvideDirectories:

    @mkdir -p VisualGDB/Debug/

     

    PREPARE_TARGETS := ProvideDirectories

     

    #ClCompile – 2 files

     

    UpdateRSP/VisualGDB/Debug/os.o:

    $(_V)echo “-ggdb -O0 -DDEBUG=1 -ffunction-sections -fdata-sections” > VisualGDB/Debug/os.gcc.rsp-new

    $(_V)cmp –silent VisualGDB/Debug/os.gcc.rsp-new VisualGDB/Debug/os.gcc.rsp || cp VisualGDB/Debug/os.gcc.rsp-new VisualGDB/Debug/os.gcc.rsp

     

    UpdateRSP/VisualGDB/Debug/sqlite.o:

    $(_V)echo “-ggdb -O0 -DDEBUG=1 -ffunction-sections -fdata-sections” > VisualGDB/Debug/sqlite.gcc.rsp-new

    $(_V)cmp –silent VisualGDB/Debug/sqlite.gcc.rsp-new VisualGDB/Debug/sqlite.gcc.rsp || cp VisualGDB/Debug/sqlite.gcc.rsp-new VisualGDB/Debug/sqlite.gcc.rsp

     

    -include VisualGDB/Debug/os.dep

    VisualGDB/Debug/os.o: os.c VisualGDB/Debug/os.gcc.rsp

    @echo os.c

    $(_V)gcc @VisualGDB/Debug/os.gcc.rsp -c “os.c” -o “VisualGDB/Debug/os.o” -MD -MP -MF “VisualGDB/Debug/os.dep”

     

    -include VisualGDB/Debug/sqlite.dep

    VisualGDB/Debug/sqlite.o: sqlite.cpp VisualGDB/Debug/sqlite.gcc.rsp

    @echo sqlite.cpp

    $(_V)g++ @VisualGDB/Debug/sqlite.gcc.rsp -c “sqlite.cpp” -o “VisualGDB/Debug/sqlite.o” -MD -MP -MF “VisualGDB/Debug/sqlite.dep”

     

    PREPARE_TARGETS += UpdateRSP/VisualGDB/Debug/os.o UpdateRSP/VisualGDB/Debug/sqlite.o

    CLCOMPILE_TARGETS += VisualGDB/Debug/os.o VisualGDB/Debug/sqlite.o

     

     

    UpdateRSP/../VisualGDB/Debug/sqlite.ar.rsp:

    $(_V)mkdir -p “../VisualGDB/Debug”

    $(_V)echo “-r ../VisualGDB/Debug/sqlite.a VisualGDB/Debug/os.o VisualGDB/Debug/sqlite.o” > ../VisualGDB/Debug/sqlite.ar.rsp-new

    $(_V)cmp –silent ../VisualGDB/Debug/sqlite.ar.rsp-new ../VisualGDB/Debug/sqlite.ar.rsp || cp ../VisualGDB/Debug/sqlite.ar.rsp-new ../VisualGDB/Debug/sqlite.ar.rsp

     

    ../VisualGDB/Debug/sqlite.a: ../VisualGDB/Debug/sqlite.ar.rsp VisualGDB/Debug/os.o VisualGDB/Debug/sqlite.o

    $(_V)ar @../VisualGDB/Debug/sqlite.ar.rsp

     

    PREPARE_TARGETS += UpdateRSP/../VisualGDB/Debug/sqlite.ar.rsp

    FINAL_TARGETS += ../VisualGDB/Debug/sqlite.a

     

     

    .PHONY: $(PREPARE_TARGETS)

    build: $(PREPARE_TARGETS) $(FINAL_TARGETS)

     

     

    • This reply was modified 7 years, 5 months ago by slavav.
    #9267
    slavav
    Participant

    I use trial. Is there trial limitation for… number of files? project dependancies?

    due to very strange error.

    I create new static lib project – build OK

    add 2-3 files – build OK

    I create another static lib project – Build OK

    I add reference from one project to another – build error.

    remove reference – doesn’t help.

     

    Another situation:

    new project – buld OK

    add 1-2 new files – build OK

    add 3-rd file – build fail.  Why????

    I remove this 3-rd file – build failed at any rate. That’s all.  Visually make file looks good for me

    #9275
    support
    Keymaster

    Hi,

    There are no functional limitations in the trial version. The VisualGDB MSBuild backend is relatively new, so this actually looks like a bug triggered by “..” in some of the paths.

    Could you please send your .vcxproj, .filters, .vgdbsettings and .sln files to support@sysprogs.com? This should help us reproduce and fix this.

    #9350
    slavav
    Participant

    Sent. Thanks!!!  I sit crossing fingers )))

     

    ps: I forget to send sln, but nothing special in it:

    Microsoft Visual Studio Solution File, Format Version 12.00

    # Visual Studio 14

    VisualStudioVersion = 14.0.25123.0

    MinimumVisualStudioVersion = 10.0.40219.1

    Project(“{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}”) = “tesst”, “tesst\tesst.vcxproj”, “{46E4911E-1E99-4B9F-9D81-C8C2037EC2F3}”

    EndProject

    Global

    GlobalSection(SolutionConfigurationPlatforms) = preSolution

    Debug|VisualGDB = Debug|VisualGDB

    Debug|x64 = Debug|x64

    Debug|x86 = Debug|x86

    Release|VisualGDB = Release|VisualGDB

    Release|x64 = Release|x64

    Release|x86 = Release|x86

    EndGlobalSection

    GlobalSection(ProjectConfigurationPlatforms) = postSolution

    {46E4911E-1E99-4B9F-9D81-C8C2037EC2F3}.Debug|VisualGDB.ActiveCfg = Debug|VisualGDB

    {46E4911E-1E99-4B9F-9D81-C8C2037EC2F3}.Debug|VisualGDB.Build.0 = Debug|VisualGDB

    {46E4911E-1E99-4B9F-9D81-C8C2037EC2F3}.Debug|x64.ActiveCfg = Debug|VisualGDB

    {46E4911E-1E99-4B9F-9D81-C8C2037EC2F3}.Debug|x86.ActiveCfg = Debug|VisualGDB

    {46E4911E-1E99-4B9F-9D81-C8C2037EC2F3}.Release|VisualGDB.ActiveCfg = Release|VisualGDB

    {46E4911E-1E99-4B9F-9D81-C8C2037EC2F3}.Release|VisualGDB.Build.0 = Release|VisualGDB

    {46E4911E-1E99-4B9F-9D81-C8C2037EC2F3}.Release|x64.ActiveCfg = Release|VisualGDB

    {46E4911E-1E99-4B9F-9D81-C8C2037EC2F3}.Release|x86.ActiveCfg = Release|VisualGDB

    EndGlobalSection

    GlobalSection(SolutionProperties) = preSolution

    HideSolutionNode = FALSE

    EndGlobalSection

    EndGlobal

     

     

    • This reply was modified 7 years, 5 months ago by slavav.
    #9368
    support
    Keymaster

    Hi,

    Thanks, we have located and fixed the problem. It was caused by a conflict between an internal target called ‘build’ and build.c in your project. Please try this build: VisualGDB-5.2.12.1269.msi

    #9382
    slavav
    Participant

    Yessss!!  Thanks, I can build now. Continue checking further. Thanks!

Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.