trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: February 2014

Re: [trinity-devel] undefined symbols in all builds

From: "Darrell Anderson" <darrella@...>
Date: Mon, 10 Feb 2014 10:35:39 -0600
>Any other methods?
>You can send a list?

No, because each time I copy what you did in your patch to add 
Q_EXPORT to a different location, yet another new 'undefined 
symbols' message appears. The messages do not all appear at the 
same time in one nice dump.

Reversing commit 2ee14b64 resolves the problem.

Darrell