Here is the output; libgcc_s.so.1 GCC_4.2.0 GCC_3.3 GCC_3.0
Im currently trying to rebuild libdirac with 4.1.2 but i am struggling as it is not picking up on my local version of liborc. To be honest I really dont know enough about compiling and linking. I normally just use qmake to generate my make files. Would it be better then to just use g++ without make to run it? Regards, Jack Straw On 30 March 2011 14:29, Peter Pearson <[email protected]> wrote: > On 30/03/11 13:18, Jack Straw wrote: > >> Thanks Peter. >> >> I think I might be going about this the wrong way possibly though now. >> >> This is what I was struggling with; >> >> When i try to use the opencv library I get this error on loading in the >> plugin (it does compile without error and works when i'm not trying to >> use it); >> >> /usr/local/Nuke6.1v1/libstdc++.so.6: version `GLIBCXX_3.4.11' not found >> (required by /usr/lib/libdirac_encoder.so.0) >> >> >> Now if I preload using this, just because I saw the same error in one of >> the threads here and that was the fix; >> >> >> export LD_PRELOAD=/usr/lib64/libstdc++.so.6:/lib64/libgcc_s.so.1 >> >> >> I get past that error and get this one; >> >> /usr/lib/libavcodec.so.52: symbol av_random_init, version LIBAVUTIL_49 >> not defined in file libavutil.so.49 with link time reference >> >> >> Now I dont know how to progress past this. >> > > Hi, > > It probably is a compiler incompatibility issue somewhere... > > Can you do a: > > strings /usr/lib64/libstdc++.so.6 | grep -i gcc > > The one bundled with Nuke is built with gcc 3.3, whereas I'm guessing the > one on your system in /usr/lib64/ is more modern (mine on Ubuntu is 4.2) so > I'd say they are ABI incompatible. > > It looks like the first error above is because your > /usr/lib/libdirac_encoder.so.0 was built with gcc 3.4 which isn't compatible > with the libstdc++ we bundle that was built with 3.3. > > The second error looks like you're trying to link with a newer libavcodec > on your system - I'd try linking against the .49 one we bundle with Nuke, > but admittedly, you'd probably want a later version than that. > > So you'll have to work out what's dynamically linking with what - might be > a case of ldd'ing every file you're linking to in order to work out where > they're resolving... > > As a last resort, you could always try statically linking, but that might > introduce duplicate symbol issues... > > Regards, > Peter > > -- > Peter Pearson, Software Engineer > The Foundry, 6th Floor, The Communications Building, > 48 Leicester Square, London, UK, WC2H 7LT > Tel: +44 (0)20 7434 0449 - Fax: +44 (0)20 7434 1550 > Web: www.thefoundry.co.uk > > The Foundry Visionmongers Ltd. > Registered in England and Wales No: 4642027 > _______________________________________________ > Nuke-dev mailing list > [email protected] > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev >
_______________________________________________ Nuke-dev mailing list [email protected] http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
