My Attempts To Build Qt4, The Qt4 Odyssey Options

[adf]

[yeah..updating the libs (and hopefully passing them back into pdaxii13) might be agood idea.

[ernestus]

It looks like the kernel guys would like to have a newer compiler as well, so I am here, well after midnight building a toolchain

[ScottYelich]

I'm waiting anxiously -- I haven't upgraded my my zauruses in about 2 years now.
Having Qt4 available would be the trigger for me to upgrade.

Scott

[Civil]

By the way, I've managed to compile qt-4.3.0 on my zaurus's gentoo (glibc 2.5, gcc-4.1.2, eabi).

[kkazakov13]

By the way, I've managed to compile qt-4.3.0 on my zaurus's gentoo (glibc 2.5, gcc-4.1.2, eabi).

And ... ? We all know it compiles everywhere else , except pdaxrom

[ernestus]

By the way, I've managed to compile qt-4.3.0 on my zaurus's gentoo (glibc 2.5, gcc-4.1.2, eabi).

And ... ? We all know it compiles everywhere else , except pdaxrom

Not for too long, I hope

[ernestus]

Some problems compiling glibc
=========================

Well, I managed to compile:
1 - The last binutils,
2 - The last GCC (4.2.1, released just 4 days ago, without glibc support)

so the two other steps needed to have the complete toolchain are:

3- Compiling glibc (this is the problematic point read more)
4- Compiling GCC 4.2.1 again with glibc support (to be honest, once point 2 has succeeded, I don't expect problems here)

The amazing case of the problematic point 3
----------------------------------------------------------------

Well, when the build of glibc failed I thought it was related to GCC 4.2.1, many times, the latest compiler is not able to compile glibc, so I tried to build it with the 3.4.6 tool chain available somewhere in the forum, with the same result.

I am quite sure the problem is related to the unexistence of glibc-linuxthreads-2.6, does anyone know what happened to it, I cannot find it anywhere? I am tempted to use the one for glibc 2.5 instead (will try this evening), but I am reluctant to do so, because of the possible stability issues (may trigger very difficult to find bugs, thread related issues are very hairy matters)

I may go back to glibc 2.5 (but, this is not the COOLEST, LATEST and GREATEST release)

Choosing the target
----------------------------

Another question, I've built the compiler with options for softfloat and xscale, there is another very interesting one iwmmx:
- does anyone know what is the difference of compiling for a iwmmx target insead of a xscale one? both are exclusive, OR you compile for a xcale target OR you compile for a iwmmx target, not both. My guess is that choosing the iwmmx target may produce code able to run in iwmmx enabled PXA's but not in others, but I may be wrong.
- how can it render the compiler incompatible with older pxa devices?

Any hint is appreciated.

thanks all
E

[Civil]

I am quite sure the problem is related to the unexistence of glibc-linuxthreads-2.6

Linuxthreads was removed. Use NPTL instead of it.

Another question, I've built the compiler with options for softfloat and xscale, there is another very interesting one iwmmx:
- does anyone know what is the difference of compiling for a iwmmx target insead of a xscale one? both are exclusive, OR you compile for a xcale target OR you compile for a iwmmx target, not both. My guess is that choosing the iwmmx target may produce code able to run in iwmmx enabled PXA's but not in others, but I may be wrong.
- how can it render the compiler incompatible with older pxa devices?

armv5te compiler can generate code with march=iwmmxt, march=xscale and march=armv5te.

[ernestus]

I am quite sure the problem is related to the unexistence of glibc-linuxthreads-2.6

Linuxthreads was removed. Use NPTL instead of it.

Yes, I do, but the compilation then fails because of undeclared symbols that I think are related to linuxthreads. Maybe I need a header or something like that.

I will post the precise error tonight.

[speculatrix]

qt4.4 is out!
http://www.linuxdevices.com/news/NS8928092497.html