Michal Klocek wrote: > might want to check what actually returns -I/opt/local/include/glib-2.0 > -I/opt/local/lib/glib-2.0/include -I/opt/local/include. A good starting > point might be glib-2.0.pc file (or simply run pkg-config --cflags > glib-2.0)
Yeah, that'd be the culprit, or a culprit. Question is what to do about that, other than making sure no conflicting headers exist wherever they shouldn't be, during the build. It also doesn't tell us why the openssl headers from /usr/include/openssl do NOT cause the same problem as the newer ones in /opt/local/include/openssl . I don't see any options to exclude the usual system include directories. R. _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
