Problems getting Boost to work when compiling with Ocelot

1,216 views
Skip to first unread message

mattds...@gmail.com

unread,
Jun 14, 2010, 2:41:00 PM6/14/10
to gpuocelot
Hi everyone,

I have been working on installing Ocelot on my Fedora 12 machine
(http://groups.google.com/group/gpuocelot/browse_thread/thread/
5d100c1dbdf604ae#), and I believe that I've got it installed correctly
now. However, when I try to compile an example program, I get the
following error message:

$ nvcc -cuda example.cu
ptxas /tmp/tmpxft_0000670b_00000000-2_example.ptx, line 114; warning :
Double is not supported. Demoting to float
$ g++ -o example_ocelot example.cu.cpp `OcelotConfig -l`
/usr/local/lib/libocelot.so: undefined reference to
`boost::serialization::extended_type_info::key_unregister() const'
/usr/local/lib/libocelot.so: undefined reference to
`boost::serialization::typeid_system::extended_type_info_typeid_0::type_unregister()'
/usr/local/lib/libocelot.so: undefined reference to
`boost::serialization::typeid_system::extended_type_info_typeid_0::is_less_than(boost::serialization::extended_type_info
const&) const'
/usr/local/lib/libocelot.so: undefined reference to
`boost::archive::archive_exception::archive_exception(boost::archive::archive_exception::exception_code,
char const*, char const*)'
/usr/local/lib/libocelot.so: undefined reference to
`boost::serialization::typeid_system::extended_type_info_typeid_0::~extended_type_info_typeid_0()'
/usr/local/lib/libocelot.so: undefined reference to
`boost::serialization::extended_type_info::key_register() const'
/usr/local/lib/libocelot.so: undefined reference to
`boost::serialization::typeid_system::extended_type_info_typeid_0::type_register(std::type_info
const&)'
/usr/local/lib/libocelot.so: undefined reference to
`boost::archive::detail::shared_ptr_helper::shared_ptr_helper()'
/usr/local/lib/libocelot.so: undefined reference to
`boost::archive::detail::shared_ptr_helper::~shared_ptr_helper()'
/usr/local/lib/libocelot.so: undefined reference to `typeinfo for
boost::serialization::typeid_system::extended_type_info_typeid_0'
/usr/local/lib/libocelot.so: undefined reference to
`boost::serialization::typeid_system::extended_type_info_typeid_0::is_equal(boost::serialization::extended_type_info
const&) const'
/usr/local/lib/libocelot.so: undefined reference to
`boost::serialization::typeid_system::extended_type_info_typeid_0::extended_type_info_typeid_0(char
const*)'
collect2: ld returned 1 exit status

Any ideas what the problem could be? I went back and manually re-
installed Boost 1.42, and it completed without issue (even though it
doesn't seem to be).

Thanks,
Matt

Gregory...@gatech.edu

unread,
Jun 14, 2010, 2:54:47 PM6/14/10
to gpuo...@googlegroups.com
Try running 'ldd /usr/local/libocelot.so'. You should get some references to boost as in:

...
libboost_serialization.so.1.40.0 => /usr/lib/libboost_serialization.so.1.40.0 (0x009fd000)
libboost_wserialization.so.1.40.0 => /usr/lib/libboost_wserialization.so.1.40.0 (0x00d27000)
libboost_filesystem.so.1.40.0 => /usr/lib/libboost_filesystem.so.1.40.0 (0x004e6000)
libboost_system.so.1.40.0 => /usr/lib/libboost_system.so.1.40.0 (0x00516000)
...

If not, try adding boost's path to your LD_LIBRARY_PATH.

Regards,

Greg

Hi everyone,

Thanks,
Matt

--
You received this message because you are subscribed to the Google Groups "gpuocelot" group.
To post to this group, send email to gpuo...@googlegroups.com.
To unsubscribe from this group, send email to gpuocelot+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/gpuocelot?hl=en.

mattds...@gmail.com

unread,
Jun 14, 2010, 3:01:01 PM6/14/10
to gpuocelot
The ldd option did not work, it returned this:

ldd: /usr/local/libocelot.so: No such file or directory

Adding the top-level directory of the unzipped / installed Boost files
did not work either. Any other ideas?

Thanks,
Matt

mattds...@gmail.com

unread,
Jun 14, 2010, 3:02:32 PM6/14/10
to gpuocelot
I can see the libboost libraries installed in the lib64 folder.
Should I be adding one of those instead? If so, which one?

Matt

mattds...@gmail.com

unread,
Jun 14, 2010, 3:04:15 PM6/14/10
to gpuocelot

mattds...@gmail.com

unread,
Jun 14, 2010, 3:06:20 PM6/14/10
to gpuocelot

Diamos, Gregory F

unread,
Jun 14, 2010, 3:10:08 PM6/14/10
to gpuo...@googlegroups.com
Sorry, you probably want /usr/local/lib/libocelot.so not /usr/local/libocelot.so ... Also if boost installs into lib64 then try adding that to your LD_LIBRARY_PATH variable.

Greg

----- Original Message -----
From: "msin...@wisc.edu" <mattds...@gmail.com>
To: "gpuocelot" <gpuo...@googlegroups.com>

Matt

--

mattds...@gmail.com

unread,
Jun 14, 2010, 3:13:47 PM6/14/10
to gpuocelot
I tried with /usr/local/lib/libocelot.so instead and got something
similar to what you have:

...
libboost_serialization-mt.so.5 => /usr/lib64/libboost_serialization-
mt.so.5 (0x00007fa21e702000)
libboost_wserialization-mt.so.5 => /usr/lib64/libboost_wserialization-
mt.so.5 (0x00007fa21e4a7000)
libboost_filesystem-mt.so.5 => /usr/lib64/libboost_filesystem-mt.so.5
(0x00007fa21e293000)
libboost_system-mt.so.5 => /usr/lib64/libboost_system-mt.so.5
(0x00007fa21e090000)
...

What does this mean though? Does it mean I should be adding /usr/
local/lib/libocelot.so to my library path?

Matt

Gregory...@gatech.edu

unread,
Jun 14, 2010, 3:54:19 PM6/14/10
to gpuo...@googlegroups.com
This means that ocelot is linked against the boost libraries that you have installed under /usr/lib64, which should be fine. When you run OcelotConfig -l it should link against ocelot.so which should implicitly link against all of its dependencies, including boost. You could try specifying your version of boost explicitly via

g++ -o example example.cu.cpp -L /usr/lib64 -lboost_serialization-mt -lboost_wserialization-mt -lboost_filesystem-mt `OcelotConfig -l`

Greg

----- Original Message -----
From: "msin...@wisc.edu" <mattds...@gmail.com>
To: "gpuocelot" <gpuo...@googlegroups.com>
Sent: Monday, June 14, 2010 12:13:47 PM GMT -08:00 US/Canada Pacific
Subject: [gpuocelot] Re: Problems getting Boost to work when compiling with Ocelot

Matt

--

mattds...@gmail.com

unread,
Jun 14, 2010, 4:00:16 PM6/14/10
to gpuocelot
Hi Greg,

Thanks again for your help, I really appreciate it. I tried
specifying the libraries explicitly, as you mentioned, and that did
not change the error message(s). Any other ideas?

Thanks,
Matt

Gregory...@gatech.edu

unread,
Jun 14, 2010, 4:14:03 PM6/14/10
to gpuo...@googlegroups.com
It is possible that you have multiple versions of boost installed. Could you check under /usr/local/lib for any other boost libraries?

Greg

----- Original Message -----
From: "msin...@wisc.edu" <mattds...@gmail.com>
To: "gpuocelot" <gpuo...@googlegroups.com>
Sent: Monday, June 14, 2010 1:00:16 PM GMT -08:00 US/Canada Pacific
Subject: [gpuocelot] Re: Problems getting Boost to work when compiling with Ocelot

Hi Greg,

Thanks,
Matt

--

mattds...@gmail.com

unread,
Jun 14, 2010, 4:20:09 PM6/14/10
to gpuocelot
It would appear that you are correct. In /usr/lib64/ there are boost
1.39.0 files installed. And in /usr/local/lib64/, there are the boost
1.42.0 files installed. So would it be something as simple as
removing the 1.39.0 files, or creating symlinks to the 1.42.0 files?

Matt

Diamos, Gregory F

unread,
Jun 14, 2010, 4:37:12 PM6/14/10
to gpuo...@googlegroups.com
I think that just uninstalling either version of boost and then rebuilding ocelot (you would have to run ./configure again) would be the easiest solution. Ocelot should work with either 1.39 or 1.42.

Regards,

Greg

----- Original Message -----
From: "msin...@wisc.edu" <mattds...@gmail.com>
To: "gpuocelot" <gpuo...@googlegroups.com>
Sent: Monday, June 14, 2010 1:20:09 PM GMT -08:00 US/Canada Pacific
Subject: [gpuocelot] Re: Problems getting Boost to work when compiling with Ocelot

Matt

--

mattds...@gmail.com

unread,
Jun 14, 2010, 5:02:47 PM6/14/10
to gpuocelot
So after seeing what you said, I decided to clobber both of them and
start over installing Boost 1.42.0. I was able to install it (at
least it runs through everything and there doesn't appear to be any
errors), but when I run ./configure for Ocelot (I ran through
libtoolize, aclocal, automake, autoconf, etc. again after re-
installing Boost), I get the following message:

...
checking for main in -lboost_system-mt... no
configure: error: "libboost_system required"

Any ideas what might be happening now?

Thanks,
Matt

Gregory...@gatech.edu

unread,
Jun 14, 2010, 5:13:36 PM6/14/10
to gpuo...@googlegroups.com
See section 6.1 on here ( http://www.boost.org/doc/libs/1_43_0/more/getting_started/unix-variants.html ). Boost names libraries differently depending on how they were built. The easiest way to get around this is to just create symbolic links to the versions that you have installed.

We end up getting the vast majority of build issues due to boost. I am seriously considering stripping out everything that depends on boost and releasing it separately from the main code base. What do other people think?

Regards,

Greg

----- Original Message -----
From: "msin...@wisc.edu" <mattds...@gmail.com>
To: "gpuocelot" <gpuo...@googlegroups.com>
Sent: Monday, June 14, 2010 2:02:47 PM GMT -08:00 US/Canada Pacific
Subject: [gpuocelot] Re: Problems getting Boost to work when compiling with Ocelot

Thanks,
Matt

--

mattds...@gmail.com

unread,
Jun 14, 2010, 5:17:58 PM6/14/10
to gpuocelot
Hi Greg,

Sorry for causing so much grief. I will look at that section again
and see if I can make it work from that. Basically, what's happening
is that it's installing the files in /usr/local/lib, and when I'm
running configure, it can't find the files there. I will see if using
that section / symbolic links solves that problem and let you know
tomorrow.

Thanks,
Matt

ark...@gatech.edu

unread,
Jun 14, 2010, 7:13:11 PM6/14/10
to gpuo...@googlegroups.com

----- "Gregory Diamos" <Gregory...@gatech.edu> wrote:
>
> We end up getting the vast majority of build issues due to boost. I
> am seriously considering stripping out everything that depends on
> boost and releasing it separately from the main code base. What do
> other people think?
>

Ultimately, we'd like to support as many platforms as possible including the three
major OSes. Decoupling Ocelot from dependencies that tend to be highly platform-specific
such as OpenGL, GLEW, and librt seems like a crucial step.

Boost, however, is pretty fundamental to a large number of Ocelot components.
Rather than pull everything that depends on Boost out of the main codebase, it seems
like we could get away with constructing our own Boost distribution consisting only
of templates and class definitions we actually used (like boost::dynamic_biset and
boost::filesystem). The Boost license would support that. Moreover, unlike LLVM,
Boost isn't so fast-moving that we couldn't distribute a snapshot of some stable
version.

Ideally, we'd want people to be able to build and run Ocelot after chasing down a
minimum number of external dependencies.

How does that sound?

--
Andrew Kerr
ark...@gatech.edu

Gregory Diamos

unread,
Jun 15, 2010, 10:02:52 AM6/15/10
to gpuo...@googlegroups.com
On 06/14/2010 04:13 PM, ark...@gatech.edu wrote:
>
> ----- "Gregory Diamos"<Gregory...@gatech.edu> wrote:
>>
>> We end up getting the vast majority of build issues due to boost. I
>> am seriously considering stripping out everything that depends on
>> boost and releasing it separately from the main code base. What do
>> other people think?
>>
>
> Ultimately, we'd like to support as many platforms as possible including the three
> major OSes. Decoupling Ocelot from dependencies that tend to be highly platform-specific
> such as OpenGL, GLEW, and librt seems like a crucial step.

I agree with the point that we want to ease the transition to platforms
other than linux, but I don't think that OpenGL or GLEW are standing in
the way. There are implementations of each for all three major OSes.
librt is the kicker, but would be very easy to wrap using platform
specific backends as we only use it for one function (gettimeofday).

>
> Boost, however, is pretty fundamental to a large number of Ocelot components.
> Rather than pull everything that depends on Boost out of the main codebase, it seems
> like we could get away with constructing our own Boost distribution consisting only
> of templates and class definitions we actually used (like boost::dynamic_biset and
> boost::filesystem). The Boost license would support that. Moreover, unlike LLVM,
> Boost isn't so fast-moving that we couldn't distribute a snapshot of some stable
> version.

Other than dynamic bitset, it is used mainly by the trace generators for
the serialization library and a few unit tests which rely on filesystem.
We could rip out the pieces that are required (I have done this in the
past), just realize that it is going to be on the order of 80-100 files.
See the included dependencies (headers only) for one of the trace
generators at the end of the email.

>
> Ideally, we'd want people to be able to build and run Ocelot after chasing down a
> minimum number of external dependencies.
>
> How does that sound?
>

Ideally we wouldn't want any, but that is probably wishful thinking.

Greg

=====================================

/usr/include/boost/serialization/split_member.hpp \
/usr/include/boost/config.hpp /usr/include/boost/config/user.hpp \
/usr/include/boost/config/select_compiler_config.hpp \
/usr/include/boost/config/compiler/gcc.hpp \
/usr/include/boost/config/select_stdlib_config.hpp \
/usr/include/boost/config/no_tr1/utility.hpp \
/usr/include/boost/config/stdlib/libstdcpp3.hpp \
/usr/include/boost/config/select_platform_config.hpp \
/usr/include/boost/config/platform/linux.hpp \
/usr/include/boost/config/posix_features.hpp \
/usr/include/boost/config/suffix.hpp /usr/include/boost/mpl/eval_if.hpp \
/usr/include/boost/mpl/if.hpp /usr/include/boost/mpl/aux_/value_wknd.hpp \
/usr/include/boost/mpl/aux_/static_cast.hpp \
/usr/include/boost/mpl/aux_/config/workaround.hpp \
/usr/include/boost/detail/workaround.hpp \
/usr/include/boost/mpl/aux_/config/integral.hpp \
/usr/include/boost/mpl/aux_/config/msvc.hpp \
/usr/include/boost/mpl/aux_/config/eti.hpp \
/usr/include/boost/mpl/aux_/na_spec.hpp \
/usr/include/boost/mpl/lambda_fwd.hpp \
/usr/include/boost/mpl/void_fwd.hpp \
/usr/include/boost/mpl/aux_/adl_barrier.hpp \
/usr/include/boost/mpl/aux_/config/adl.hpp \
/usr/include/boost/mpl/aux_/config/intel.hpp \
/usr/include/boost/mpl/aux_/config/gcc.hpp \
/usr/include/boost/mpl/aux_/na.hpp /usr/include/boost/mpl/bool.hpp \
/usr/include/boost/mpl/bool_fwd.hpp \
/usr/include/boost/mpl/integral_c_tag.hpp \
/usr/include/boost/mpl/aux_/config/static_constant.hpp \
/usr/include/boost/mpl/aux_/na_fwd.hpp \
/usr/include/boost/mpl/aux_/config/ctps.hpp \
/usr/include/boost/mpl/aux_/config/lambda.hpp \
/usr/include/boost/mpl/aux_/config/ttp.hpp \
/usr/include/boost/mpl/int.hpp /usr/include/boost/mpl/int_fwd.hpp \
/usr/include/boost/mpl/aux_/nttp_decl.hpp \
/usr/include/boost/mpl/aux_/config/nttp.hpp \
/usr/include/boost/mpl/aux_/integral_wrapper.hpp \
/usr/include/boost/preprocessor/cat.hpp \
/usr/include/boost/preprocessor/config/config.hpp \
/usr/include/boost/mpl/aux_/lambda_arity_param.hpp \
/usr/include/boost/mpl/aux_/template_arity_fwd.hpp \
/usr/include/boost/mpl/aux_/arity.hpp \
/usr/include/boost/mpl/aux_/config/dtp.hpp \
/usr/include/boost/mpl/aux_/preprocessor/params.hpp \
/usr/include/boost/mpl/aux_/config/preprocessor.hpp \
/usr/include/boost/preprocessor/comma_if.hpp \
/usr/include/boost/preprocessor/punctuation/comma_if.hpp \
/usr/include/boost/preprocessor/control/if.hpp \
/usr/include/boost/preprocessor/control/iif.hpp \
/usr/include/boost/preprocessor/logical/bool.hpp \
/usr/include/boost/preprocessor/facilities/empty.hpp \
/usr/include/boost/preprocessor/punctuation/comma.hpp \
/usr/include/boost/preprocessor/repeat.hpp \
/usr/include/boost/preprocessor/repetition/repeat.hpp \
/usr/include/boost/preprocessor/debug/error.hpp \
/usr/include/boost/preprocessor/detail/auto_rec.hpp \
/usr/include/boost/preprocessor/tuple/eat.hpp \
/usr/include/boost/preprocessor/inc.hpp \
/usr/include/boost/preprocessor/arithmetic/inc.hpp \
/usr/include/boost/mpl/aux_/preprocessor/enum.hpp \
/usr/include/boost/mpl/aux_/preprocessor/def_params_tail.hpp \
/usr/include/boost/mpl/limits/arity.hpp \
/usr/include/boost/preprocessor/logical/and.hpp \
/usr/include/boost/preprocessor/logical/bitand.hpp \
/usr/include/boost/preprocessor/identity.hpp \
/usr/include/boost/preprocessor/facilities/identity.hpp \
/usr/include/boost/preprocessor/empty.hpp \
/usr/include/boost/preprocessor/arithmetic/add.hpp \
/usr/include/boost/preprocessor/arithmetic/dec.hpp \
/usr/include/boost/preprocessor/control/while.hpp \
/usr/include/boost/preprocessor/list/fold_left.hpp \
/usr/include/boost/preprocessor/list/detail/fold_left.hpp \
/usr/include/boost/preprocessor/control/expr_iif.hpp \
/usr/include/boost/preprocessor/list/adt.hpp \
/usr/include/boost/preprocessor/detail/is_binary.hpp \
/usr/include/boost/preprocessor/detail/check.hpp \
/usr/include/boost/preprocessor/logical/compl.hpp \
/usr/include/boost/preprocessor/list/fold_right.hpp \
/usr/include/boost/preprocessor/list/detail/fold_right.hpp \
/usr/include/boost/preprocessor/list/reverse.hpp \
/usr/include/boost/preprocessor/control/detail/while.hpp \
/usr/include/boost/preprocessor/tuple/elem.hpp \
/usr/include/boost/preprocessor/arithmetic/sub.hpp \
/usr/include/boost/mpl/aux_/config/overload_resolution.hpp \
/usr/include/boost/mpl/aux_/lambda_support.hpp \
/usr/include/boost/mpl/identity.hpp \
/usr/include/boost/serialization/access.hpp \
/usr/include/boost/serialization/pfto.hpp \
/usr/include/boost/dynamic_bitset.hpp \
/usr/include/boost/dynamic_bitset/dynamic_bitset.hpp \
/usr/include/boost/dynamic_bitset/config.hpp /usr/include/c++/4.4/locale \
/usr/include/boost/dynamic_bitset_fwd.hpp /usr/include/c++/4.4/memory \
/usr/include/c++/4.4/tr1_impl/boost_sp_counted_base.h \
/usr/include/boost/detail/dynamic_bitset.hpp \
/usr/include/boost/detail/iterator.hpp /usr/include/c++/4.4/iterator \
/usr/include/boost/static_assert.hpp /usr/include/boost/limits.hpp \
/usr/include/c++/4.4/limits /usr/include/boost/pending/lowest_bit.hpp \
/usr/include/boost/pending/integer_log2.hpp \
hydrazine/implementation/Exception.h /usr/include/boost/filesystem.hpp \
/usr/include/boost/filesystem/operations.hpp \
/usr/include/boost/filesystem/path.hpp \
/usr/include/boost/filesystem/config.hpp \
/usr/include/boost/config/auto_link.hpp \
/usr/include/boost/system/system_error.hpp \
/usr/include/boost/system/error_code.hpp \
/usr/include/boost/system/config.hpp /usr/include/boost/cstdint.hpp \
/usr/include/boost/assert.hpp /usr/include/boost/operators.hpp \
/usr/include/boost/iterator.hpp /usr/include/boost/noncopyable.hpp \
/usr/include/boost/utility/enable_if.hpp /usr/include/boost/cerrno.hpp \
/usr/include/boost/config/abi_prefix.hpp \
/usr/include/boost/config/abi_suffix.hpp \
/usr/include/boost/iterator/iterator_facade.hpp \
/usr/include/boost/iterator/interoperable.hpp \
/usr/include/boost/mpl/or.hpp \
/usr/include/boost/mpl/aux_/config/use_preprocessed.hpp \
/usr/include/boost/mpl/aux_/nested_type_wknd.hpp \
/usr/include/boost/mpl/aux_/include_preprocessed.hpp \
/usr/include/boost/mpl/aux_/config/compiler.hpp \
/usr/include/boost/preprocessor/stringize.hpp \
/usr/include/boost/mpl/aux_/preprocessed/gcc/or.hpp \
/usr/include/boost/type_traits/is_convertible.hpp \
/usr/include/boost/type_traits/intrinsics.hpp \
/usr/include/boost/type_traits/config.hpp \
/usr/include/boost/type_traits/is_same.hpp \
/usr/include/boost/type_traits/detail/bool_trait_def.hpp \
/usr/include/boost/type_traits/detail/template_arity_spec.hpp \
/usr/include/boost/type_traits/integral_constant.hpp \
/usr/include/boost/mpl/integral_c.hpp \
/usr/include/boost/mpl/integral_c_fwd.hpp \
/usr/include/boost/type_traits/detail/bool_trait_undef.hpp \
/usr/include/boost/type_traits/is_reference.hpp \
/usr/include/boost/type_traits/is_volatile.hpp \
/usr/include/boost/type_traits/detail/cv_traits_impl.hpp \
/usr/include/boost/type_traits/detail/yes_no_type.hpp \
/usr/include/boost/type_traits/is_array.hpp \
/usr/include/boost/type_traits/add_reference.hpp \
/usr/include/boost/type_traits/detail/type_trait_def.hpp \
/usr/include/boost/type_traits/detail/type_trait_undef.hpp \
/usr/include/boost/type_traits/ice.hpp \
/usr/include/boost/type_traits/detail/ice_or.hpp \
/usr/include/boost/type_traits/detail/ice_and.hpp \
/usr/include/boost/type_traits/detail/ice_not.hpp \
/usr/include/boost/type_traits/detail/ice_eq.hpp \
/usr/include/boost/type_traits/is_arithmetic.hpp \
/usr/include/boost/type_traits/is_integral.hpp \
/usr/include/boost/type_traits/is_float.hpp \
/usr/include/boost/type_traits/is_void.hpp \
/usr/include/boost/type_traits/is_abstract.hpp \
/usr/include/boost/iterator/detail/config_def.hpp \
/usr/include/boost/iterator/detail/config_undef.hpp \
/usr/include/boost/iterator/iterator_traits.hpp \
/usr/include/boost/iterator/detail/facade_iterator_category.hpp \
/usr/include/boost/iterator/iterator_categories.hpp \
/usr/include/boost/mpl/placeholders.hpp /usr/include/boost/mpl/arg.hpp \
/usr/include/boost/mpl/arg_fwd.hpp \
/usr/include/boost/mpl/aux_/na_assert.hpp \
/usr/include/boost/mpl/assert.hpp /usr/include/boost/mpl/not.hpp \
/usr/include/boost/mpl/aux_/yes_no.hpp \
/usr/include/boost/mpl/aux_/config/arrays.hpp \
/usr/include/boost/mpl/aux_/config/pp_counter.hpp \
/usr/include/boost/mpl/aux_/arity_spec.hpp \
/usr/include/boost/mpl/aux_/arg_typedef.hpp \
/usr/include/boost/mpl/aux_/preprocessed/gcc/arg.hpp \
/usr/include/boost/mpl/aux_/preprocessed/gcc/placeholders.hpp \
/usr/include/boost/mpl/and.hpp \
/usr/include/boost/mpl/aux_/preprocessed/gcc/and.hpp \
/usr/include/boost/type_traits/is_const.hpp \
/usr/include/boost/detail/indirect_traits.hpp \
/usr/include/boost/type_traits/is_function.hpp \
/usr/include/boost/type_traits/detail/false_result.hpp \
/usr/include/boost/type_traits/detail/is_function_ptr_helper.hpp \
/usr/include/boost/type_traits/is_pointer.hpp \
/usr/include/boost/type_traits/is_member_pointer.hpp \
/usr/include/boost/type_traits/is_member_function_pointer.hpp \
/usr/include/boost/type_traits/detail/is_mem_fun_pointer_impl.hpp \
/usr/include/boost/type_traits/remove_cv.hpp \
/usr/include/boost/type_traits/broken_compiler_spec.hpp \
/usr/include/boost/type_traits/is_class.hpp \
/usr/include/boost/type_traits/remove_reference.hpp \
/usr/include/boost/type_traits/remove_pointer.hpp \
/usr/include/boost/iterator/detail/enable_if.hpp \
/usr/include/boost/implicit_cast.hpp \
/usr/include/boost/type_traits/add_const.hpp \
/usr/include/boost/type_traits/add_pointer.hpp \
/usr/include/boost/type_traits/remove_const.hpp \
/usr/include/boost/type_traits/is_pod.hpp \
/usr/include/boost/type_traits/is_scalar.hpp \
/usr/include/boost/type_traits/is_enum.hpp \
/usr/include/boost/mpl/always.hpp /usr/include/boost/mpl/apply.hpp \
/usr/include/boost/mpl/apply_fwd.hpp \
/usr/include/boost/mpl/aux_/preprocessed/gcc/apply_fwd.hpp \
/usr/include/boost/mpl/apply_wrap.hpp \
/usr/include/boost/mpl/aux_/has_apply.hpp \
/usr/include/boost/mpl/has_xxx.hpp \
/usr/include/boost/mpl/aux_/type_wrapper.hpp \
/usr/include/boost/mpl/aux_/config/has_xxx.hpp \
/usr/include/boost/mpl/aux_/config/msvc_typename.hpp \
/usr/include/boost/mpl/aux_/config/has_apply.hpp \
/usr/include/boost/mpl/aux_/msvc_never_true.hpp \
/usr/include/boost/mpl/aux_/preprocessed/gcc/apply_wrap.hpp \
/usr/include/boost/mpl/lambda.hpp /usr/include/boost/mpl/bind.hpp \
/usr/include/boost/mpl/bind_fwd.hpp \
/usr/include/boost/mpl/aux_/config/bind.hpp \
/usr/include/boost/mpl/aux_/preprocessed/gcc/bind_fwd.hpp \
/usr/include/boost/mpl/next.hpp /usr/include/boost/mpl/next_prior.hpp \
/usr/include/boost/mpl/aux_/common_name_wknd.hpp \
/usr/include/boost/mpl/protect.hpp \
/usr/include/boost/mpl/aux_/preprocessed/gcc/bind.hpp \
/usr/include/boost/mpl/aux_/full_lambda.hpp \
/usr/include/boost/mpl/quote.hpp /usr/include/boost/mpl/void.hpp \
/usr/include/boost/mpl/aux_/has_type.hpp \
/usr/include/boost/mpl/aux_/config/bcc.hpp \
/usr/include/boost/mpl/aux_/preprocessed/gcc/quote.hpp \
/usr/include/boost/mpl/aux_/template_arity.hpp \
/usr/include/boost/mpl/aux_/preprocessed/gcc/template_arity.hpp \
/usr/include/boost/mpl/aux_/preprocessed/gcc/full_lambda.hpp \
/usr/include/boost/mpl/aux_/preprocessed/gcc/apply.hpp \
/usr/include/boost/throw_exception.hpp \
/usr/include/boost/exception/detail/attribute_noreturn.hpp \
/usr/include/boost/exception/exception.hpp \
/usr/include/boost/current_function.hpp \
/usr/include/boost/shared_ptr.hpp \
/usr/include/boost/smart_ptr/shared_ptr.hpp \
/usr/include/boost/config/no_tr1/memory.hpp \
/usr/include/boost/checked_delete.hpp \
/usr/include/boost/smart_ptr/detail/shared_count.hpp \
/usr/include/boost/smart_ptr/bad_weak_ptr.hpp \
/usr/include/boost/smart_ptr/detail/sp_counted_base.hpp \
/usr/include/boost/smart_ptr/detail/sp_has_sync.hpp \
/usr/include/boost/smart_ptr/detail/sp_counted_base_gcc_x86.hpp \
/usr/include/boost/detail/sp_typeinfo.hpp \
/usr/include/boost/smart_ptr/detail/sp_counted_impl.hpp \
/usr/include/boost/smart_ptr/detail/sp_convertible.hpp \
/usr/include/boost/smart_ptr/detail/spinlock_pool.hpp \
/usr/include/boost/smart_ptr/detail/spinlock.hpp \
/usr/include/boost/smart_ptr/detail/spinlock_sync.hpp \
/usr/include/boost/smart_ptr/detail/yield_k.hpp \
/usr/include/boost/memory_order.hpp \
/usr/include/boost/smart_ptr/detail/operator_bool.hpp \
/usr/include/boost/detail/scoped_enum_emulation.hpp \
/usr/include/boost/filesystem/convenience.hpp /usr/include/c++/4.4/stack \
/usr/include/boost/archive/text_oarchive.hpp \
/usr/include/boost/archive/detail/auto_link_archive.hpp \
/usr/include/boost/archive/detail/decl.hpp \
/usr/include/boost/archive/basic_text_oprimitive.hpp \
/usr/include/c++/4.4/iomanip /usr/include/boost/config/no_tr1/cmath.hpp \
/usr/include/c++/4.4/tr1_impl/cmath /usr/include/boost/io/ios_state.hpp \
/usr/include/boost/io_fwd.hpp /usr/include/boost/scoped_ptr.hpp \
/usr/include/boost/smart_ptr/scoped_ptr.hpp \
/usr/include/boost/serialization/throw_exception.hpp \
/usr/include/boost/archive/archive_exception.hpp \
/usr/include/boost/archive/detail/abi_prefix.hpp \
/usr/include/boost/archive/detail/abi_suffix.hpp \
/usr/include/boost/archive/basic_text_oarchive.hpp \
/usr/include/boost/archive/detail/common_oarchive.hpp \
/usr/include/boost/archive/detail/basic_oarchive.hpp \
/usr/include/boost/archive/basic_archive.hpp \
/usr/include/boost/serialization/strong_typedef.hpp \
/usr/include/boost/serialization/level.hpp \
/usr/include/boost/type_traits/is_fundamental.hpp \
/usr/include/boost/type_traits/is_base_and_derived.hpp \
/usr/include/boost/serialization/level_enum.hpp \
/usr/include/boost/serialization/tracking_enum.hpp \
/usr/include/boost/archive/detail/interface_oarchive.hpp \
/usr/include/boost/archive/detail/oserializer.hpp \
/usr/include/boost/serialization/smart_cast.hpp \
/usr/include/boost/type_traits/is_polymorphic.hpp \
/usr/include/boost/serialization/static_warning.hpp \
/usr/include/boost/type_traits/remove_extent.hpp \
/usr/include/boost/serialization/assume_abstract.hpp \
/usr/include/boost/mpl/greater_equal.hpp \
/usr/include/boost/mpl/aux_/comparison_op.hpp \
/usr/include/boost/mpl/aux_/numeric_op.hpp \
/usr/include/boost/mpl/numeric_cast.hpp /usr/include/boost/mpl/tag.hpp \
/usr/include/boost/mpl/aux_/has_tag.hpp \
/usr/include/boost/mpl/aux_/numeric_cast_utils.hpp \
/usr/include/boost/mpl/aux_/config/forwarding.hpp \
/usr/include/boost/mpl/aux_/msvc_eti_base.hpp \
/usr/include/boost/mpl/aux_/is_msvc_eti_arg.hpp \
/usr/include/boost/mpl/aux_/preprocessed/gcc/greater_equal.hpp \
/usr/include/boost/mpl/equal_to.hpp \
/usr/include/boost/mpl/aux_/preprocessed/gcc/equal_to.hpp \
/usr/include/boost/serialization/extended_type_info_typeid.hpp \
/usr/include/boost/serialization/singleton.hpp \
/usr/include/boost/serialization/force_include.hpp \
/usr/include/boost/serialization/extended_type_info.hpp \
/usr/include/boost/serialization/config.hpp \
/usr/include/boost/weak_ptr.hpp \
/usr/include/boost/smart_ptr/weak_ptr.hpp \
/usr/include/boost/serialization/factory.hpp \
/usr/include/boost/preprocessor/comparison/greater.hpp \
/usr/include/boost/preprocessor/comparison/less.hpp \
/usr/include/boost/preprocessor/comparison/less_equal.hpp \
/usr/include/boost/preprocessor/logical/not.hpp \
/usr/include/boost/preprocessor/comparison/not_equal.hpp \
/usr/include/boost/archive/detail/basic_oserializer.hpp \
/usr/include/boost/archive/detail/basic_serializer.hpp \
/usr/include/boost/archive/detail/basic_pointer_oserializer.hpp \
/usr/include/boost/archive/detail/archive_serializer_map.hpp \
/usr/include/boost/serialization/serialization.hpp \
/usr/include/boost/serialization/nvp.hpp \
/usr/include/boost/serialization/tracking.hpp \
/usr/include/boost/mpl/greater.hpp \
/usr/include/boost/mpl/aux_/preprocessed/gcc/greater.hpp \
/usr/include/boost/serialization/type_info_implementation.hpp \
/usr/include/boost/serialization/traits.hpp \
/usr/include/boost/serialization/base_object.hpp \
/usr/include/boost/serialization/void_cast_fwd.hpp \
/usr/include/boost/serialization/wrapper.hpp \
/usr/include/boost/serialization/version.hpp \
/usr/include/boost/serialization/void_cast.hpp \
/usr/include/boost/type_traits/is_virtual_base_of.hpp \
/usr/include/boost/type_traits/is_base_of.hpp \
/usr/include/boost/serialization/array.hpp /usr/include/boost/array.hpp \
/usr/include/boost/swap.hpp /usr/include/boost/utility/swap.hpp \
/usr/include/boost/serialization/collection_size_type.hpp \
/usr/include/boost/serialization/string.hpp \
/usr/include/boost/archive/detail/register_archive.hpp

mattds...@gmail.com

unread,
Jun 15, 2010, 12:44:46 PM6/15/10
to gpuocelot
Greg,

Where are you proposing I create symbolic links? The libraries are
already installed in /usr/local/lib, but obviously that isn't working
with Ocelot, because it can't find them there.

Thanks,
Matt

Diamos, Gregory F

unread,
Jun 15, 2010, 12:49:07 PM6/15/10
to gpuo...@googlegroups.com
I would do something like this:

sudo ln -s /usr/local/lib/libboost_filesystem-******.so /usr/local/lib/libboost_filsystem-mt.so
sudo ln -s /usr/local/lib/libboost_serialization-******.so /usr/local/lib/libboost_serialization-mt.so
sudo ln -s /usr/local/lib/libboost_wserialization-******.so /usr/local/lib/libboost_wserialization-mt.so

and then rebuild ocelot.

make clean
./configure
sudo make install

Regards,

Greg

----- Original Message -----
From: "msin...@wisc.edu" <mattds...@gmail.com>
To: "gpuocelot" <gpuo...@googlegroups.com>
Sent: Tuesday, June 15, 2010 9:44:46 AM GMT -08:00 US/Canada Pacific
Subject: [gpuocelot] Re: Problems getting Boost to work when compiling with Ocelot

Greg,

Thanks,
Matt

--

mattds...@gmail.com

unread,
Jun 15, 2010, 1:08:31 PM6/15/10
to gpuocelot
Hi Greg,

Thanks for the help. In addition to the sym links you asked me to
make, I had to do the same for the libboost_system*.so file. After
doing that, I did make clean, ./configure, sudo make install as you
outlined. However, when doing this error:

libtool: compile: g++ -DHAVE_CONFIG_H -I. -I/usr/local/include -
D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -
I ./ocelot/cuda/include -Wall -ansi -Werror -std=c++0x -g -O2 -MT
libocelot_la-Timer.lo -MD -MP -MF .deps/libocelot_la-Timer.Tpo -c
hydrazine/implementation/Timer.cpp -fPIC -DPIC -o .libs/libocelot_la-
Timer.o
In file included from /usr/lib/gcc/x86_64-redhat-linux/
4.4.3/../../../../include/c++/4.4.3/ext/string_conversions.h:33,
from /usr/lib/gcc/x86_64-redhat-linux/
4.4.3/../../../../include/c++/4.4.3/bits/basic_string.h:2562,
from /usr/lib/gcc/x86_64-redhat-linux/
4.4.3/../../../../include/c++/4.4.3/string:53,
from /usr/lib/gcc/x86_64-redhat-linux/
4.4.3/../../../../include/c++/4.4.3/bits/locale_classes.h:42,
from /usr/lib/gcc/x86_64-redhat-linux/
4.4.3/../../../../include/c++/4.4.3/bits/ios_base.h:43,
from /usr/lib/gcc/x86_64-redhat-linux/
4.4.3/../../../../include/c++/4.4.3/ios:43,
from /usr/lib/gcc/x86_64-redhat-linux/
4.4.3/../../../../include/c++/4.4.3/istream:40,
from /usr/lib/gcc/x86_64-redhat-linux/
4.4.3/../../../../include/c++/4.4.3/sstream:39,
from ./hydrazine/interface/Stringable.h:21,
from hydrazine/implementation/Timer.h:15,
from hydrazine/implementation/Timer.cpp:13:
/usr/lib/gcc/x86_64-redhat-linux/4.4.3/../../../../include/c++/4.4.3/
cstdlib:127: error: ‘::realloc’ has not been declared
make[1]: *** [libocelot_la-Timer.lo] Error 1

I remember when I downloaded the SVN from hydrazine being confused
about how to compile it. What needs to be done to compile it? I
don't see any directions on it in the README, etc. for it (nor on its
website). If you know how to do that, I'll try re-compiling it and
try this sequence again.

Thanks,
Matt

Diamos, Gregory F

unread,
Jun 15, 2010, 1:13:43 PM6/15/10
to gpuo...@googlegroups.com
This happened to a few other people before, though I have no idea why. See this thread: http://groups.google.com/group/gpuocelot/browse_thread/thread/9f8eb573dace12be?fwc=1&pli=1

Try doing the full reconfigure/reinstall. libtoolize; aclocal; autoconf; automake; ./configure; sudo make install

Newer versions of Ocelot do not require you to download and build hydrazine. Pulling ocelot from SVN should automatically also pull hydrazine and build it.

Regards,

Greg

----- Original Message -----
From: "msin...@wisc.edu" <mattds...@gmail.com>
To: "gpuocelot" <gpuo...@googlegroups.com>
Sent: Tuesday, June 15, 2010 10:08:31 AM GMT -08:00 US/Canada Pacific
Subject: [gpuocelot] Re: Problems getting Boost to work when compiling with Ocelot

Hi Greg,

Thanks,
Matt

--

mattds...@gmail.com

unread,
Jun 15, 2010, 1:21:06 PM6/15/10
to gpuocelot
Hi Greg,

I followed your directions on doing the full re-install. It did not
work. Here is the order I went in:

sudo make clean
libtoolize
aclocal
autoconf
automake
./configure
sudo make install

I saw in the other thread that Mr. Worley fixed it by trying it
several times. I will try that and see what happens. If anyone sees
something wrong with the order I'm using, please let me know.

Thanks,
Matt

mattds...@gmail.com

unread,
Jun 15, 2010, 1:21:55 PM6/15/10
to gpuocelot
I should also mention that it didn't work AND it was the same exact
error.

Matt

mattds...@gmail.com

unread,
Jun 15, 2010, 1:30:08 PM6/15/10
to gpuocelot
I ran it 3 times in a row, the full sequence as mentioned in my last
post, and they all stop on the same error. I tried running it without
the make clean too, and that did not solve the issue.

I started looking through the configure output. Here is the list of
things it replied "no" to, should I be worried about any of them / are
any of them possibly causing this issue?

checking whether we are cross compiling... no
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking if gcc supports -fno-rtti -fno-exceptions... no
checking whether -lc should be explicitly linked in... no
checking if g++ static flag -static works... no
checking for _LARGEFILE_SOURCE value needed for large files... no
checking for working memcmp... no
checking for GNU libc compatible realloc... no
checking for working strnlen... no
checking for working strtod... no

Any other ideas? I suppose I could check out a fresh version of
Ocelot / Hydrazine, but it doesn't seem like that would solve the
issue...

Matt

Diamos, Gregory F

unread,
Jun 15, 2010, 1:37:40 PM6/15/10
to gpuo...@googlegroups.com
Try editing configure.in and removing the line AC_FUNC_REALLOC.

Regards,

Greg

----- Original Message -----
From: "msin...@wisc.edu" <mattds...@gmail.com>
To: "gpuocelot" <gpuo...@googlegroups.com>
Sent: Tuesday, June 15, 2010 10:30:08 AM GMT -08:00 US/Canada Pacific
Subject: [gpuocelot] Re: Problems getting Boost to work when compiling with Ocelot

Matt

--

mattds...@gmail.com

unread,
Jun 15, 2010, 1:50:47 PM6/15/10
to gpuocelot
It now compiles! However, I get the following when I try to compile:

OcelotConfig: error while loading shared libraries:
libboost_serialization.so.1.42.0: cannot open shared object file: No
such file or directory

(compile line: $ g++ -o example_ocelot example.cu.cpp `OcelotConfig -
l`)

Any ideas how to fix this?

Thanks,
Matt

Diamos, Gregory F

unread,
Jun 15, 2010, 1:54:08 PM6/15/10
to gpuo...@googlegroups.com
Put the path where libboost_serialization.so.1.42.0 is located (/usr/local/lib?) on your LD_LIBRARY_PATH. Then try to run it again.

Greg

----- Original Message -----
From: "msin...@wisc.edu" <mattds...@gmail.com>
To: "gpuocelot" <gpuo...@googlegroups.com>
Sent: Tuesday, June 15, 2010 10:50:47 AM GMT -08:00 US/Canada Pacific
Subject: [gpuocelot] Re: Problems getting Boost to work when compiling with Ocelot

Thanks,
Matt

--

mattds...@gmail.com

unread,
Jun 15, 2010, 2:08:43 PM6/15/10
to gpuocelot
That is where it's located:

$ ls -l /usr/local/lib/libboost_serialization*
-rw-r--r--. 1 root root 1244352 2010-06-14 16:14 /usr/local/lib/
libboost_serialization.a
lrwxrwxrwx. 1 root root 40 2010-06-15 11:59 /usr/local/lib/
libboost_serialization-mt.so -> /usr/local/lib/
libboost_serialization.so
lrwxrwxrwx. 1 root root 32 2010-06-14 16:10 /usr/local/lib/
libboost_serialization.so -> libboost_serialization.so.1.42.0
-rwxr-xr-x. 1 root root 460648 2010-06-14 16:10 /usr/local/lib/
libboost_serialization.so.1.42.0

and it's in my LD_LIBRARY_PATH:

$ echo $LD_LIBRARY_PATH
/home/sinclair/Downloads/ocelot-1.1.560/ocelot/.libs/:/usr/lib/local/:/
usr/local/cuda/lib64:/home/sinclair/Downloads/ocelot-1.1.560/
ocelot/.libs/:/usr/lib/local/:/usr/local/cuda/lib64:

(although I don't know why it shows up twice)

However, that doesn't solve the problem, I still get the same error:

OcelotConfig: error while loading shared libraries:
libboost_serialization.so.1.42.0: cannot open shared object file: No
such file or directory

Any other ideas?

Matt

Diamos, Gregory F

unread,
Jun 15, 2010, 2:13:48 PM6/15/10
to gpuo...@googlegroups.com
It should be /usr/local/lib rather than /usr/lib/local I think.

Greg

----- Original Message -----
From: "msin...@wisc.edu" <mattds...@gmail.com>
To: "gpuocelot" <gpuo...@googlegroups.com>
Sent: Tuesday, June 15, 2010 11:08:43 AM GMT -08:00 US/Canada Pacific
Subject: [gpuocelot] Re: Problems getting Boost to work when compiling with Ocelot

Any other ideas?

Matt

--

mattds...@gmail.com

unread,
Jun 15, 2010, 2:21:10 PM6/15/10
to gpuocelot
Yep, it should have been. That wasn't embarrassing or anything...

I am able to compile it now, but I have (hopefully) one more question
for you about running it. Looking at the installation manual, it says
to do this:

LD_LIBRARY_PATH=/{path_to_the_ocelot_sdk}/ocelot/.libs/ ./MyCudaprog

(I set OCELOT_DIR = top level folder of Ocelot)

However, when I look in my $OCELOT_DIR/ocelot folder, there is
no .libs/ folder. What would I do to fix this? Or is the manual out
of date? Because when I run the command

LD_LIBRARY_PATH=$OCELOT_DIR/ocelot/.libs/ ./MyCudaprog

I get this:

./MyCudaprog: error while loading shared libraries: libocelot.so.0:
cannot open shared object file: No such file or directory

Thanks,
Matt

Diamos, Gregory F

unread,
Jun 15, 2010, 2:27:23 PM6/15/10
to gpuo...@googlegroups.com
Don't worry about it, it happens :)

That LD_LIBRARY_PATH=/{path_to_the_ocelot_sdk}/ocelot/.libs/ is only necessary if your LD__LIBRARY_PATH is not already set up properly and you do a plain make rather than a make install for ocelot. The easiest thing to do is to just do make install and set your LD_LIRBARY_PATh in some *rc file. In that case, you can just run the program normally.

Regards,

Greg

----- Original Message -----
From: "msin...@wisc.edu" <mattds...@gmail.com>
To: "gpuocelot" <gpuo...@googlegroups.com>
Sent: Tuesday, June 15, 2010 11:21:10 AM GMT -08:00 US/Canada Pacific
Subject: [gpuocelot] Re: Problems getting Boost to work when compiling with Ocelot

LD_LIBRARY_PATH=/{path_to_the_ocelot_sdk}/ocelot/.libs/ ./MyCudaprog

LD_LIBRARY_PATH=$OCELOT_DIR/ocelot/.libs/ ./MyCudaprog

I get this:

Thanks,
Matt

--

mattds...@gmail.com

unread,
Jun 15, 2010, 2:34:07 PM6/15/10
to gpuocelot
I can answer this one myself! It appears that the manual is out of
date, when I just ran ./MyCudaprog, it actually attempts to run
something (probably because I have /usr/local/lib/ in my
LD_LIBRARY_PATH environment variable).

The program I'm trying to run crashes though, I will try to look into
that and post more later.

Matt

mattds...@gmail.com

unread,
Jun 15, 2010, 2:34:39 PM6/15/10
to gpuocelot
...guess I should have refreshed first.

Matt

mattds...@gmail.com

unread,
Jun 15, 2010, 2:40:19 PM6/15/10
to gpuocelot
So I'm attempting to run an old implementation of the blackscholes
PARSEC benchmark that I did in CUDA. I am able to compile the code
with ocelot. However, when I try to run it, I get this:

==Ocelot== WARNING: Could not parse config file 'configure.ocelot',
loading defaults.
...
terminate called after throwing an instance of 'hydrazine::Exception'
what(): invalid value
Aborted (core dumped)

Is this something I did wrong when installing it? Or something else?

Thanks,
Matt

mattds...@gmail.com

unread,
Jun 15, 2010, 2:40:39 PM6/15/10
to gpuocelot
I should also mention that the version that doesn't use Ocelot runs to
completion.

Matt

Gregory...@gatech.edu

unread,
Jun 15, 2010, 2:55:56 PM6/15/10
to gpuo...@googlegroups.com
Ocelot accepts a number of configuration options in a configure.ocelot file in the directory that you run your program from. There is an example that comes in the main ocelot directory. Could you try copying that file into your current directory and changing the list of devices to 'emulated' only.

If that still generates the same error, could you tell me which version of NVCC you are using and how you compiled your program?

Regards,

Greg

----- Original Message -----
From: "msin...@wisc.edu" <mattds...@gmail.com>
To: "gpuocelot" <gpuo...@googlegroups.com>
Sent: Tuesday, June 15, 2010 11:40:19 AM GMT -08:00 US/Canada Pacific
Subject: [gpuocelot] Re: Problems getting Boost to work when compiling with Ocelot

Thanks,
Matt

--

mattds...@gmail.com

unread,
Jun 15, 2010, 3:02:52 PM6/15/10
to gpuocelot
Hi Greg,

I am not sure I completely understand what you're asking me to do.
First, I looked in my top-level / main Ocelot directory, and there is
not configure.ocelot file in there, so I'm not able to copy it over.
Second, what do you mean by changing the list of devices to emulated
only? Does that mean run my program in emulated mode?

I am using CUDA SDK 2.3 with this as the compilation line:

$ make ocelot
nvcc -arch sm_11 -cuda blackscholes.cu
g++ -o blackscholes_ocelot blackscholes.cu.cpp `OcelotConfig -l`

Thanks,
Matt

Gregory...@gatech.edu

unread,
Jun 15, 2010, 3:06:30 PM6/15/10
to gpuo...@googlegroups.com
See the attached file for an example of a configure.ocelot file.

Everything you are doing seems fine. Would you mind sending me a copy of blackscholes.cu and I could try to reproduce the problem here or give you some more information about it.

Regards,

Greg

----- Original Message -----
From: "msin...@wisc.edu" <mattds...@gmail.com>
To: "gpuocelot" <gpuo...@googlegroups.com>
Sent: Tuesday, June 15, 2010 12:02:52 PM GMT -08:00 US/Canada Pacific
Subject: [gpuocelot] Re: Problems getting Boost to work when compiling with Ocelot

Hi Greg,

Thanks,
Matt

--

configure.ocelot

mattds...@gmail.com

unread,
Jun 15, 2010, 3:10:13 PM6/15/10
to gpuocelot
I copied the file you attached to both the main Ocelot directory and
my blackscholes directory (is this ok)? Copying it to the
blackscholes directory removed the first error message:

==Ocelot== WARNING: Could not parse config file 'configure.ocelot',
loading defaults.

However, it still errors out with the same hydrazine exception (the
part after the ... in my previous post).

I will send you the code / Makefile / input file. Hopefully that will
help clear this up.

Thanks!
Matt
Reply all
Reply to author
Forward
0 new messages