Qt for Embedded Linux, minimum requirements not met, there is always a way

[knc1]

@NiLuJe : Do you like writing build systems in Make language?
I could clone YEM's development repository into my public repo system, then you send me a pub-key and we can both work on extending the unfinished parts of ct-ng.

[twobob]

Originally Posted by knc1

@NiLuJe : Do you like writing build systems in Make language?.

As a total OT. I am using this as my next chat-up line...

[knc1]

Originally Posted by twobob

As a total OT. I am using this as my next chat-up line...

I am always trolling for volunteers.
There is a limit before a crew of one worker (you) and one cheerleader (me) burns out.

[NiLuJe]

@knc1: I wouldn't say 'like' exactly, but I can somewhat make sense of it, sometimes... ;D.

What do you have in mind? Since I'm doing all of this for 'fun', I'm more likely to be of use if there's something that I actually have an interest in .

[knc1]

Originally Posted by NiLuJe

@knc1: I wouldn't say 'like' exactly, but I can somewhat make sense of it, sometimes... ;D.

What do you have in mind? Since I'm doing all of this for 'fun', I'm more likely to be of use if there's something that I actually have an interest in .

Let me give some thought about "goals" and get back to you.

If I can get something out that twobob can use, I will not be making any changes at all to ct-ng.

[knc1]

Originally Posted by NiLuJe

@knc1: What's the issue with CT-NG when building a GCC 4.7/Glibc 2.6/2.5 TC?

I am going to start with this bundled set of sources and ct-ng configuration . . . .
https://launchpad.net/linaro-toolcha...estone/2012.08
Then see if I can just "tweak" it for the older glibc.

Either this plan will "just work" and I will be done today . . .
OR I may not live long enough to get it working at all.

[NiLuJe]

@knc1: Huh, I wasn't aware of Linaro's ct-ng branch... (FWIW, I'm using upstream's ct-ng, it supports Linaro's GCC/GDB fine ).

Their sample softfp config is very similar to what I do for my K3/K5 TC, except I don't rely on their prebuilt lib/kernel, and I don't default to thumb mode (in fact, I've never used it, going by the assumption that thumb1 wasn't worth it... I might have to look into it for the K5, which supports thumb2...) .

[knc1]

Originally Posted by NiLuJe

@knc1: Huh, I wasn't aware of Linaro's ct-ng branch... (FWIW, I'm using upstream's ct-ng, it supports Linaro's GCC/GDB fine ).

Their sample softfp config is very similar to what I do for my K3/K5 TC, except I don't rely on their prebuilt lib/kernel, and I don't default to thumb mode (in fact, I've never used it, going by the assumption that thumb1 wasn't worth it... I might have to look into it for the K5, which supports thumb2...) .

I intend to only use their sources as a "known working set".

I have ct-ng_1.16.0 installed and I see that they used 1.13.1 (the same one Buildroot is stuck on).

I may or may not try moving the 1.13 config to 1.16

The other things you mention will go away in the "tweaking".

At least that is the initial plan. Will see how long that plan holds up.

[knc1]

Originally Posted by knc1

I am going to start with this bundled set of sources and ct-ng configuration . . . .
https://launchpad.net/linaro-toolcha...estone/2012.08
Then see if I can just "tweak" it for the older glibc.

Either this plan will "just work" and I will be done today . . .
OR I may not live long enough to get it working at all.

All the files listed on the linked page above are now mirrored in our DIY-KeK resource pool.
The resouce section (appendix B) of the reference manual has not (yet) been updated.

Now - take the sources that where used to build that release (K4&K5 style hardware) and cobble them into something suitable for the K3.

In the set of things:

[ps34532]$ tar --list -f gcc-linaro-arm-linux-gnueabihf-2012.08-20120827_src.tar.bz2 
gcc-linaro-arm-linux-gnueabihf-2012.08-20120827_src/
gcc-linaro-arm-linux-gnueabihf-2012.08-20120827_src/gmp-5.0.2.tar.bz2
gcc-linaro-arm-linux-gnueabihf-2012.08-20120827_src/newlib-1.19.0.tar.gz
gcc-linaro-arm-linux-gnueabihf-2012.08-20120827_src/libiconv-1.14.tar.gz
gcc-linaro-arm-linux-gnueabihf-2012.08-20120827_src/ppl-0.11.2.tar.lzma
gcc-linaro-arm-linux-gnueabihf-2012.08-20120827_src/gdb-linaro-7.4-2012.06.tar.bz2
gcc-linaro-arm-linux-gnueabihf-2012.08-20120827_src/md5sum
gcc-linaro-arm-linux-gnueabihf-2012.08-20120827_src/zlib-1.2.5.tar.gz
gcc-linaro-arm-linux-gnueabihf-2012.08-20120827_src/binutils-2.22.tar.bz2
gcc-linaro-arm-linux-gnueabihf-2012.08-20120827_src/precise-sysroot-armhf-1+bzr2433.tar.bz2
gcc-linaro-arm-linux-gnueabihf-2012.08-20120827_src/gcc-linaro-4.7-2012.08.tar.bz2
gcc-linaro-arm-linux-gnueabihf-2012.08-20120827_src/pkg-config-0.25.tar.gz
gcc-linaro-arm-linux-gnueabihf-2012.08-20120827_src/expat-2.1.0.tar.gz
gcc-linaro-arm-linux-gnueabihf-2012.08-20120827_src/mpc-0.9.tar.gz
gcc-linaro-arm-linux-gnueabihf-2012.08-20120827_src/cloog-ppl-0.15.11.tar.gz
gcc-linaro-arm-linux-gnueabihf-2012.08-20120827_src/mpfr-3.1.0.tar.xz

And the ct-ng is an archive of the entire build tree.
Including glibc and a zillion patches for the various sources.
This tool-chain can be re-built for an S390, but the question is, can it be re-built for an i.MX35?

Hmm...
Just need to dig around a bit to find a suitably old enough glibc set of sources.

[twobob]

rather exciting stuff mr knc!

[knc1]

Originally Posted by knc1

Just need to dig around a bit to find a suitably old enough glibc set of sources.

Not required.
The ct-ng patches directory is cumlative. It goes back to glibc-2.5 and gcc-4.3
The "oldest" that can be built / can build itself (gcc-4.2 is reported to be "too old" to build glibc these days).

Now, see how I do on the ct-ng learning curves. See if I can stay on the road course and not do a towbob (bump across the in-field).

Here is some of the curves in the course:
https://bugs.launchpad.net/linaro-toolchain-binaries
#1034186 is going to bite us - we have VFP, but no Thumb-2 on the i.MX35 - so don't expect gdb-server to work.