Thread: [Bayes++] Re: [jamboost] bjam use help
Brought to you by:
mistevens
Menu
▾
▴
bayesclasses-general
|
From: Michael S. <Mic...@ep...> - 2005-02-02 07:28:44
|
On Wednesday 02 February 2005 03:18, Rene Rivera wrote:
> Lucas Vickers wrote:
> > I think I need to edit the "/home/poobarr/boost_1_32_0/boost-build.jam"
> > file or the "/home/poobarr/Bayes++/Jamfile.v2" file, but I am confused.
> >
> > Thank you for the development and for your time.
> > Sorry if this is the wrong group but I think this is more of a bjam
> > issue than boost issue.
>
> Your are mostly at the right place.. In order to really help you though
> we'd need to know what you are using to build the Bayes++ project. From
> your mention of "/home/poobarr/Bayes++/Jamfile.v2" it seems to have a
> BBv2 project. But does it also have a BBv1 "Jamfile"? Are there
> instructions with the Bayes++ project on how to build? Is there a
> Bayes++ group/maintainer you can ask?
Rene seems to have covered most of important stuff already. As the Bayes++
author hopefully I can help also! I have CC'd my reply to the Bayes++ list.
> A few minutes later.. Answering some of my own question after looking up
> the Bayes++ project..
>
> Looks like the newest version is BBv2 only. So at minimum you'll have to
> do "bjam --v2" to get the BBv2 functionality.
Release versions of Bayes++ have Jamfiles for Boost Build version 1 and
version 2. I assume you are using '2003.8-4' which is the latest stable
release. It would be worth trying 'bjam --v2' to see if it works in your
case.
> Since Bayes++ looks like it uses header only Boost libraries you: a)
> don't need to build the Boost libraries that have source, b) it really
> doesn't matter where you put the Boost headers.
I agree with this.
> And looking at the Bayes++/Jamfile.v2 all you should need to set is
> "-sBOOST=/usr/local/include/boost-1_32/".
Bayes++ picks up it's settings from 'BOOST_ROOT' as described in "compiling
the examples".
> PS. It looks like the docs on the Bayes++ web page are out of date.
I double checked. Docs are up to date, they were updated only about a week ago
to match the 2003.8-4 release.
Probably best to continue this discussion on the bayesclasses-general list or
via personal mail.
Michael
--
___________________________________
Michael Stevens Systems Engineering
Navigation Systems, Estimation and
Bayesian Filtering
http://bayesclasses.sf.net
___________________________________
|
|
From: Lucas V. <lvi...@mi...> - 2005-02-03 03:00:49
|
Okay tweaked some and no luck, I am thoroughly confused :) ! I went through chapter 19, did the basic configuration as stated, but could not get the hello example (or any other examples) to compile Thank you for the help, Michael, Rene, and everyone. I appreciate it. ** (topic 1 ) ** Micheal and I thought maybe it's a g++ version issue... but after messing with the boost-build.jam file the errors have changed (see topic 2) g++ version: ------------------ Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2/specs Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --host=i386-redhat-linux --with-system-zlib --enable-__cxa_atexit Thread model: posix gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7) --------------- ** (topic 2) ** configured 'user-config.jam' --- thank you for pointing out the relevant web page Michael (I can be air headed at times :) ) all I see relevant to me is to tell it to use gcc, so I uncommented that tried following chap 19 tried setting boost_root variable in my profile tried making a boost-build.jam file set both of these attempts to the local boost (in /home/poobarr/boost_1_32_0) tried copying the Jamroot file to a 'Jamfile' file for the hell of it. tried compiling the hello example, yielding the following: ------------- /home/poobarr/boost_1_32_0/tools/build/v2/build/targets.jam:794: in object(file-reference)@1.exists rule CHECK_IF_FILE unknown in module object(file-reference)@1. /home/poobarr/boost_1_32_0/tools/build/v2/build/targets.jam:369: in find-really /home/poobarr/boost_1_32_0/tools/build/v2/build/targets.jam:401: in object(project-target)@1.find /home/poobarr/boost_1_32_0/tools/build/v2/build/targets.jam:828: in resolve-reference /home/poobarr/boost_1_32_0/tools/build/v2/build/targets.jam:847: in targets.generate-from-reference /home/poobarr/boost_1_32_0/tools/build/v2/build/targets.jam:1056: in generate-dependencies /home/poobarr/boost_1_32_0/tools/build/v2/build/targets.jam:1097: in object(typed-target)@1.generate /home/poobarr/boost_1_32_0/tools/build/v2/build/targets.jam:750: in generate-really /home/poobarr/boost_1_32_0/tools/build/v2/build/targets.jam:723: in object(main-target)@1.generate /home/poobarr/boost_1_32_0/tools/build/v2/build/targets.jam:252: in object(project-target)@1.generate /home/poobarr/boost_1_32_0/tools/build/v2/build-system.jam:160: in load /home/poobarr/boost_1_32_0/tools/build/v2/kernel/modules.jam:259: in import /home/poobarr/boost_1_32_0/tools/build/v2/kernel/bootstrap.jam:120: in boost-build /home/poobarr/boost_1_32_0/tools/build/v2/example/hello/boost-build.jam:1: in module scope ------------- took a look at boost-build.jam but, not sure where to track the problem -- or if this output is even a problem It doesn't say compilation failed, but it doesn't say anything about even calling gcc all of these examples won't compile, I am confused. It appears to be a bjam problem (note this is all being done in the hello directory, not bjam root. but I am using the '--v2' flag) And finally, after tweaking as I have, I followed Rene's advice, went to the Bayes++ directory and tried the following three commands: bjam --v2 "-sBOOST=/home/poobarr/boost_1_32_0/" (local boost) bjam --v2 "-sBOOST=/usr/local/include/boost-1_32/" (global boost install) bjam --v2 all yielding yielded ---------------------------------------- /home/poobarr/boost_1_32_0/tools/build/v2/build/targets.jam:369: in find-really /home/poobarr/boost_1_32_0/tools/build/v2/build/targets.jam:401: in object(project-target)@2.find /home/poobarr/boost_1_32_0/tools/build/v2/build/targets.jam:828: in resolve-reference /home/poobarr/boost_1_32_0/tools/build/v2/build/targets.jam:847: in targets.generate-from-reference /home/poobarr/boost_1_32_0/tools/build/v2/build/targets.jam:1056: in generate-dependencies /home/poobarr/boost_1_32_0/tools/build/v2/build/targets.jam:1097: in object(typed-target)@1.generate /home/poobarr/boost_1_32_0/tools/build/v2/build/targets.jam:750: in generate-really /home/poobarr/boost_1_32_0/tools/build/v2/build/targets.jam:723: in object(main-target)@1.generate /home/poobarr/boost_1_32_0/tools/build/v2/build/targets.jam:252: in object(project-target)@2.generate /home/poobarr/boost_1_32_0/tools/build/v2/build/targets.jam:252: in object(project-target)@1.generate /home/poobarr/boost_1_32_0/tools/build/v2/build-system.jam:160: in load /home/poobarr/boost_1_32_0/tools/build/v2//kernel/modules.jam:259: in import /home/poobarr/boost_1_32_0/tools/build/v2//kernel/bootstrap.jam:120: in boost-build /home/poobarr/boost_1_32_0/tools/build/v2//boost-build.jam:2: in module scope ------------------------------------- |
|
From: Lucas V. <lvi...@mi...> - 2005-02-02 18:17:56
|
>Release versions of Bayes++ have Jamfiles for Boost Build version 1 and
>version 2. I assume you are using '2003.8-4' which is the latest stable
>release. It would be worth trying 'bjam --v2' to see if it works in your
>case.
>
>
>
Yes I am using that release.
a simple 'bjam --v2' spits out:
---------------------
/home/poobarr/boost_1_32_0/tools/build/v2/build/feature.jam:431: in
feature.validate-value-string from module feature
error: "gcc" is not a known value of feature <toolset>
error: legal values:
/home/poobarr/boost_1_32_0/tools/build/v2/build/property.jam:249: in
validate1 from module property
/home/poobarr/boost_1_32_0/tools/build/v2/build/property.jam:272: in
property.validate from module property
/home/poobarr/boost_1_32_0/tools/build/v2/tools/builtin.jam:170: in
variant from module builtin
project-root.jam:7: in modules.load from module
Jamfile</home/poobarr/Bayes++>
/home/poobarr/boost_1_32_0/tools/build/v2/build/project.jam:301: in
load-jamfile from module project
/home/poobarr/boost_1_32_0/tools/build/v2/build/project.jam:68: in
project.load from module project
/home/poobarr/boost_1_32_0/tools/build/v2/build-system.jam:80: in load
from module build-system
/home/poobarr/boost_1_32_0/tools/build/v2/kernel/modules.jam:259: in
import from module modules
/home/poobarr/boost_1_32_0/tools/build/v2/kernel/bootstrap.jam:120: in
boost-build from module
/home/poobarr/boost_1_32_0/boost-build.jam:12: in module scope from module
------------------
so I tried ' bjam "--v2 -sTOOLS=gcc" '
which is more promising but fails
so I tried ' bjam "--v2 -sBOOST=/usr/local/include/boost-1_32/
-sTOOLS=gcc" '
which fails in a similar manner
>>v2 all you should need to set is
>>"-sBOOST=/usr/local/include/boost-1_32/".
>>
>>
>Bayes++ picks up it's settings from 'BOOST_ROOT' as described in "compiling
>the examples".
>
>
Okay I made sure BOOST_ROOT was set to /usr/local/include/boost-1_32/"
(it already was)
and still compilation errors
the errors boil down to the following, on all build attempts that get
past the basic necessities (ie it tries to compile)
is this an include issue or is this a g++ version issue?
Thanks for the help,
reading over the links that Rene provided now but I wanted to get this
email out while I had a chance.
Lucas
---------------------------------------------
[poobarr@mm122947-pc Bayes++]$ bjam "--v2 -sTOOLS=gcc"
...found 1697 targets...
...updating 36 targets...
gcc-C++-action
bin/bin/Bayes++/BayesFilter/libBayesFilter.a/gcc/debug/bayesFlt.o
In file included from /home/poobarr/Bayes++/BayesFilter/matSupSub.hpp:120,
from /home/poobarr/Bayes++/BayesFilter/bayesFlt.hpp:21,
from /home/poobarr/Bayes++/BayesFilter/bayesFlt.cpp:16:
/home/poobarr/Bayes++/BayesFilter/uBLASmatrix.hpp:28: `row' not declared
/home/poobarr/Bayes++/BayesFilter/uBLASmatrix.hpp:29: `column' not declared
/home/poobarr/Bayes++/BayesFilter/uBLASmatrix.hpp:212: syntax error
before `('
token
/home/poobarr/Bayes++/BayesFilter/uBLASmatrix.hpp:217: semicolon missing
after
declaration of `Bayesian_filter_matrix::detail::FMMatrix<MatrixBase>'
/home/poobarr/Bayes++/BayesFilter/uBLASmatrix.hpp:218: ISO C++ forbids
defining
types within return type
/home/poobarr/Bayes++/BayesFilter/uBLASmatrix.hpp:218: `sorry, not
implemented:
/home/poobarr/Bayes++/BayesFilter/uBLASmatrix.hpp:218: `parm_decl' not
supported by dump_type
<type error>' is not an aggregate type
/home/poobarr/Bayes++/BayesFilter/uBLASmatrix.hpp:218: syntax error
before `('
token
/home/poobarr/Bayes++/BayesFilter/uBLASmatrix.hpp:220: ISO C++ forbids
declaration of `sub_column' with no type
/home/poobarr/Bayes++/BayesFilter/uBLASmatrix.hpp: In function `int
Bayesian_filter_matrix::detail::sub_column(unsigned int, unsigned int,
unsigned int)':
/home/poobarr/Bayes++/BayesFilter/uBLASmatrix.hpp:221: `matrix_vector_slice'
undeclared in namespace `boost::numeric::ublas'
/home/poobarr/Bayes++/BayesFilter/uBLASmatrix.hpp:221: `MatrixBase'
undeclared
(first use this function)
/home/poobarr/Bayes++/BayesFilter/uBLASmatrix.hpp:221: (Each undeclared
identifier is reported only once for each function it appears in.)
/home/poobarr/Bayes++/BayesFilter/uBLASmatrix.hpp:221: invalid use of
`this' in
non-member function
/home/poobarr/Bayes++/BayesFilter/uBLASmatrix.hpp: At global scope:
/home/poobarr/Bayes++/BayesFilter/uBLASmatrix.hpp:255: parse error
before `<'
token
--------------------------------------- (and so on)
>
>
>>PS. It looks like the docs on the Bayes++ web page are out of date.
>>
>>
>I double checked. Docs are up to date, they were updated only about a week ago
>to match the 2003.8-4 release.
>
>Probably best to continue this discussion on the bayesclasses-general list or
>via personal mail.
>
>Michael
>
>
>
|
|
From: Michael S. <ma...@mi...> - 2005-02-02 20:01:12
|
On Wednesday 02 February 2005 19:17, Lucas Vickers wrote: > >Release versions of Bayes++ have Jamfiles for Boost Build version 1 and > >version 2. I assume you are using '2003.8-4' which is the latest stable > >release. It would be worth trying 'bjam --v2' to see if it works in your > >case. > > Yes I am using that release. > a simple 'bjam --v2' spits out: > You need to configure Boost.Build v2 first so it knows which toolset you have and which to use as a default. This is done with a 'user-config.jam'. Have look at the documentation at http://boost.org/boost-build2/ > so I tried ' bjam "--v2 -sTOOLS=gcc" ' > which is more promising but fails > > so I tried ' bjam "--v2 -sBOOST=/usr/local/include/boost-1_32/ > -sTOOLS=gcc" ' > which fails in a similar manner The -sTOOLS is not relevant to BBv2 > Okay I made sure BOOST_ROOT was set to /usr/local/include/boost-1_32/" > (it already was) > and still compilation errors Compilation errors, now we are getting somewhere! > is this an include issue or is this a g++ version issue? This is a 'g++' version issue. Which version of gcc is this? Michael -- ___________________________________ Michael Stevens Systems Engineering Navigation Systems, Estimation and Bayesian Filtering http://bayesclasses.sf.net ___________________________________ |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X