Register Guidelines E-Books Search Today's Posts Mark Forums Read

Go Back   MobileRead Forums > E-Book Readers > More E-Book Readers > iRex > iRex Developer's Corner

Notices

Reply
 
Thread Tools Search this Thread
Old 04-24-2007, 06:39 AM   #1
tororebelde
No es el toro que piensas
tororebelde began at the beginning.
 
tororebelde's Avatar
 
Posts: 44
Karma: 10
Join Date: Mar 2007
Device: iRex iliad
Is possible a new toolchain with updated libc?

Hi all,

After spent some days to try to compile qt-embedded and qtopia under out beloved vmware enviroment I reached to know why I wasn't able to compile them

When configure compiles qmake (a esential qt tool) and extrange error arises:

qlocale.o(.text+0x116e4): In function `qdtoa(double, int, int, int*, int*, char**, char**)':
: warning: warning: feholdexcept is not implemented and will always fail
qlocale.o(.text+0x1172c): In function `qdtoa(double, int, int, int*, int*, char**, char**)':
: warning: warning: fesetenv is not implemented and will always fail

but process continues (as is just a warning). When configure ends, do a make. It start building libraries until the src/gui directory is reached, then the following happens:

/home/developer/qtopia-core-opensource-src-4.2.3/bin/qmake -spec ../../mkspecs/qws/linux-generic-g++ -unix -o Makefile gui.pro
free(): invalid pointer 0xa18dd44!
free(): invalid pointer 0xa18dd10!
make[2]: *** [Makefile] Error 126

Funny, isn't it?

Ok, I found that this may come from the libc libraries we are using because they are 2.3.3 (Antartica's toolchain). Of course if I try to compile the Qt libs under my home distro there's no problem (I'm using libc 2.3.6)

Very suspicious ... At this point is when I got a problem, because don't know if could be possible to update the libc libs we are using to compile (at scratchbox).

I will still do tests to give you a working Qt libs for iLiad, but if someone can help me I'll appreciate it!

I'll also communicate any new advance ...

Javier
tororebelde is offline   Reply With Quote
Old 04-24-2007, 09:25 AM   #2
Adam B.
Addicted to Porting
Adam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the rough
 
Adam B.'s Avatar
 
Posts: 1,695
Karma: 7194
Join Date: Oct 2006
Location: Indianapolis, IN
Device: iRex iLiad, Nokia 770, Samsung i760
Pardon my ignorance, but why not just download, compile, and install libc within the scratchox environment?
Adam B. is offline   Reply With Quote
Old 04-24-2007, 10:03 AM   #3
Antartica
Evangelist
Antartica has learned how to read e-booksAntartica has learned how to read e-booksAntartica has learned how to read e-booksAntartica has learned how to read e-booksAntartica has learned how to read e-booksAntartica has learned how to read e-booksAntartica has learned how to read e-books
 
Posts: 415
Karma: 754
Join Date: Jun 2006
Location: Madrid, Spain
Device: iliad, onhandpc, newton, zaurus
Quote:
Originally Posted by tororebelde
Ok, I found that this may come from the libc libraries we are using because they are 2.3.3 (Antartica's toolchain). Of course if I try to compile the Qt libs under my home distro there's no problem (I'm using libc 2.3.6)

Very suspicious ... At this point is when I got a problem, because don't know if could be possible to update the libc libs we are using to compile (at scratchbox).
Adam is right. You can compile another libc alongside the one installed in the scratchbox environment (AFAIK, Adam did it for gnumeric), and compile/link against it.

The toolchain has such an old version so as to be compatible with the one included in the iliad firmware.

It is rather easy to generate another toolchain with an up-to-date libc, but as it would not be compatible with the iliad firmware, one would have to include it with every program (and it's somewhat large).

Perhaps in the future when Matthijs et al release the flashing procedure, we can arrange a firmware with a more recent libc, but until then, I think that it's better to do what Adam proposes.

Good luck with the port!
Antartica is offline   Reply With Quote
Old 04-25-2007, 02:29 AM   #4
tororebelde
No es el toro que piensas
tororebelde began at the beginning.
 
tororebelde's Avatar
 
Posts: 44
Karma: 10
Join Date: Mar 2007
Device: iRex iliad
Quote:
Originally Posted by Adam B.
Pardon my ignorance, but why not just download, compile, and install libc within the scratchox environment?
Oh, really I think is MY ignorance that I wasn't aware I can do that without troubling with the scratchbox environment

Quote:
Originally Posted by Antartica
The toolchain has such an old version so as to be compatible with the one included in the iliad firmware.
Yeh, that's the same I thought. And you're right: it increases the size of our future distributed apps until we can update some libs on iliad without worrying about get a bricked device, but just I'm want to get a functional Qt application running on iliad, and if I get it I will be a very very happy iliad user

Quote:
Originally Posted by Antartica
Good luck with the port!
Thanks dudes! I will soon send you my progress / contributions.
tororebelde is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
updated metadata=updated file? jomaweb Calibre 13 01-28-2010 08:12 PM
Toolchain Problems benjaminvm Sony Reader Dev Corner 3 12-02-2008 10:03 PM
iLiad How to build iPDF with toolchain? ericshliao iRex Developer's Corner 2 01-23-2008 11:15 AM
iLiad now in the wiki: iliad unofficial toolchain Antartica iRex Developer's Corner 22 12-26-2007 05:27 AM
iLiad iPDF and Toolchain Sources Updated Adam B. iRex Developer's Corner 0 12-08-2006 08:42 AM


All times are GMT -4. The time now is 10:05 AM.


MobileRead.com is a privately owned, operated and funded community.