* Robert Pearce <rob@xxxxxxxxxxxxxxxxxxxx> wrote: > It's not "glib make", it's the configure script. In order to confirm > whether glib can use a POSIX compliant getgrgid_r the configure script > has to build and run a test program to check for compliance. For most > things it's enough to compile the test, but for some compliance checks > the program must actually be run on the target system. That's rather > hard for configure to do when cross-compiling. That's silly! If the function is there and does not behave the specified way, the providing package (in this case libc) is simply broken and has to be fixed. It's that simple. *If* you really want some sanity test, why aren't they run in the 'make test' pass ? For the 'make test' it is clear that it has to run on the actual target, build and install has to run properly on any other system (w/ proper cross-toolchain). Making silly assumptions like that the building system is identical with the target completely breaks this. cu -- ---------------------------------------------------------------------- Enrico Weigelt, metux IT service -- http://www.metux.de/ phone: +49 36207 519931 email: weigelt@xxxxxxxx mobile: +49 151 27565287 icq: 210169427 skype: nekrad666 ---------------------------------------------------------------------- Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme ---------------------------------------------------------------------- _______________________________________________ gtk-list mailing list gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
