Sysprogs forums › Forums › VisualGDB › i586-poky-linux-gcc.exe: error: CreateProcess: No such file or directory
- This topic has 7 replies, 2 voices, and was last updated 7 years, 6 months ago by support.
-
AuthorPosts
-
April 28, 2017 at 15:37 #11093christoph.pParticipant
I’ve installed Visual Studio 2017, und the newest VisualGDB. Now I try to compile an
older project, but I get always:Tool arguments: -c “C:\Users\Christoph\AppData\Local\Temp\/VisualGDB_ToolchainTestProgram.c” -o “C:\Users\Christoph\AppData\Local\Temp\/VisualGDB_ToolchainTestProgram.o” -ggdb -ffunction-sections
i586-poky-linux-gcc.exe: error: CreateProcess: No such file or directoryApril 28, 2017 at 16:40 #11094christoph.pParticipantPlease help. I have to get it to work fast…
April 28, 2017 at 16:53 #11095supportKeymasterHi,
This looks like a corrupt toolchain. Is it one of the toolchains shipped with VisualGDB?
April 28, 2017 at 18:25 #11096christoph.pParticipantThank you very much for your answer!
No. As the Tutorial in (https://visualgdb.com/tutorials/linux/edison/) doesn’t work any more (the Intel Edison
Installer doesn’t offer any development environment any more), I have extracted the toolchain somewhere out
of the archives of here: https://downloadcenter.intel.com/de/product/84574/Intel-Edison-Board-for-Arduino-On my previous PC, the toolchain I used worked well. But now I get this strange error. I read in the net that
with Mingw it’s often a PATH environment var problem.Although on my previous PC there weren’t any paths set in “PATH” to any Edison / GDB related directories. Could
this be the problem I have now?The things that have changed from the previous machine to now is Visual Studio (now 2017 and not 2015 any more)
and the Visual GDB Version.As you talked about a VisualGDB shipped toolchain. Can I get a VisualGDB shipped toolchain for the Intel Edison?
That would be very nice because at the moment I have to get it to work in a dubious indirect way.Thanks for you fast help (I hope it’s going on…)
- This reply was modified 7 years, 6 months ago by christoph.p.
April 28, 2017 at 23:17 #11099supportKeymasterHi,
Thanks for the explanation. As Intel Edison is not as popular as Raspberry Pi and other modern boards, we don’t ship a separate toolchain for it (the only other option would be to build a custom toolchain under our toolchain building service that usually costs EUR 1000 per toolchain).
Some GCC toolchains are configured in a way that requires their location to be stored in the registry, so just extracting the files for such a toolchain won’t work. We would recommend checking the archives and 3rd-party sites for a usable toolchain; if the toolchain itself is broken and does not work, VisualGDB unfortunately cannot fix this.
April 29, 2017 at 10:48 #11106christoph.pParticipantI’ve downloaded “Cross Compiler Toolchain for Intel® Edison Maker Board” from here: https://downloadcenter.intel.com/download/24472/Cross-Compiler-Toolchain-for-Intel-Edison-Maker-Board?product=86928
My sysroots is “–sysroot=C:\Users\Christoph\Downloads\edison-toolchain-20150120-windows\i686\pokysdk\usr\bin\i586-poky-linux”
where the downloaded archive is extracted to “C:\Users\Christoph\Downloads\edison-toolchain-20150120-windows”
I’ve not changed anything else on the sample projekt. I think there is some kind of problem with the surrounding environmen (windows 10 / visual studio / visualGDB)?
The test.cpp
<p style=”padding-left: 30px;”>#include <iostream>using namespace std;
int main(int argc, char *argv[])
{
char sz[] = “Hello, World!”; //Hover mouse over “sz” while debugging to see its contents
cout << sz << endl; //<================= Put a breakpoint here
return 0;
}</p>
Thats my makefile:
<p style=”padding-left: 30px;”>#Generated by VisualGDB project wizard.
#Note: VisualGDB will automatically update this file when you add new sources to the project.
#All other changes you make in this file will be preserved.
#Visit http://visualgdb.com/makefiles for more details#VisualGDB: AutoSourceFiles #
TARGETNAME := Test
#TARGETTYPE can be APP, STATIC or SHARED
TARGETTYPE := APPto_lowercase = $(subst A,a,$(subst B,b,$(subst C,c,$(subst D,d,$(subst E,e,$(subst F,f,$(subst G,g,$(subst H,h,$(subst I,i,$(subst J,j,$(subst K,k,$(subst L,l,$(subst M,m,$(subst N,n,$(subst O,o,$(subst P,p,$(subst Q,q,$(subst R,r,$(subst S,s,$(subst T,t,$(subst U,u,$(subst V,v,$(subst W,w,$(subst X,x,$(subst Y,y,$(subst Z,z,$1))))))))))))))))))))))))))
CONFIG ?= DEBUG
CONFIGURATION_FLAGS_FILE := $(call to_lowercase,$(CONFIG)).mak
include $(CONFIGURATION_FLAGS_FILE)
#LINKER_SCRIPT defined inside the configuration file (e.g. debug.mak) should override any linker scripts defined in shared .mak files
CONFIGURATION_LINKER_SCRIPT := $(LINKER_SCRIPT)include $(ADDITIONAL_MAKE_FILES)
ifneq ($(CONFIGURATION_LINKER_SCRIPT),)
LINKER_SCRIPT := $(CONFIGURATION_LINKER_SCRIPT)
endififneq ($(LINKER_SCRIPT),)
LDFLAGS += -T$(LINKER_SCRIPT)
endififeq ($(BINARYDIR),)
error:
$(error Invalid configuration, please check your inputs)
endifSOURCEFILES := Test.cpp
EXTERNAL_LIBS :=
EXTERNAL_LIBS_COPIED := $(foreach lib, $(EXTERNAL_LIBS),$(BINARYDIR)/$(notdir $(lib)))CFLAGS += $(COMMONFLAGS)
CXXFLAGS += $(COMMONFLAGS)
ASFLAGS += $(COMMONFLAGS)
LDFLAGS += $(COMMONFLAGS)CFLAGS += $(addprefix -I,$(INCLUDE_DIRS))
CXXFLAGS += $(addprefix -I,$(INCLUDE_DIRS))CFLAGS += $(addprefix -D,$(PREPROCESSOR_MACROS))
CXXFLAGS += $(addprefix -D,$(PREPROCESSOR_MACROS))
ASFLAGS += $(addprefix -D,$(PREPROCESSOR_MACROS))CXXFLAGS += $(addprefix -framework ,$(MACOS_FRAMEWORKS))
CFLAGS += $(addprefix -framework ,$(MACOS_FRAMEWORKS))
LDFLAGS += $(addprefix -framework ,$(MACOS_FRAMEWORKS))LDFLAGS += $(addprefix -L,$(LIBRARY_DIRS))
ifeq ($(GENERATE_MAP_FILE),1)
LDFLAGS += -Wl,-Map=$(BINARYDIR)/$(basename $(TARGETNAME)).map
endifLIBRARY_LDFLAGS = $(addprefix -l,$(LIBRARY_NAMES))
ifeq ($(IS_LINUX_PROJECT),1)
RPATH_PREFIX := -Wl,–rpath=’$$ORIGIN/../
LIBRARY_LDFLAGS += $(EXTERNAL_LIBS)
LIBRARY_LDFLAGS += -Wl,–rpath=’$$ORIGIN’
LIBRARY_LDFLAGS += $(addsuffix ‘,$(addprefix $(RPATH_PREFIX),$(dir $(EXTERNAL_LIBS))))ifeq ($(TARGETTYPE),SHARED)
CFLAGS += -fPIC
CXXFLAGS += -fPIC
ASFLAGS += -fPIC
LIBRARY_LDFLAGS += -Wl,-soname,$(TARGETNAME)
endififneq ($(LINUX_PACKAGES),)
PACKAGE_CFLAGS := $(foreach pkg,$(LINUX_PACKAGES),$(shell pkg-config –cflags $(pkg)))
PACKAGE_LDFLAGS := $(foreach pkg,$(LINUX_PACKAGES),$(shell pkg-config –libs $(pkg)))
CFLAGS += $(PACKAGE_CFLAGS)
CXXFLAGS += $(PACKAGE_CFLAGS)
LIBRARY_LDFLAGS += $(PACKAGE_LDFLAGS)
endif
else
LIBRARY_LDFLAGS += $(EXTERNAL_LIBS)
endifLIBRARY_LDFLAGS += $(ADDITIONAL_LINKER_INPUTS)
all_make_files := $(firstword $(MAKEFILE_LIST)) $(CONFIGURATION_FLAGS_FILE) $(ADDITIONAL_MAKE_FILES)
ifeq ($(STARTUPFILES),)
all_source_files := $(SOURCEFILES)
else
all_source_files := $(STARTUPFILES) $(filter-out $(STARTUPFILES),$(SOURCEFILES))
endifsource_obj1 := $(all_source_files:.cpp=.o)
source_obj2 := $(source_obj1:.c=.o)
source_obj3 := $(source_obj2:.s=.o)
source_obj4 := $(source_obj3:.S=.o)
source_obj5 := $(source_obj4:.cc=.o)
source_objs := $(source_obj5:.cxx=.o)all_objs := $(addprefix $(BINARYDIR)/, $(notdir $(source_objs)))
PRIMARY_OUTPUTS :=
ifeq ($(GENERATE_BIN_FILE),1)
PRIMARY_OUTPUTS += $(BINARYDIR)/$(basename $(TARGETNAME)).bin
endififeq ($(GENERATE_IHEX_FILE),1)
PRIMARY_OUTPUTS += $(BINARYDIR)/$(basename $(TARGETNAME)).ihex
endififeq ($(PRIMARY_OUTPUTS),)
PRIMARY_OUTPUTS := $(BINARYDIR)/$(TARGETNAME)
endifall: $(PRIMARY_OUTPUTS)
$(BINARYDIR)/$(basename $(TARGETNAME)).bin: $(BINARYDIR)/$(TARGETNAME)
$(OBJCOPY) -O binary $< $@$(BINARYDIR)/$(basename $(TARGETNAME)).ihex: $(BINARYDIR)/$(TARGETNAME)
$(OBJCOPY) -O ihex $< $@ifneq ($(LINKER_SCRIPT),)
$(BINARYDIR)/$(TARGETNAME): $(LINKER_SCRIPT)
endififeq ($(TARGETTYPE),APP)
$(BINARYDIR)/$(TARGETNAME): $(all_objs) $(EXTERNAL_LIBS)
$(LD) -o $@ $(LDFLAGS) $(START_GROUP) $(all_objs) $(LIBRARY_LDFLAGS) $(END_GROUP)
endififeq ($(TARGETTYPE),SHARED)
$(BINARYDIR)/$(TARGETNAME): $(all_objs) $(EXTERNAL_LIBS)
$(LD) -shared -o $@ $(LDFLAGS) $(START_GROUP) $(all_objs) $(LIBRARY_LDFLAGS) $(END_GROUP)
endififeq ($(TARGETTYPE),STATIC)
$(BINARYDIR)/$(TARGETNAME): $(all_objs)
$(AR) -r $@ $^
endif-include $(all_objs:.o=.dep)
clean:
ifeq ($(USE_DEL_TO_CLEAN),1)
cmd /C del /S /Q $(BINARYDIR)
else
rm -rf $(BINARYDIR)
endif$(BINARYDIR):
mkdir $(BINARYDIR)#VisualGDB: FileSpecificTemplates # $(BINARYDIR)/%.o : %.cpp $(all_make_files) |$(BINARYDIR)
$(CXX) $(CXXFLAGS) -c $< -o $@ -MD -MF $(@:.o=.dep)$(BINARYDIR)/%.o : %.c $(all_make_files) |$(BINARYDIR)
$(CC) $(CFLAGS) -c $< -o $@ -MD -MF $(@:.o=.dep)$(BINARYDIR)/%.o : %.S $(all_make_files) |$(BINARYDIR)
$(CC) $(CFLAGS) $(ASFLAGS) -c $< -o $@ -MD -MF $(@:.o=.dep)$(BINARYDIR)/%.o : %.s $(all_make_files) |$(BINARYDIR)
$(CC) $(CFLAGS) $(ASFLAGS) -c $< -o $@ -MD -MF $(@:.o=.dep)$(BINARYDIR)/%.o : %.cc $(all_make_files) |$(BINARYDIR)
$(CC) $(CFLAGS) $(CXXFLAGS) -c $< -o $@ -MD -MF $(@:.o=.dep)$(BINARYDIR)/%.o : %.cxx $(all_make_files) |$(BINARYDIR)
$(CC) $(CFLAGS) $(CXXFLAGS) -c $< -o $@ -MD -MF $(@:.o=.dep)#VisualGDB: GeneratedRules #
</p>April 29, 2017 at 15:09 #11108christoph.pParticipantOk. got it with a new downloaded toolchain from intel. Because the directory structure changed, I hat such problems…
Thanks
April 30, 2017 at 04:07 #11116supportKeymasterHi,
Good to hear it works. If you encounter any further issues, let us know.
-
AuthorPosts
- You must be logged in to reply to this topic.