• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 122 subscribers
  • Views 10823 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DS-5: recipe for target 'HelloWorld' failed

Richard Tenney

Hi. I've installed the Community Edition of DS-5 v5.26.2 on a Windows 7 machine. My target is the latest Beaglebone Black Wireless. I've tried several Linaro toolchains. With each toolchain, my attempt to compile the initial Hello World program provided by DS-5 fails. For some of the toolchains, even the macro expression EXIT_SUCCESS is undefined (I substiute 0 for it); for others, it is defined. The failure is always the same. I've tried toolchain version 6.1.1 -- specifically 

gcc-linaro-6.2.1-2016.11-i686-mingw32_arm-linux-gnueabihf

-- as well as versions 4.9.4 and 6.2.1.

The results here are for version 4.9.4, but it's virtually the same result for all three.

The Problems window shows

Description Resource Path Location Type
make: *** [HW621] Error 1 HW621 C/C++ Problem
recipe for target 'HW621' failed makefile /HW621/Debug line 30 C/C++ Problem
syntax error HW621 line 1, external location: c:\local\linaro49\gcc-linaro-4.9-2016.02-i686-mingw32_arm-linux-gnueabihf\arm-linux-gnueabihf\bin\ld.exe:c:\local\linaro49\gcc-linaro-4.9-2016.02-i686-mingw32_arm-linux-gnueabihf\arm-linux-gnueabihf\libc\lib\libc.so.6 C/C++ Problem

The Console window shows: 

17:25:06 **** Build of configuration Debug for project HW621 ****
make all
'Building file: ../src/HW621.c'
'Invoking: GCC C Compiler 4.9.4 [arm-linux-gnueabihf]'
arm-linux-gnueabihf-gcc.exe -O0 -g -Wall -c -fmessage-length=0 -MMD -MP -MF"src/HW621.d" -MT"src/HW621.o" -o "src/HW621.o" "../src/HW621.c"
'Finished building: ../src/HW621.c'
' '
'Building target: HW621'
'Invoking: GCC C Linker 4.9.4 [arm-linux-gnueabihf]'
arm-linux-gnueabihf-gcc.exe -o "HW621" ./src/HW621.o
c:/local/linaro49/gcc-linaro-4.9-2016.02-i686-mingw32_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld.exe:c:\local\linaro49\gcc-linaro-4.9-2016.02-i686-mingw32_arm-linux-gnueabihf\bin\../arm-linux-gnueabihf/libc/lib/libc.so.6: file format not recognized; treating as linker script
c:/local/linaro49/gcc-linaro-4.9-2016.02-i686-mingw32_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-gnueabihf/4.9.4/../../../../arm-linux-gnueabihf/bin/ld.exe:c:\local\linaro49\gcc-linaro-4.9-2016.02-i686-mingw32_arm-linux-gnueabihf\bin\../arm-linux-gnueabihf/libc/lib/libc.so.6:1: syntax error
collect2.exe: error: ld returned 1 exit status
make: *** [HW621] Error 1
makefile:30: recipe for target 'HW621' failed

17:25:08 Build Finished (took 2s.44ms)

 

PLEASE can someone help me? I've hacked around this for three or four days, installing and uninstalling DS-5 and various toolchains. I've fiddled with my PATH variables, installed GNU make in a directory at the front of the PATH (to hide the make program associated with Delphi7 that was already there), etc. I'm stuck!

 

Thanks,

Richard

Parents
  • 0
    Hi Richard,
    Unfortunately it looks like neither of those toolchains extract properly under some circumstances on a Windows system - for GCC 4.9.4 all I get is symbolic link failures and requests to overwrite include files because of case-invariance in the filesystem.

    Essentially, just by extracting those Linaro tarballs on a Windows system, you get a corrupted installation. Here, because of the above errors, libc\lib\libc.so.6 is a 0-byte file which somewhat explains (although boggles the mind) as to why the linker attempts to use it as a linker script. Can you check if yours is 0-bytes too, that would confirm it's the same issue.
Reply
  • 0
    Hi Richard,
    Unfortunately it looks like neither of those toolchains extract properly under some circumstances on a Windows system - for GCC 4.9.4 all I get is symbolic link failures and requests to overwrite include files because of case-invariance in the filesystem.

    Essentially, just by extracting those Linaro tarballs on a Windows system, you get a corrupted installation. Here, because of the above errors, libc\lib\libc.so.6 is a 0-byte file which somewhat explains (although boggles the mind) as to why the linker attempts to use it as a linker script. Can you check if yours is 0-bytes too, that would confirm it's the same issue.
Children