Yeah, I didn't trace back where that happened. Might be that my specific version of SWIG tries to link against that destructor's symbol. I really can't tell. Still, technically, Sylvain is right, such errors can hit you late when runtime dynamically loads/links.
Best regards, Marcus On 06.07.2016 11:04, Tom Early wrote: > When Marcus build my OOT, he encountered both a "was not declared in > this scope" comp error and an undefined reference linking error. (See > his previous post in this discussion.) > > I did not encounter any errors or warnings building the exact same > source. I'm trying to understand why. > > On 07/05/2016 01:06 AM, Sylvain Munaut wrote: >> Hi, >> >>> Do you have any idea why my system did not complain AT ALL when >>> building the >>> syncing branch? I am using ubuntu 16.04 with the apt-installed grc >>> (3.7.9). >>> Do I have some config screwed up somewhere? >> No, that's expected. >> >> GR modules are libraries and as so the linking process will accept >> undefined symbols, and just expect them to be present when the .so is >> effectively loaded at runtime. >> >> Cheers, >> >> Sylvain >> >> > > > _______________________________________________ > Discuss-gnuradio mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio _______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
