Christian Grothoff <[email protected]> writes: > This should have been self-fixing if you ran './bootstrap' to generate > configure. Next time you see this (kind of) message, just re-run > ./bootstrap.
Hm, I think I need to revisit how this is done by my packages, to exclude this behavior which might lead to a 'die' in the build process. Especially on gentoo, where moving gnunet from eapi 5 to the new eapi 6 gets hard and needs an entirely new build structure in the ebuild file. > However, I also should have just pushed the latest POTFILES.in manually. > So fixed in SVN 37009. > > -Christian Thanks! Would you (or someone else) know if there are tested to be unsupported (non functional) plattforms of GNUnet? Gentoo can support those to build on: alpha amd64 arm arm 64 hppa ia64 mips ppc ppc64 sh sparc x86 x86-fbsd amd64-linux ia64-linux x86-linux It would help for the later testings team to have some input which ones to exclude, I can only test a limited set on the hardware I have here. > On 04/10/2016 04:51 AM, Nils Gillmann wrote: >> Hi Christian, >> >> thanks for the quick fix. >> >> Currently I'm trying to finish the work of lynX and myself and >> try to get gnunet, gnunet-gtk and gnurl into gentoo's >> portage. That's why I run and test it very much, now with the >> latest push I ran into something where I am not sure if this it >> is related or not, paste is here: >> >> https://bpaste.net/raw/01e184d9b55f >> >> build breaks at "no rule to make target >> '../src/sensordashboard/gnunet-sensordashboard.c' needed by >> 'gnunet.pot-update" > > _______________________________________________ > GNUnet-developers mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/gnunet-developers -- ng0 _______________________________________________ GNUnet-developers mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnunet-developers
