Sorry for the late reply. I didn't run configure --with-pgm. I was expecting
udp to mean unicast UDP.
On a related note, is there any plan to support unreliable multicast?
Chris
On Mar 3, 2010, at 4:53 AM, Martin Lucina wrote:
> sust...@250bpm.com 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.
>
> -mato
_______________________________________________
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
