* Sven Neumann <s.neum...@raumfeld.com> schrieb: > > They still use the conceptionally broken AC_TRY_RUN(). [1] > > So, the chain is broken, everything beyond that cannot be built. > > Period. > > That is really a problem in your build environment then.
No, it's a general misdesign. In 99.99% totally unncessary. > You can easily feed the expected result of AC_TRY_RUN tests > to the configure script so that it will not attempt to run > the tests. Easily ?! By analyzing the configure.in and all related m4 files, watch out for the AC_TRY_RUN calls, find out what they really should do, tweak them to produce the appropriate result - for each specific target - w/o trying to run anything. For each single package in all required versions. Basicly this means maintaining full downstream-branches, one per package+version+target. That totally undermines the whole purpose of autoconf. > Pretty much any decent build environment out there has > support to build glib2. Which of those are doing clean crosscompiling ? How much work to the package maintainers have to spend into each single upstream release, per individual target configuration ? cu -- ---------------------------------------------------------------------- Enrico Weigelt, metux IT service -- http://www.metux.de/ phone: +49 36207 519931 email: weig...@metux.de mobile: +49 151 27565287 icq: 210169427 skype: nekrad666 ---------------------------------------------------------------------- Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme ---------------------------------------------------------------------- _______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
