25 Jul
2010
25 Jul
'10
5:28 p.m.
On 25/07/10 19:15, Steven Watanabe wrote: > AMDG Thank you for the answer, see below. > Eugen Dedu wrote: >> We compile ekiga for windows and boost signals is one of its >> dependencies, so we need to compile it for windows. I use gcc-mingw32 >> from debian unstable (gcc configured for mingw, version 4.4.4-0.1) and >> I do like this: >> - download boost 1.43.0 >> - echo "using gcc : : i586-mingw32msvc-gcc : ;" >> >$(BOOST_DIR)/user-config.jam >> - cd $(BOOST_DIR); ./bjam $(confboost) >>>> I have discovered that the link can proceed if I do: >> - echo "using gcc : : i586-mingw32msvc-g++ : ;" >> >$(BOOST_DIR)/user-config.jam >> - cd $(BOOST_DIR); ./bjam $(confboost) >> >> i.e. compile again after changing gcc to g++, but of course this is a >> workaround. How to solve it properly? > > No. Using g++ is the correct solution. Shame on me. I tried also g++ but compiled with other flags, and the errors were surely in other place. So it works with g++, thank you. >> Second, I execute afterwards: >> - cd $(BOOST_DIR); ./bjam $(confboost) install >> 2. Is $(confboost) still needed or not for install? > > Yes. You'd actually be better off just running the install. > It will build everything it needs. Ok. >> 3. This command does nothing for about 1 minute 30 secs (I thought at >> the beginning that it simply does not work, fortunately I let it >> execute more than 10 seconds to see what happens), and only afterwards >> copy the files. > > This is normal. Is it normal to wait for about 100 seconds?! >> Executing through strace shows many lines like this: >> brk(0x6116000) = 0x6116000 >> and these lines take almost all the installation time. -- Eugen Dedu