• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 146 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

PROCESSOR-SDK-AM64X: Uboot build error with gcc: error: unrecognized command-line option ‘-fcanon-prefix-map’; did you mean...

TDA4VM: Error when building u-boot for sk tda4vm

Dashi Cao
Prodigy 60 points

Part Number: TDA4VM

Cannot build U-Boot after upgraded gcc. The build failed with the error:

gcc: error: unrecognized command-line option ‘-fcanon-prefix-map’; did you mean ‘-fmacro-prefix-map=’?
gcc: error: unrecognized command-line option ‘-fcanon-prefix-map’; did you mean ‘-fmacro-prefix-map=’?
error: command '/usr/bin/gcc' failed with exit code 1

Exactly the same issue as https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1555455/processor-sdk-am64x-uboot-build-error-with-gcc-error-unrecognized-command-line-option--fcanon-prefix-map-did-you-mean--fmacro-prefix-map

But the error disappears when some configuration options are removed.

--- /tmp/a72/.config    2025-12-02 08:44:09.440197067 +0800
+++ config.a72    2025-12-02 08:26:17.271401022 +0800
@@ -2377,7 +2377,7 @@
 CONFIG_MKIMAGE_DTC_PATH="dtc"
 CONFIG_TOOLS_CRC32=y
 CONFIG_TOOLS_LIBCRYPTO=y
-CONFIG_TOOLS_KWBIMAGE=y
+# CONFIG_TOOLS_KWBIMAGE is not set
 CONFIG_TOOLS_FIT=y
 CONFIG_TOOLS_FIT_FULL_CHECK=y
 CONFIG_TOOLS_FIT_PRINT=y
@@ -2391,6 +2391,6 @@
 CONFIG_TOOLS_SHA256=y
 CONFIG_TOOLS_SHA384=y
 CONFIG_TOOLS_SHA512=y
-CONFIG_TOOLS_MKEFICAPSULE=y
+# CONFIG_TOOLS_MKEFICAPSULE is not set
 # CONFIG_FSPI_CONF_HEADER is not set
 # CONFIG_TOOLS_MKFWUMDATA is not set

The test result seems all right as for now.

 

Dashi Cao

 

 

  • 0
    TI__Guru**** 167980 points

    Hello,

    Can you try to install the SDK and use the exact compiler version that is used in the SDK?

    Dashi Cao said:
    -CONFIG_TOOLS_KWBIMAGE=y
    +# CONFIG_TOOLS_KWBIMAGE is not set

    Dashi Cao said:
    -CONFIG_TOOLS_MKEFICAPSULE=y
    +# CONFIG_TOOLS_MKEFICAPSULE is not set

    Are the above enabled in the default U-Boot configs? If not then recommend commenting out.

    - Keerthy

  • 0 in reply to Keerthy J
    Prodigy 60 points

    I have not used the tool chain shipped with SDK. But before I upgraded the gcc from 12.x to 15.x, the build has no such errors.

    Both of the CONFIG_* are enabled in both j721e_sk_r5_defconfig and j721e_sk_a72_defconfig. So I'd like to know if it is ok to remove them. It seems that all is right as for now in my case.

    Dashi Cao

  • 0 in reply to Dashi Cao
    TI__Guru**** 167980 points

    Hello Dashi Cao,

    Could you double check once with SDK compiler version? Those errors should not be seen. Recommend to use the SDK tested compiler version.

    - Keerthy