This forum has been archived. All content is frozen. Please use KDE Discuss instead.

compile warning/error GCC 3.3.4 for ARM

Tags: None
(comma "," separated)
cpylant
Registered Member
Posts
1
Karma
0
OS
Hello,

I'm working with a cross-compiler (running on Ubuntu x86, producing code for a modest ARM9 embedded computer).

The cross-compile is working fine for generic C++ projects.

But -- simple project which includes Eigen won't build.

Here's the code in question:

#include <Eigen/LU>
#include <Eigen/Array>
using namespace Eigen;

#define SIZE (200)

int main()
{
MatrixXf A = MatrixXf::Random(SIZE, SIZE);
VectorXf b = VectorXf::Random(SIZE);
VectorXf x;

A.lu().solve(b, &x);
...
}

And here's the warning/error report:

g++ -c main.cpp -I /home/chris/dev/eigen2
In file included from /home/chris/dev/eigen2/Eigen/Core:94,
from /home/chris/dev/eigen2/Eigen/LU:4,
from main.cpp:12:
/home/chris/dev/eigen2/Eigen/src/Core/util/XprHelper.h:39: warning: all member
functions in class `Eigen::ei_no_assignment_operator' are private
In file included from /home/chris/dev/eigen2/Eigen/Core:124,
from /home/chris/dev/eigen2/Eigen/LU:4,
from main.cpp:12:
/home/chris/dev/eigen2/Eigen/src/Core/Matrix.h: In member function `
Eigen::Matrix<_Scalar, _Rows, _Cols, _Options, _MaxRows, _MaxCols>&
Eigen::Matrix<_Scalar, _Rows, _Cols, _Options, _MaxRows,
_MaxCols>::_set(const Eigen::MatrixBase<OtherDerived>&)':
/home/chris/dev/eigen2/Eigen/src/Core/Matrix.h:508: error: parse error before `
;' token


The same code builds and runs perfectly under the native gcc shipped with Ubuntu.

Any clues?

Thanks!
User avatar
bjacob
Registered Member
Posts
658
Karma
3
Thanks for the report, this should now be fixed in the 2.0 branch (see the main wiki page for instructions how to get it).


Join us on Eigen's IRC channel: #eigen on irc.freenode.net
Have a serious interest in Eigen? Then join the mailing list!
ben2610
Registered Member
Posts
7
Karma
0
Hi, I'm having the exact same error in OSX 10.3 with gcc 3.3
I'm using the Eigen2 2.0.6 revision
I have updated the source but I see no change in it. Did you port the fix in 2.0.6? If not is it possible to do it?

thanks
ben2610
Registered Member
Posts
7
Karma
0
never mind my previous message, I've moved to using 2.0 as I see it contains various bug fix.
Thanks


Bookmarks



Who is online

Registered users: Bing [Bot], daret, Google [Bot], sandyvee, Sogou [Bot]