Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Overriding recipe warnings on "make build" when FWUPDATE_* equals OTA_* variables #16

Open
htgoebel opened this issue May 30, 2020 · 1 comment

Comments

@htgoebel
Copy link

When running "make install", I get these warnings:

Makefile:88: warning: overriding recipe for target 'updates/19.11.2-sibon-24df0be9-ota.zip'
Makefile:82: warning: ignoring old recipe for target 'updates/19.11.2-sibon-24df0be9-ota.zip'

@Roboe
Copy link
Member

Roboe commented Aug 13, 2022

@htgoebel Thanks for bringing this up.

This happens because the two OTA upgrade packages the script need are the same at the time (here and here). This makes two make targets at the lines you mention to have the same filename, so make needs to override one of them.

Since it's essentially the same recipe and the package satisfies the two different uses in this case (sourcing the Edify binary and the different firmware images), I'm sure there's no functional problem at all and the message can be discarded. I'm guessing the warning messages don't impede the Makefile running fine and generating the modem ZIP correctly, though; if that's the case, please indicate your OS and make versions.

Any other way, it's an aesthetic problem. I don't have the immediate knowledge or time to solve it, but if anyone does, we'll apreciate a proposition to fix it. Just reply here!

@Roboe Roboe changed the title Warnings on "make install" Overriding recipe warnings on "make install" when FWUPDATE_* equals OTA_* variables Aug 13, 2022
@Roboe Roboe changed the title Overriding recipe warnings on "make install" when FWUPDATE_* equals OTA_* variables Overriding recipe warnings on "make build" when FWUPDATE_* equals OTA_* variables Aug 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants