Below was comparing suse131_32_xeyes on two -current/amd64 machines, one with suse 13.1 packages , the other suse 13.2. suse131_xeyes works on 13.2 => this seems to be a 32 vs 64 bit linux emulation problem...
Cheers, Patrick On Tue, Jun 02, 2015 at 02:11:40PM +0100, Patrick Welche wrote: > My attempt at updating pkgsrc suse to 13.2 > > http://mail-index.netbsd.org/pkgsrc-users/2015/04/20/msg021432.html > > is failing because X programs return "Resource temporarily unavailable". > > When running xeyes, I see that suse 13.1 calls recv() whereas suse 13.2 > calls recvmsg(): > > suse 13.1: > > 9353 9353 xeyes CALL socketcall(0xa,0xbffff710) > 9353 9353 xeyes MISC linux32/recv: 16, > 03000000682f05080010000000000000 > 9353 9353 xeyes MISC msghdr: [name=0x0, namelen=2151258043, > iov=0xfffffe8040d67d88, iovlen=1, control=0x0, controllen=1087798824, flags=0] > 9353 9353 xeyes GIO fd 3 read 32 bytes > "\^A\0\^A\0\0\0\0\0\^A\M^N\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0" > > suse 13.2: > > 17133 17133 xeyes CALL socketcall(0x11,0xbffff610) > 17133 17133 xeyes MISC linux32/recvmsg: 12, 0300000064f6ffbf00000000 > 17133 17133 xeyes MISC msghdr: [name=0x0, namelen=3221223004, > iov=0x4cbffff680, iovlen=0, control=0xfbc113dcfbfe5cf7, controllen=3, > flags=4000000] > 17133 17133 xeyes MISC msghdr: [name=0x0, namelen=0, iov=0x4cbffff680, > iovlen=0, control=0xfbc113dcfbfe5cf7, controllen=0, flags=0] > 17133 17133 xeyes RET socketcall 0 > 17133 17133 xeyes CALL netbsd32_write(2,0xbfffd290,0x4d) > 17133 17133 xeyes GIO fd 2 wrote 77 bytes > "XIO: fatal IO error 11 (Resource temporarily unavailable) on X > server\ > \":0\"\r\n" > > iovlen=0? > linux_sys_recvmsg() trouble? > Commit trivial xeyes pkg? > Thoughts? > > Cheers, > > Patrick
