Martin Lucina wrote: > [email protected] said: >> Interestingly, the configure silently switches off PGM support rather >> than complaining. The build system contains the code that should complain: >> >> case "${host_os}" in >> *linux*|*mingw32*|*solaris*) >> ;; >> *) >> AC_MSG_ERROR([the PGM extension is not supported on system >> ${host_os}.]) >> ;; >> esac > > Eh? It shouldn't do that, it should fail if you ask for --with-pgm. > >> Chris, do you see the error message in your configure log? > > I suspect Chris has assumed that the "udp" transport means some form of > unicast UDP, and did not actually build with --with-pgm. > > This is why I suggested some time ago to rename the "udp" transport to > "pgm+udp" to better reflect that it's actually PGM encapsulated in UDP. > > Martin, what do you think about this suggestion? You didn't reply when I > last mentioned it.
"pgm+udp" is plain ugly and pain to use. If needed we can change it to "epgm" = encapuslated PGM, however, given there's no real UDP transport, "udp" seems to be sufficient. Note that in exactly the same way "tcp" is not raw TCP, rather it's a simple message delimiting protocol on top of TCP. Martin _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
