colleague hands me the following curiosity ... approximately morty-based build, wherein ntp_4.2.8p10 has a bbappend file which contains (among other things) the line:
DEPENDS += "autogen-native perl-native" i'm always nervous when a bbappend file just adds new build dependencies but, apparently, this has worked fine all this time, as there was an autogen-native recipe back then. dragging this recipe forward, unsurprisingly, it fails as there is no autogen-native recipe anymore. so i'm just going to drop that dependency, while poking aorund to figure out why it was ever needed in the first place. and apparently, this is not the first time that a legacy recipe which contained an autogen-native DEPENDS line has caused problems, so what is the deal with autogen-native? clearly, i need to get rid of that, but is there an explanation as to how that migration was done elsewhere? i'm about to find out what happens when i go that, while going from ntp 4.2.8p10 to 4.2.8p13, and seeing what else breaks. rday
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#147056): https://lists.openembedded.org/g/openembedded-core/message/147056 Mute This Topic: https://lists.openembedded.org/mt/80000363/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
