Git Product home page Git Product logo

hydrazine's People

Contributors

alele3 avatar greg1232 avatar jwang323 avatar kerrmudgeon avatar sudnya avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

hydrazine's Issues

Build error

I'm on GCC 4.5.2, CUDA Toolkit 3.2, Boost 1.42.0.

Current SVN won't build:

g++ -DHAVE_CONFIG_H -I.    -Wall -ansi -pedantic -Werror -std=c++0x -g -O2 -MT 
libhydralize_a-CudaException.o -MD -MP -MF 
.deps/libhydralize_a-CudaException.Tpo -c -o libhydralize_a-CudaException.o 
`test -f 'hydrazine/cuda/CudaException.cpp' || echo 
'./'`hydrazine/cuda/CudaException.cpp
In file included from hydrazine/cuda/CudaException.cpp:11:0:
hydrazine/cuda/CudaException.h:10:48: fatal error: 
ocelot/cuda/interface/cuda_runtime.h: No such file or directory
compilation terminated.

When I edited that file and changed the include to:

#include </opt/cuda/include/cuda_runtime.h>

the build progressed further, but then I got another error:

g++ -DHAVE_CONFIG_H -I.    -Wall -ansi -pedantic -Werror -std=c++0x -pipe -O2 
-I/opt/cuda/include -MT libhydralize_a-Thread.o -MD -MP -MF 
.deps/libhydralize_a-Thread.Tpo -c -o libhydralize_a-Thread.o `test -f 
'hydrazine/interface/Thread.cpp' || echo './'`hydrazine/interface/Thread.cpp
In file included from /usr/include/boost/thread/thread.hpp:22:0,
                 from /usr/include/boost/thread.hpp:13,
                 from hydrazine/interface/Thread.h:10,                                                                                          
                 from hydrazine/interface/Thread.cpp:14:                                                                                        
/usr/include/boost/thread/detail/thread.hpp: In function 'boost::thread&& 
boost::move(boost::thread&&)':
/usr/include/boost/thread/detail/thread.hpp:349:16: error: invalid 
initialization of reference of type 'boost::thread&&' from expression of type 
'boost::thread'                                                                 

In file included from 
/usr/include/boost/thread/detail/thread_heap_alloc.hpp:17:0,
                 from /usr/include/boost/thread/detail/thread.hpp:13,
                 from /usr/include/boost/thread/thread.hpp:22,                                                                                  
                 from /usr/include/boost/thread.hpp:13,                                                                                         
                 from hydrazine/interface/Thread.h:10,                                                                                          
                 from hydrazine/interface/Thread.cpp:14:                                                                                        
/usr/include/boost/thread/pthread/thread_heap_alloc.hpp: In function 'T* 
boost::detail::heap_new(A1&&) [with T = boost::detail::thread_data<void (*)()>, 
A1 = void (*&)()]':                                                             

/usr/include/boost/thread/detail/thread.hpp:130:95:   instantiated from here    

/usr/include/boost/thread/pthread/thread_heap_alloc.hpp:24:47: error: no 
matching function for call to 'boost::detail::thread_data<void 
(*)()>::thread_data(void (*&)())'                                               

/usr/include/boost/thread/detail/thread.hpp:62:13: note: candidates are: 
boost::detail::thread_data<F>::thread_data(boost::detail::thread_data<F>&) 
[with F = void (*)(), boost::detail::thread_data<F> = 
boost::detail::thread_data<void (*)()>]                                         

/usr/include/boost/thread/detail/thread.hpp:43:13: note:                 
boost::detail::thread_data<F>::thread_data(F&&) [with F = void (*)()] <near 
match>                                                                          

In file included from /usr/include/boost/thread/pthread/mutex.hpp:11:0,
                 from /usr/include/boost/thread/mutex.hpp:16,
                 from /usr/include/boost/thread/pthread/thread_data.hpp:12,                                                                     
                 from /usr/include/boost/thread/thread.hpp:17,                                                                                  
                 from /usr/include/boost/thread.hpp:13,                                                                                         
                 from hydrazine/interface/Thread.h:10,                                                                                          
                 from hydrazine/interface/Thread.cpp:14:                                                                                        
/usr/include/boost/thread/locks.hpp: In member function 
'boost::unique_lock<Mutex>& 
boost::unique_lock<Mutex>::operator=(boost::unique_lock<Mutex>&&) [with Mutex = 
boost::mutex, boost::unique_lock<Mutex> = boost::unique_lock<boost::mutex>]':   

/usr/include/boost/thread/future.hpp:414:91:   instantiated from here           

/usr/include/boost/thread/locks.hpp:269:13: error: no matching function for 
call to 
'boost::unique_lock<boost::mutex>::swap(boost::unique_lock<boost::mutex>&)'     


/usr/include/boost/thread/locks.hpp:279:14: note: candidate is: void 
boost::unique_lock<Mutex>::swap(boost::unique_lock<Mutex>&&) [with Mutex = 
boost::mutex, boost::unique_lock<Mutex> = boost::unique_lock<boost::mutex>] 
<near match>




Original issue reported on code.google.com by [email protected] on 15 Jan 2011 at 6:11

Fix include in test suite

Hi.

I am working to package gpuocelot to Debian (at least, for my own purposes, 
but, perhaps, for inclusion in the upstream archive).

While doing so, I encountered a problem with the test suite, which wouldn't 
compile.

I am attaching a patch to fix (at least) this problem. There may be others, but 
I am still at the beginning of my journey trying to learn this CUDA thing.

BTW, I have a (very) preliminary Debian packaging.

