taskwarrior (REQUIRES KTERM)

[nasser]

Originally Posted by encol

In your environment, what's the

gcc --version

output?

4.6.3

[knc1]

Originally Posted by nasser

4.6.3

I don't recall if that is one of them, but there are some compiler version early in the 4.x series that are to be avoided due to mis-compilations on ARM.

Your best bet is to use Linaro (sp?) ARM compilers -
They are the leading maintainer of the GCC/ARM compiler(s).

Current:
https://releases.linaro.org/componen...naries/latest/

A little digging will get you earlier GCC series releases (back to early 4.x IIRC - nobody in their right mind keeps any 3.y stuff around).

Edit:
Back to 4.9:
http://releases.linaro.org/component...hain/binaries/

And the fog clears a bit - it was the versions upto 4.8 that had problems.
So to avoid those, and be most likely to compile the very old sources used in the Kindle system, pick from here:
http://releases.linaro.org/component...linux-gnueabi/

[nasser]

knc1,
I used gcc 4.6.3 under the debian-wheezy-armel qemu image running under Ubuntu 14.04.
Was able to compile the popeye chess application.
The compiled executable runs OK both on the qemu VM as well as on PW1 and PW3.

The latest version of this thread's application, however requires a C++11 compliant gcc( at least 4.7), which the debian-wheezy-armel repository doesn't seem to have.

[encol]

check here

[nasser]

Thanks, encol!
Will try it.
Don't know why they can't make it accessible through apt-get?

[knc1]

Originally Posted by nasser

knc1,
I used gcc 4.6.3 under the debian-wheezy-armel qemu image running under Ubuntu 14.04.
Was able to compile the popeye chess application.
The compiled executable runs OK both on the qemu VM as well as on PW1 and PW3.

The latest version of this thread's application, however requires a C++11 compliant gcc( at least 4.7), which the debian-wheezy-armel repository doesn't seem to have.

"Works for me" doesn't cover all use cases.
You would have to check either the bug reports and/or the changelog of the following versions to find out what feature of the source code causes the problem.
And then test that on your specific compiler.
Unless you built it yourself, you don't know what all patches had, or had not, been applied.

My recounting known history is not a directive - people can still make up their own mind.

[nasser]

Originally Posted by nasser

Thanks, encol!
Will try it.
Don't know why they can't make it accessible through apt-get?

Downloaded and installed gcc-4.7 & g++-4.7.
Since they installed into the non-standard /usr/bin, also entered EXPORT CC= and CXX= the actual paths in /usr/bin
But the cmake script still says no C++11 support and advises to upgrade compiler, though it is able to recognise both the versions and locations.
The install help file in the package clearly states v 4.7 is sufficient.

[knc1]

Originally Posted by nasser

Downloaded and installed gcc-4.7 & g++-4.7.
Since they installed into the non-standard /usr/bin, also entered EXPORT CC= and CXX= the actual paths in /usr/bin
But the cmake script still says no C++11 support and advises to upgrade compiler, though it is able to recognise both the versions and locations.
The install help file in the package clearly states v 4.7 is sufficient.

Check if it automagically pulled in libstdc++ for that version of the compiler.
Having that missing will break C++
It is possible that the direction writer had a system where the installation of libstdc++ was automated (they did it, but didn't know about it).

{You just gotta love these puzzles to be a software developer. Some people even do this for a living.}

[nasser]

I installed libstdc++ manually, after(I think) the GCC or G++ installs mentioned it as a dependency.
Have raised a bug on the taskwarrior forum. Let me see...

[encol]

post

dpkg-query -l 'libstdc++*' | grep ii

[nasser]

Originally Posted by encol

post

dpkg-query -l 'libstdc++*' | grep ii

root@debian-armel:~# dpkg-query -l 'libstdc++*' | grep ii
ii  libstdc++6:armel     4.7.2-5    armel     GNU Standard C++ Library v3 
ii  libstdc++6:armel     4.7.2-5    armel     GNU Standard C++ Library v3 (development files)

[knc1]

can not say.
you only posted: "4.7" not the specific version (4.7.?.?-?)
so use the same command (changing the target name of course) to see if the compiler's full version matches the library's full version.

[nasser]

Originally Posted by knc1

can not say.
you only posted: "4.7" not the specific version (4.7.?.?-?)
so use the same command (changing the target name of course) to see if the compiler's full version matches the library's full version.

GNU C compiler  4.7.2-5
GNU C++ compiler 4.7.2-5
GCC, the GNU Compiler Collection (base package)   4.7.2-5

[knc1]

Originally Posted by nasser

GNU C compiler  4.7.2-5
GNU C++ compiler 4.7.2-5
GCC, the GNU Compiler Collection (base package)   4.7.2-5

That looks like it should work.
Have c++ report where it is looking for externals -
as in (for gcc):
gcc -v -o junk junk.c

Hmm...
I think that will also give you the information you might need if you try compiling /dev/null as the source code.
Compiling /dev/null does have its uses.

[nasser]

Got a pile of messages:
COMPILER_PATH= ....
.......
LIBRARY_PATH= .....
.....
COLLECT_GCC_OPTIONS= .....