Hey Tor,
2014-04-07 13:52 GMT+02:00 Tor Arne Fallingen <fallin...@gmail.com>:
> Hey everyone,
>
> Now Ive been working for a while on a Wt dbo backend class for a project,
> but the past week its not been touched, and then as Im trying to start
> editing it again, I start out trying just trying to run my test program
> again, as this was working fine before I put it aside last time. However,
> life is not easy, this time I get an error saying:
>
> dyld: Library not loaded: /usr/local/lib/libboost_system-mt.dylib
> Referenced from: /usr/local/opt/boost/lib/libboost_thread-mt.dylib
> Reason: image not found
>
This doesn't sound good at all. Your /usr/local/opt/boost/lib version
should not be referencing itself boost libraries from another location.
This I can only explain if you have been moving your boost library after it
was installed.
But this is trying to reverse engineer things that have been doing on your
end; in the end, the installation, if done correctly, will not take a lot
of time and does not involve many steps, so I believe you should simply
develop a single procedure that works, from scratch, instead of repairing a
broken setup.
Im on my Macbook, and I haven't touched either my boost or Wt install since
> I got it all installed and working. Im almost afraid to say this, but the
> boost folder in my use/local/include was gone when I started looking into
> stuff. And I reinstalled boost, but I do get a few errors during the
> install, and I have searched, and I dont find the lib
> boost_system-mt.dylib, I have no <<-mt>> dylibs, but I have the ordinary
> ones. Im still on Wt-3.3.2-rc2 on this Mac, and Id be really grateful if
> anyone has any tips for me. Ill paste all the errors from my install into
> the bottom of this mail. I just dont see why its searching for lib
> boost_system or lib boost_thread at all, they are not in my .pro file:
>
Despite it's nice appearance, Mac OSX isn't the easiest platform for C++
development since it's in a migration from gcc to CLang. There are three
toolchains on your macbook (and perhaps more if you're using portage or
homebrew):
- pure GNU: g++ with libstdc++
- LLVM/GNU: g++ front-end with LLVM backend with libstdc++
- CLANG/GNU: CLang with libstdc++
- pure CLANG: CLang with libc++
The latter is definitely the toolchain that the mac osx platform is moving
to, and is also the one that works best (in our experience). No matter what
toolchain you chose, however, you should not mix them.
Thus if you use the latter toolchain (as we do in our Mac OSX installation
guide) then you should make sure that boost, Wt and your own application is
being built using that toolchain.
If you do things wrong, you'll get all kinds of strange issues ...
> ./boost/atomic/detail/gcc-atomic.hpp:961:64: error: no matching
> constructor for initialization of 'storage_type' (aka
> 'boost::atomics::detail::storage128_type')
> explicit base_atomic(value_type const& v) BOOST_NOEXCEPT : v_(0)
> ^ ~
>
... like these.
Regards,
koen
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
witty-interest mailing list
witty-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/witty-interest
