[DaveP]

 

Hi,

The build ‘succeeded’ (ie it produced a valid and runnable executable) whether or not I changed the path. I see that the original PATH had c:\SysGCC\Raspberry\bin included (I believe this is the default toolchain location – never used on this PC). I believe the build works OK anyway because the build procedure adds ‘c:\Pi\Toolchain\bin’ to the PATH itself (4th line from bottom in listing above).

Anyway, I added ‘c:\Pi\Toolchain\bin’ permanently to the system path, rebooted and it made no difference. Screenshots of the PATH on the PC and the Pi are below.

So if the executable is being successfully created on the PC, what could give rise to the error messages in the build process? It appeared to me that ‘make’ was being initiated from within a VisualGDB program and – as ‘make’ runs successfully from the command line –  it was other processes within that program that must have been producing the error messages.

You say that the transfer to the Pi happens when debugging starts but surely it must happen before the debug command is executed on the Pi. Is VGDB previously checking that it has a valid path to transfer the executable to (and for some reason not finding it)? My suspicion is that, somewhere within its bowels and only for some purposes, VGDB is still assuming that the toolchain is in its default location (c:\SysGCC…).

One other (possibly irrelevant) fact. The test program (standard, system-generated ‘Hello World’) shows intellisense errors on <iostream>, namespace std;, cout and endl (ie iostream is not being found), even though I have synchronised all includes and libraries in the toolchain (twice). Clearly the compliler is finding the header, as it completes and links OK. Is there some data value or default within VGDB that could be causing this and other problems?

Sorry to ramble a little but, as you can imagine, I am becoming very frustrated with this problem and not getting any work done! Will appreciate your further thoughts.

 

### Path on the PC (line breaks inserted to aid readability)
PATH=C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;
C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;
C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Common Files\Sage SData\;
C:\Program Files (x86)\WinMerge;C:\Program Files\Microsoft\Web Platform Installer\;
C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\;
C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\;
C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\;
C:\Program Files (x86)\Microsoft ASP.NET\ASP.NET Web Pages\v1.0\;
C:\Program Files (x86)\Windows Kits\8.0\Windows Performance Toolkit\;
C:\Program Files (x86)\QuickTime\QTSystem\;
C:\Program Files (x86)\MySQL\MySQL Fabric 1.5.4 & MySQL Utilities 1.5.4 1.5\;
C:\Program Files (x86)\MySQL\MySQL Fabric 1.5.4 & MySQL Utilities 1.5.4 1.5\Doctrine extensions for PHP\;
C:\Program Files (x86)\Skype\Phone\;c:\Pi\Toolchain\bin;;C:\SysGCC\Raspberry\bin

### Make successful without errors from PC command line – produces viable executable
c:\Dev\Cpp\Test\Test4\Test4>make
C:/Pi/Toolchain/bin/arm-linux-gnueabihf-g++.exe -ggdb -ffunction-sections -O0 -std=c++11   -DDEBUG  -c Test4.cpp -o Debug/Test4.o -MD -MF Debug/Test4.dep
C:/Pi/Toolchain/bin/arm-linux-gnueabihf-g++.exe -o Debug/Test4 -Wl,-gc-sections    -Wl,–start-group Debug/Test4.o   -Wl,–rpath=’$ORIGIN’   -Wl,–end-group
c:\Dev\Cpp\Test\Test4\Test4>

### Path on the Pi
pi@RaspberryPi ~ $ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games

### Test executable Test4 transferred to the Pi and permissions changed
pi@RaspberryPi ~ $ cd /tmp
pi@RaspberryPi /tmp $ ls -l
total 1244
-rwxrwxrwx 1 pi pi 1239120 Nov  7 17:30 DpDateTest
-rw-r–r– 1 pi pi     313 Nov  8 16:49 ld.so.conf
-rwxrwxrwx 1 pi pi   24772 Nov  8 15:55 Test4

### Test4 running successfully on the Pi
pi@RaspberryPi /tmp $ ./Test4
Hello, World!
pi@RaspberryPi /tmp $

 

[DaveP]

Hi Bazis,

I set the PATH as suggested and the make completed without error (having deleted the previous binaries). ‘make all’ also did so.

After ‘manually’ setting the path, the error messages from VGDB were the same as before.

However, I searched the disk and could not find a relevant .elf file.

I don’t think the problem is with the ‘make’ but rather with the transfer to the Pi – because the executable is created OK in the PC debug folder (and was also before changing the PATH). If I copy it to the Pi and change the permissions, it runs fine on the Pi.

[Author]

Posts