make menuconfig doesn't register changes in toolchain prefix

[eugenio]

I tried several times to edit by make menuconfig the toolchain prefix for arm but once i run make:

[GEN] /home/eugenio/progetti/stm32/tmp/ldfile.lds
/bin/bash: arm-ncrmnt-eabi-gcc: comando non trovato
/home/eugenio/progetti/stm32/antares/src/arch/arm/stm32/arch.mk:76: set di istruzioni per l'obiettivo "/home/eugenio/progetti/stm32/tmp/ldfile.lds" non riuscito
make: *** [/home/eugenio/progetti/stm32/tmp/ldfile.lds] Errore 127
eugenio@debian-laptop:~/progetti/stm32$

[nekromant]

You need to set the proper toolchain prefix in "Toolchain settings" and save the config. (Make sure your changes are saved in .config ). If this doesn't work for you, please provide some more info:

1. navigate to "buildsystem tweeks" and enable verbose output.
2. Provide logs for running menuconfig and actual build.
3. Tell me what system (linux/osx) you are running and what example you started with, so that I can try to reproduce this issue on my side (so far everything works for me)

Thanks.

[eugenio]

Sorry, I didn't provide any details on my build system.
I'm on debian lInux Jessie (testing).
I found the source of the problem: multiple .config files, removing all but one did it.
You can mark as solved

[nekromant]

Just interesting, how did you manage to do that? Antares just uses .config in your project top directory - any other .config files should be ignored.

[eugenio]

Actually there were multiple .config files in the top directory, but only the oldest one was read I think.

[nekromant]

Can you reproduce this and post the tarball somewhere?
Upon changing the config kconfig and tools save the old config to .config.old. But it should only use .config is all circumstances. If not - it's likely a bug.
There may have also been a permission problem e.g. .config was not writeable by the user who ran menuconfig.

[eugenio]

Sorry i didn't explain myself correctly, i meant that there were multiple files with suffix .config but with variable prefix.
I think that the buildsystem behaves correctly because only the file with no prefix is used. however i'll host the tarball on my dropbox if necessary.

[eugenio]

i did a clean initialization and all compiled well. it's likely that some misconfiguration was left from my previous attempt to set up the system.

[nekromant]

Okay, closing it for now. If you manage to find out what went wrong - please reopen,