** Changed in: enblend
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1023037
Title:
Enblend fails to build with boost 1.50
Status in Enblend:
Fi
** Changed in: enblend
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1023037
Title:
Enblend fails to build with boost 1.50
Status in Enblend:
Fix Com
Grr, 'w' key sticks:
it now builds with boost-1.50 using --with-boost-filesystem
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1023037
Title:
Enblend fails to build with boost 1.50
Status in
Ok, it no builds with boost-1.50 using --with-boost-filesystem
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1023037
Title:
Enblend fails to build with boost 1.50
Status in Enblend:
Triaged
I see this same problem on fedora f18 which has boost-1.50 (this is with
the fedora boost-devel, boost-system and boost-filesystem packages
installed amongst others):
checking boost/filesystem.hpp usability... yes
checking boost/filesystem.hpp presence... yes
checking for boost/filesystem
It's easy to patch enblend-enfuse-4.0 as such for boost 1.50 but I have not
enough knowledge about the ins and outs with the MacPorts Portfile right now.
I patched the enblend Portfile and added the patch but somehow it still doesn't
work. I have to ask one of the Macports gurus how patching logi
I said "but I can determine it".
I meant of course "but I can't determine it".
sorry.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1023037
Title:
Enblend fails to build with boost 1.50
Statu
I have forwarderd the problem to Harry an Ingemar.
With respect to your problem with "--with-boost-filesystem":
I was (implicitely - as almost always) talking about the current
head of development in the hg repo. There, both Boost
libs get added with the "--with-boost-filesystem" option.
Anyhow,
Thanks.
I'm not familiar with what the practice is here, would it be more
appropriate to email Harry and Ingemar directly, or should I just
subscribe them to this bug? In either case could you forward it along,
since I don't have their email addresses.
Incidentally, the "--with-boost-filesystem"
I don't have access to OSX, so you might want to ask
Harry van der Wolf or Ingemar Bergmark, who are the
Mac-builders in our team.
As you confirm that adding "-lboost_filesystem -lboost_system"
fixes your problem, you can also pass option
--with-boost-filesystem
to ./configure. It forces the
FYI - Build is successful when "-lboost_filesystem -lboost_system" is
added to the LIBS variable in src/Makefile.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1023037
Title:
Enblend fails to
I'm using the configure script that comes with the source code, and am
running OS X. The configure script doesn't show any extra libraries
requested. In case it's helpful, this is everything the configure
script reports at the end:
enblend-enfuse now configured for i386-apple-darwin11.4.0
So
The linker invocation looks sick. It lacks (at least)
-lboost_filesystem -lboost_system
Presumably, the error msg comes from a missing
libboost_system. This is a configuration problem.
Are you using GNU's configure or cmake?
At the end of its run configure(1) tells you, whether
it has request
13 matches
Mail list logo
