I messed with the order a whole bunch and it didn't seem to matter. ?The rest of Gtest seemed to link fine as well.
On Thu, 2016-04-28 at 09:16 -0700, Thiago Macieira wrote: > On quinta-feira, 28 de abril de 2016 08:40:18 PDT Keane, Erich wrote: > > Thiago- > > > > This is the exact issue I was having a few days ago, where > > rebuilding > > GTest was the solution.??GetBoolAssertionFailureMessage is inside > > the > > libgtest.??The linking options LOOKED right to me when I debugged, > > it > > was properly finding the correct libgtest.a (Confirmed by deleting > > the > > one I expected it to pick up, and seeing that the link error was > > different), but this symbol wasn't in it correctly. > > > > Could some versions of our gtest have incompletely built .a > > files???I > > rebuilt gtest (deleted the .a files, then did a 'make' in the gtest > > directory) to fix mine, but no idea if that would fix Joey's. > > Wait, .a? > > Then there's another weird and oft-forgotten problem rearing its ugly > head:? > the order in which the libraries are listed matters. Make sure that > -lgtest? > appears on the command-line after caprotocolmessagetest.o. > > Or build GTest as a shared library. >
