On 7/27/14, LRN <lrn1...@gmail.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 27.07.2014 1:49, Ozkan Sezer wrote: >> On 7/27/14, LRN <lrn1...@gmail.com> wrote: [...] >>> (2013-09-08 22:41:48) LRN: meanwhile - go ahead, fix ws2bth.h (add >>> #pragma pack(push, 1), #pragma pack(pop)) >>> >>> >>> Apparently, i forgot to report this. >>> >> >> Seems like v3.x and trunk version of ws2bth.h already has byte-packing >> via >> the pshpack1.h and poppack.h includes. The v2.x version does need fixing; >> just did that, here: >> http://sourceforge.net/p/mingw-w64/mingw-w64/ci/8790e7cb674793a31f023d8fd3d16f8ed8dbde4d/ >> >> > 2014-07-26 22:03:20 +0400 RyanGlScott: I'm having trouble running > Bluetooth-related code on MinGW-w64. It does work on MSVC. > http://lpaste.net/108193 > 2014-07-26 22:04:16 +0400 RyanGlScott: bind() fails, giving me the > error > code 10049 (WSAEADDRNOTAVAIL). > 2014-07-26 22:14:52 +0400 lh_mouse: RyanGlScott, try #define > WIN_VER > 0x0601 > #define _WIN32_WINNT 0x0601 > 2014-07-26 22:17:34 +0400 RyanGlScott: lh_mouse: That didn't seem to > fix > it, although it warned that _WIN32_WINNT was redefined. > 2014-07-26 22:18:03 +0400 lh_mouse: RyanGlScott, define them before > #include'ing any headers. > 2014-07-26 22:18:19 +0400 RyanGlScott: lh_mouse: Oh, duh. Sorry, I'll > try > again. > 2014-07-26 22:18:54 +0400 RyanGlScott: lh_mouse: Hm, no difference. > 2014-07-26 22:20:03 +0400 lh_mouse: No need to apologize. Is it > the 42nd > line that you get an error? > 2014-07-26 22:20:44 +0400 RyanGlScott: Yeah, the output is "Binding > failed", "errno 10049" > 2014-07-26 22:31:25 +0400 lh_mouse: I don't know why. But I > suggest you > dump the binary contents of SOCKADDR_BTH of the two programs and check > whether they are the same. > 2014-07-26 22:31:49 +0400 RyanGlScott: lh_mouse: Good idea. I'll check > that > out. > 2014-07-26 22:47:55 +0400 RyanGlScott: What's the best way of doing a > binary dump in Windows? objdump.exe -S isn't revealing much to me. > 2014-07-26 22:51:18 +0400 lh_mouse: RyanGlScott, I meant the > contents of > that SOCKADDR_BTH you defined in your code. > 2014-07-26 22:54:18 +0400 RyanGlScott: lh_mouse: I'm not sure what the > best > way of comparing them is. Should I just make a simpler program containing > only the SOCKADDR_BTH parts of compare their objdumps? > 2014-07-26 23:11:15 +0400 lh_mouse: RyanGlScott, unsigned char *p = > &blah; > for(size_t i = 0; i < sizeof(blah); ++i){ printf("%02X ", *(p++)); } > 2014-07-26 23:14:37 +0400 RyanGlScott: lh_mouse: Is "&blah" > representing > the SOCKADDR_BTH address? And is there a reason to make it an unsigned char > pointer type? > 2014-07-26 23:17:58 +0400 lh_mouse: It should be that address > variable > defined on line 35 in your code. > 2014-07-26 23:18:27 +0400 lh_mouse: Just print all bytes of it in > hex. > 2014-07-26 23:20:50 +0400 RyanGlScott: Alright, the for the MinGW-w64 > version: 20 00 2A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > 00 > 00 00 00 00 00 00 00 00 00 FF FF FF FF 00 00 00 00 > 2014-07-26 23:21:08 +0400 RyanGlScott: And for the MSVC version: 20 > 00 00 > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FF FF > FF FF > 2014-07-26 23:23:54 +0400 RyanGlScott: Curiously, the 2A changes every > time > I run the MinGW-w64 version. > 2014-07-26 23:25:58 +0400 lh_mouse: That doesn't matter, it is one > of the > padding bytes after addressFamily. >
Can you translate: does the commit on v2.x (or using v3.x branch) fix the issue, or not? -- O.S. ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public