On Sat, Jun 15, 2013 at 1:17 PM, Thijs Alkemade <th...@xnyhps.nl> wrote: > > On 15 jun. 2013, at 18:37, Jonathan Rice wrote: >> Thijs, >> >> I've been looking at the Sametime issue >> (https://trac.adium.im/ticket/16345) over the last few days, and I'd >> really appreciate your input. >> >> I've found Sametime stopped working in the 1.5.5 branch with the >> upgrade to libpurple 2.7.0 and corresponding dependency updates. >> >> There's nothing in libpurple 2.7.0 that really messes with Sametime, >> except for the one commit you mentioned in the ticket. I reverted that >> change and still couldn't connect. >> >> Something interesting, I checked out the last working version of Adium >> (8dd0d808e092) and rebuilt the dependencies using the exact same >> version of libpurple it was already using (2.10.5r590f15aee045), >> and....Sametime wouldn't connect. Working code, rebuilt with the same >> libpurple, using whatever dependencies are in brew, doesn't work. >> Since none of the Adium or libpurple code was different, to me that >> indicates a possible dependency problem. >> >> Another dependency indicator is I'm running one of the meanwhile >> samples and it's failing to connect with the same error code. >> >> I tried tweaking brew and rebuilding everything with the older >> dependencies, but no luck. Perhaps some build options have changed >> since they were built last? >> >> Is it possible to know exactly what Adium brew revision the older >> dependencies in 8dd0d808e092 were built from ? Or do I just check the >> dates and find something close (sometime September 2012)? Also, do you >> remember what the build commands were before the frameworks stuff was >> added? >> >> >> WORKS: 5345:8dd0d808e092 Backport 87047401414b for #16101. References >> #16101 (using libpurple 2.10.5r590f15aee045) >> >> ...broken builds in between... >> >> NOT WORKING: 5360:d4826d930b65 libffi and libintl were not >> install_name_toolized properly in these frameworks >> >> Thanks, >> Jonathan >> > > Hi Jonathan, > > I think the revision where 8dd0d808e092's libpurple got added was > 24a33c054027. From timestamps and commit messages I'm quite sure this was > https://github.com/adium/homebrew/commit/c5a8f439287f95f7e42c37dc864f202b32479b75. > > I just noticed the actual Homebrew version used to build the dependencies in > 1.5.6 was never committed by me, I just did so here: > https://github.com/adium/homebrew/commit/289f0e62181658f3c9ae9c609a9b314de1393cac. > Sorry if that wasted some of your effort =/ > > The old way of building dependencies was using build.sh from /Dependencies, > though I don't think it'll be easy getting this to work. For example, I don't > think Pidgin's migration to hg has been applied. > > Thijs > >
Thijs, I've narrowed the issue down to the meanwhile library. Since it doesn't have any code changes, it must just be a build issue. (I built each dependency from the homebrew revision you gave and swapped them into the last working version of Adium. It all worked fine until I swapped in meanwhile. Then it displayed the issue.) I agree most of 8dd0d808e092's dependencies seem to have been built from the homebrew revision you gave (~Oct 16). However, if you look at meanwhile, it was built Sept 23. Any possibility you could've built meanwhile differently? - I built meanwhile with each of the revisions around that time, but none of them worked. - I added a missing configure arg (--enable-shared) that was present in the old-style build. No luck. - I don't think it could've been built the old way, because I see that it's linked against a newer glib (2.32.4). - It's also strange that even though it was built Sept 23, it's linked against other library versions that weren't in homebrew at that time. For example, in Sept, glib 2.20.5 was in brew, but the Sept meanwhile is linked against 2.32.4. You must've had the newer glib configured locally? Hopefully you can provide some insight. I'm going to start digging into the actual login message meanwhile sends and see what might be different. Thanks, Jonathan
