Editing User talk:Genuinelucifer
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 128: | Line 128: | ||
At this moment building of boost-python with 64 bit tool chain fails at final link stage | At this moment building of boost-python with 64 bit tool chain fails at final link stage. Using 32 bit octave 4.1.0+ for windows build of boost_python was successful. | ||
So far octave-4.1.0+ 32 bit has been used. | |||
==== Build Pytave | |||
==== Build Pytave (Procedure and current state) ==== | |||
# Open octave-cli.exe | # Open octave-cli.exe | ||
Line 143: | Line 146: | ||
To sum up, Tatsuro has built 32 bit version of octave and used it to build libboost-python with the option ''link=static,shared'' and has successfully got the configure step done. But in the ''make'' step he is getting some undefined symbol errors for ''__imp__'' symbols. | To sum up, Tatsuro has built 32 bit version of octave and used it to build libboost-python with the option ''link=static,shared'' and has successfully got the configure step done. But in the ''make'' step he is getting some undefined symbol errors for ''__imp__'' symbols. | ||
=== Summary === | === Summary === | ||
Line 198: | Line 200: | ||
=== Conclusion === | === Conclusion === | ||
To quote Tatsuro ''A lot of _imp__ symbols errors are detected because no _imp__(symbol)s exist in object files. While object files libboost_python for threading-multi have _imp__(symbol)s in their object files. Boost does not show full compiling states. Therefore I do not know what libboost is to do.'' | |||
I too have googled extensively but haven't gotten to any solution for this problem. | I too have googled extensively but haven't gotten to any solution for this problem. |