On my Debian Trixie build environment, OpenWrt v24.10.5, after clean build environment 'git clear -dfx' I still see the following messages on:
$ ./scripts/feeds install -a
WARNING: Makefile 'package/feeds/packages/exim/Makefile' has a dependency on 'libcrypt-compat', which does not exist
WARNING: Makefile 'package/feeds/packages/exim/Makefile' has a dependency on 'libcrypt-compat', which does not exist
WARNING: Makefile 'package/feeds/packages/exim/Makefile' has a dependency on 'libcrypt-compat', which does not exist
WARNING: Makefile 'package/feeds/packages/exim/Makefile' has a dependency on 'libcrypt-compat', which does not exist
WARNING: Makefile 'package/feeds/packages/onionshare-cli/Makefile' has a dependency on 'python3-pysocks', which does not exist
WARNING: Makefile 'package/feeds/packages/onionshare-cli/Makefile' has a dependency on 'python3-unidecode', which does not exist
WARNING: Makefile 'package/feeds/packages/python-zope-event/Makefile' has a build dependency on 'python-setuptools/host', which does not exist
WARNING: Makefile 'package/feeds/packages/python-zope-interface/Makefile' has a build dependency on 'python-setuptools/host', which does not exist
Installing all packages from feed packages.
Installing all packages from feed luci.
Installing all packages from feed routing.
Installing all packages from feed telephony.
These messages are also on following commands: make defconfig, make prereq, make menuconfig and make itself.
Do I miss some Debian packages? Building v24.10.4 went without these messages.
Those are warnings about missing package dependencies, not errors.
Unless you want to build exim, onionshare-cli, python-zope-event or python-zope-interface (and neither of these are particularly common for a typical router), those bear no consequence for you at all and are safe to ignore. Yes those may[*] be errors in the packaging and declared package dependencies of those packages - and if you actually do you either of those (unlikely), you may want to care, otherwise how about a nice game of chess?
--
[*] in some cases these omissions might be 'intentional', in the sense of optional build dependencies which aren't necessary for a normal build, but may be wanted for full-featured builds for special purposes (traditionally PAM dependencies were such a case, unfulfilled within the base feed, only offered via packages).
That would imply that you've selected those packages to be built in the first place, which you really shouldn't (unless you really want to), as it takes huge amounts of disk space, RAM and CPU cycles to build 'useless' faff. If you do your own local builds, it's rarely advisable to build everything and the kitchen sink - unless you want to provide full-featured (community) builds with full matching package repositories (you can do that, but do you really want to?).
Thanks so far for the info.
I had the same kind of warnings before (sometimes). But most of the time they went away after a second run of './scripts/feeds install -a'.
Not this time. And normally on a branch change, not on a version change of OpenWrt.
The build of OpenWrt v24.10.5 went OK, so I'll close this item.