gcc 3.4 toolchain question

Amadeus amadeus at iksw-muees.de
Fri Oct 13 23:10:16 CEST 2006


Bradley,

On Friday 13 October 2006 22:33, Bradley Remedios wrote:
> So where are you in the whole porting effort, and what could I help
> out with wrt Pixil.  I was originally going to start on Pixil until I
> noticed that you were already working on it, so I would be happy to
> work with you.

The PIXIL sources are in the CVS now, and compile & link. 
There is another big problem in PIXIL: they are using the dlopen() call 
for plugin interfaces on 3 different places for small programs 
("APPLETS").

I have disabled these applets for now, but there must be a 
minimal-invasive patch to do some sort of "register" for the applets, 
and linking them all together...

Another problem is the keyboard on /dev/fb1 which must be switched off.

And then, the sysconfig applets must be adapted to the DSLINUX 
hardware...

> Because of that, I started to work on QTopia since I want to at one
> time at least try it out on the DS (even if at the end its determined
> to run to slow or not at all).

Hmmm.. very interesting. I have not enough time to do that.

> Since we both seem to have the same goals, maybe we can co-ordinate
> our efforts.  I don't mind leaving QTopia for now if it means that we
> can get a GUI up and running faster.

Hmmm... I have checked the include paths of g++ for a working compile 
and a nonworking compile. And I have used the "-H" option of gcc to 
display the include path for all included headers. There are millions 
of files....

Now I can compare the files and highlight the differences. And I will 
find the place where all these compiler errors come from. I doubt that 
this work can be splitted up. Maybe you can come up with a good 
solution for the dlopen() problem in the meantime?

regards
Amadeus
-- 
We're back to the times when men were men 
and wrote their own device drivers.

(Linus Torvalds)



More information about the dslinux-devel mailing list