• State Verified Answer
  • Replies 4 replies
  • Subscribers 74 subscribers
  • Views 5708 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 201401
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Eclipse can't find "${cross_prefix}${cross_c}${cross_suffix}" in PATH

Andy

Hello,

I'm getting an error in Eclipse that makes it unable to find standard libraries and definitions, therefore showing literally thousands of errors with things like uint8_t and such.

I noticed this error in the problems tab:

Description Resource Path Location Type
Program "${cross_prefix}${cross_c}${cross_suffix}" not found in PATH unleashed_nordic Project Properties, C++ Preprocessor Include.../Providers, [CDT GCC Built-in Compiler Settings] options C/C++ Scanner Discovery Problem

It would be very helpful if anyone has any clue about the meaning of that error.

Thanks in advance!

EDIT: The project compiles without a problem, and I know this is just an aesthetic issue, but it's really distracting and it makes it difficult to find errors that are actually errors.

EDIT: Added screenshot of the preprocessor include providers for reference.

EDIT: I followed the troubleshooting guide in https://gnu-mcu-eclipse.github.io/toolchain/path/ and added 

${cross_prefix}${cross_c}${cross_suffix} --version

as a pre-build step. The command gets executed normally as expected:

/Applications/Xcode.app/Contents/Developer/usr/bin/make --no-print-directory pre-build
arm-none-eabi-gcc --version
arm-none-eabi-gcc (GNU Tools for Arm Embedded Processors 7-2017-q4-major) 7.2.1 20170904 (release) [ARM/embedded-7-branch revision 255204]
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

  • 0

    Hi, 

    The error seems to related to the CDT GCC Built-in Compiler Settings provider, which shouldn't be used when cross compiling for ARM targets. Do you have this provider enabled in your project settings? 

    Include paths to standard libraries should be added automatically once you enabled CDT ARM Cross Built-in Compiler settings (provided by GNU MCU Eclipse plugin), but noticed a slight difference in the naming compared to what I have here:  CDT ARM Cross Built-in Compiler settings vs CDT GCC Built-in Compiler settings Cross ARM. Are you using the same plug-in? Suggest to enable the other provider and see if you get the same result (CDT Cross GCC Built-in Compiler Settings).

    Also, try to select the device in the settings tab. Note: Nordic device family must be installed to make device selection available.

    Include folder should appear when the provider is configured correctly:

  • 0 in reply to Vidar Berg

    Hi Vidar,

    I am indeed using the same plug-in. I actually did a clean install of the OS this weekend and just reinstalled Eclipse and all that. Now it also shows CDT ARM Cross Built-in Compiler settings, no idea what was the difference. However, the project still has the same error. What's interesting is that I have another project in the same workspace, with the same configuration (checked everything, section-by-section, tab-by-tab) and that one doesn't have that problem, the symbols and includes get resolved as they should. That project is the bootloader, also using the nRF5 SDK, FYI.

    I checked the device tab and there are none available. Eclipse says that I should install CMSIS packs first. Anyway, the bootloader project doesn't have it either and that one works well.

    My problem is in fact that, in this project, the entries don't get discovered by the provider (in the bootloader project, the CDT ARM Cross GCC Built-in Compiler settings have lots of entries):

    EDIT: I have already modified the provider commands as instructed in the tutorial -> (.*gcc)|(.*[gc]\+\+) for the Output parser and arm-none-eabi-gcc ${FLAGS} ${cross_toolchain_flags} -E -P -v -dD "${INPUTS}" for the Built-in Compiler settings.

  • +1 in reply to Andy

    Hi Andy,

    I have experienced a few cases where the projects settings had to be reset back to the default configuration to make the built-in compiler settings work, but have not been able to find the root cause. 

    Have you tried to enable the CDT Cross GCC Built-in Compiler settings provider instead of CDT ARM Cross GCC Built-in Compiler Settings?  I would suggest to restore project properties back to default, then re-apply the configuration used in the working project if you get the same result with  CDT Cross GCC Built-in Compiler settings.

  • 0 in reply to Vidar Berg

    Hi Vidar,

    thanks for your suggestion! It got fixed!

    The exact steps I followed, in case anyone else has this problem, were:

    • Go to Project Properties -> C/C++ General -> Preprocessor and Include Paths
    • In the Entries tab, choose GNU C, restore defaults and apply
    • In the Providers tab, restore defaults, apply and close
    • Clean and compile the project
    • Go to Project Properties -> C/C++ General -> Preprocessor and Include Paths
    • In the Providers tab, uncheck CDT ARM Cross GCC Built-In Compiler Settings, apply
    • Check CDT GCC Build Output Parser and change the command to (.*gcc)|(.*[gc]\+\+), apply
    • Check CDT GCC Built-In Compiler Settings and change ${COMMAND} for arm-none-eabi-gcc, apply and close
    • Clean and compile the project

    After that, all the entries were discovered and my problem was gone :D Thanks again for your help!

Related
Terms of service