Would you be interested in having it included in the tree, so that the 
instructions for users installing things become much simpler (and reproducible)?

I plan on doing the same thing for gpuocelot, once I get the prerequisites 
going.


Regards,

Rogério Brito.

Original issue reported on code.google.com by [email protected] on 7 Jan 2014 at 3:17

Attachments:

[bug] r185 introduces a compiler error

Hi,

with the r185 commit an error is introduced in the code. Line 242 in file 
"hydrazine/interface/ArgumentParser.h" changed to this: 
"if( identifier == str.size() )"
"identifier" and "str" are std::strings, so this comparison leads to 
compilation errors. 
I do not know exactly how the surrounding code works, so I cannot suggest a 
patch. Please provide a commit to fix this error.

Thanks,
jellysheep

PS: Find the diff here:
https://code.google.com/p/hydrazine/source/diff?spec=svn185&r=185&format=side&pa
th=/trunk/hydrazine/interface/ArgumentParser.h

Original issue reported on code.google.com by [email protected] on 4 Dec 2013 at 3:09

difficutly with instalation

Hi!

i am sorry to use issues but i need serious with instalation.

autoconf returns this:

"
configure.ac:14: error: possibly undefined macro: AM_INIT_AUTOMAKE
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
"

and automake returns this:

"

Makefile.am:16: library used but `RANLIB' is undefined
Makefile.am:16:   The usual way to define `RANLIB' is to add `AC_PROG_RANLIB'
Makefile.am:16:   to `configure.ac' and run `autoconf' again.
/usr/share/automake-1.11/am/depend2.am: am__fastdepCXX does not appear in 
AM_CONDITIONAL
/usr/share/automake-1.11/am/depend2.am:   The usual way to define 
`am__fastdepCXX' is to add `AC_PROG_CXX'
/usr/share/automake-1.11/am/depend2.am:   to `configure.ac' and run `aclocal' 
and `autoconf' again.
/usr/share/automake-1.11/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL
/usr/share/automake-1.11/am/depend2.am:   The usual way to define `AMDEP' is to 
add one of the compiler tests
/usr/share/automake-1.11/am/depend2.am:     AC_PROG_CC, AC_PROG_CXX, 
AC_PROG_CXX, AC_PROG_OBJC,
/usr/share/automake-1.11/am/depend2.am:     AM_PROG_AS, AM_PROG_GCJ, AM_PROG_UPC
/usr/share/automake-1.11/am/depend2.am:   to `configure.ac' and run `aclocal' 
and `autoconf' again.
"

theres no INSTALL instruction included

i have download it through subverion:

svn checkout http://hydrazine.googlecode.com/svn/trunk/ hydrazine-read-only

Original issue reported on code.google.com by pravod on 23 Sep 2012 at 5:38

libz.so not found under Mac OS X

What steps will reproduce the problem?
1. Compilation of a simple HelloWorld code with gpuocelot under Mac OS X
2. Execution

What is the expected output? What do you see instead?
Exception thrown, because the dynamic library libz.so cannot be found. Under 
Mac OS X it is called libz.dylib.


What version of the product are you using? On what operating system?
gpuocelot 2.0.969 with hydrazine included. 
Compiled with gcc (MacPorts gcc46 4.6.3_9) 4.6.3 under Mac OS X 10.8.2.
Installed through gpuocelot.

Please provide any additional information below.
A possible solution is to open the libz.dylib file instead of the libz.so file 
(hydrazine/implementation/compression.cpp).

33: void* libz = dlopen("libz.so", RTLD_LAZY); 

A check for both library names solves the issue.

Original issue reported on code.google.com by [email protected] on 18 Feb 2013 at 2:25

r76 fails to compile, because of a missing constructor

What steps will reproduce the problem?
1. Checkout r76 (the latest revision as of this ticket).
2. libtoolize; aclocal; autoconf; automake; ./configure; make

What is the expected output? What do you see instead?
I expect the build to succeed, but instead I get an error message stating that 
an Exception constructor does not exist:

g++ -DHAVE_CONFIG_H -I.    -Wall -ansi -pedantic -Werror -std=c++0x -g -O2 -MT 
libhydralize_a-XmlLexer.o -MD -MP -MF .deps/libhydralize_a-XmlLexer.Tpo -c -o 
libhydralize_a-XmlLexer.o `test -f 'hydrazine/implementation/XmlLexer.cpp' || 
echo './'`hydrazine/implementation/XmlLexer.cpp
hydrazine/implementation/XmlLexer.cpp: In constructor 
‘hydrazine::XmlLexer::XmlLexer(const std::string&)’:
hydrazine/implementation/XmlLexer.cpp:318:63: error: no matching function for 
call to ‘hydrazine::Exception::Exception(std::basic_string<char>, int)’
./hydrazine/implementation/Exception.h:21:4: note: candidates are: 
hydrazine::Exception::Exception(const std::string&)
./hydrazine/implementation/Exception.h:19:2: note:                 
hydrazine::Exception::Exception(const hydrazine::Exception&)
make[1]: *** [libhydralize_a-XmlLexer.o] Error 1
make[1]: Leaving directory `/home/kemal/src/hydrazine'
make: *** [all] Error 2


What version of the product are you using? On what operating system?
release 76 from SVN. Arch Linux carnifex 2.6.35-ARCH


Please provide any additional information below.

The file hydrazine/implementation/XmlLexer.cpp needs to call the correct 
constructor. I have attached a fix.

Original issue reported on code.google.com by [email protected] on 15 Sep 2010 at 1:17

Attachments:

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.