tettoffensive wrote:dave, i sent you that binary a while back and it didn't work on the labs computers i guess cause they're centos. I'll send it to you again tonight if you don't have it.
as for the autoconf/automake. That is a build system for compiling.
First off thanks a lot! Unfortunately that's what I had tried before posting and I get the following error...admin wrote:stuart updated the wiki, let me know if that helps
DLFLFile.cc: In member function ‘void DLFL::DLFLObject::writeObject(std::ostream&, bool, bool)’:
DLFLFile.cc:153: error: ‘makeVertexUnique’ was not declared in this scope
make[1]: *** [DLFLFile.o] Error 1
make[1]: Leaving directory `/topmod/topmod/include/dlflcore'
make: *** [sub-dlflcore-make_default] Error 2(I have python 2.5 installed)./TopMod: error while loading shared libraries: libpython2.5.so.1.0: cannot open shared object file: No such file or directory
./TopMod: error while loading shared libraries: libpython2.5.so.1.0: wrong ELF class: ELFCLASS64
DLFLFaceVertex.hh: In member function ‘void DLFL::DLFLFaceVertex::assignID()’:
DLFLFaceVertex.hh:97: error: cast from ‘DLFL::DLFLFaceVertex*’ to ‘unsigned int’ loses precision
In file included from DLFLCommon.cc:43:
DLFLObject.hh: In member function ‘void DLFL::DLFLObject::makeEdgesUnique()’:
DLFLObject.hh:359: error: cast from ‘DLFL::DLFLEdge*’ to ‘unsigned int’ loses precision
DLFLObject.hh: In member function ‘void DLFL::DLFLObject::makeFacesUnique()’:
DLFLObject.hh:370: error: cast from ‘DLFL::DLFLFace*’ to ‘unsigned int’ loses precision
DLFLObject.hh: In member function ‘void DLFL::DLFLObject::addEdgePtr(DLFL::DLFLEdge*)’:
DLFLObject.hh:414: error: cast from ‘DLFL::DLFLEdge*’ to ‘unsigned int’ loses precision
DLFLObject.hh: In member function ‘void DLFL::DLFLObject::addFacePtr(DLFL::DLFLFace*)’:
DLFLObject.hh:426: error: cast from ‘DLFL::DLFLFace*’ to ‘unsigned int’ loses precision
make[1]: *** [DLFLCommon.o] Error 1I have no experience with c/c++ but had a quick go trying to make changes as per your example and it seems to work. There's a lot to be change and before I spend to much time on this do theses changes effect windows or osx? In other words if I made a patch with them all split like your example could it be added to the svn with out any problems?dave wrote:this error(s) occur, since there are a lot of friend functions IMPLEMENTED inside a class definition, where they should only be declared there. Friend function should be implemented outside the class.
As they are implemented inside the class they belong to that namespace, but as the are NOT part of the class itself (just friends) they can't be resolved by g++.
example :
instead of writing
class A
{
.....
.....
friend void foo_bar()
{
..... some code .....
}
}
it should be
void foo_bar();
class A
{
.....
.....
friend void foo_bar();
....
}
void foo_bar()
{
..... some code .....
}
trying to compile the provided source I ran into the same problem, i tried to solve this, but since this coding behaviour is spilt all over the code I resigned this try for the meanwhile.
Maybe their are some other fancy workarounds for that problem, as it seems to be an g++ specific problem.
Users browsing this forum: No registered users and 2 guests