Hi Alexander, On Monday 28 May 2007 15:21:54 Alexander Neundorf wrote:
> for testing purposes I need a cross compiling environment (architecture > doesn't really matter, it should be != x86) which has the mesa libs. I saw T2 > at Cebit and so I thought I'd try to do this with T2. > > I tried several things last week but didn't get so far to get something with > mesa built. > > I'd like to have > -a basic system > -some graphic libs (jpeg, png, jasper) > -mesa > > X and desktop are not required. > > I got quite far with "Generic System" for PowerPC, the base system > built, "mine" failed (because of including something from /usr/include) but I > didn't find mesa. Build-Pkg mesa started to work, but failed because there > was no X. I didn't find a way to build X. > > My other attempts didn't get so far. The Dreamcast target failed because in > the generated kernel some numeric value didn't match with the expected value, > for some other targets I got an assertion in bash, malloc.c. > > This is on kubuntu 6.10 Edgy Eft. > > So which target should I chose ? Generic, Exact Desktop or something else ? The Generic and Desktop ones are designed for native buidls, that is where any T2 package can built after the initial boot- strapping. However for a "I do not care to run the resulting system and just need Mesa, the generic target would still be ok. Usually the embedded one would be a better cross compile pre-definition, but it intentionally does not allow choosing glibc, ... so you would end up with a Mesa linked against uclibc. So: choose generic select the "this is a cross build option" (this will limit the packages and configuration to just that what is known to cross build). However, (at least at ExactCODE) we did not yet needed Mesa cross-build. I'm not sure if the Mesa as setup in T2 will cross build. If you use T2 you will at least need to add this to the mesa.desc file: [F] CROSS To flag it as "known to cross build" > For which processor: PPC, Sparc, ARM ? They are all in use by T2 developers, so they shoudl all be fine. > If the base system builds, how can I build mesa after that ? If you do not want to do this manually, you should let T2 just build it for you. Add the CROSS flag and press your thumbs :-) > I don't need an installation CD or iso, I just need the environment installed > on my machine so I can link to it when cross compiling. Ok. Maybe just post build errors you run into here and we can take a look. As you made me aware that T2 might not yet be able to cross build Mesa I'll setup a local test build for the generic+minimal+cross here as well to see how it goes. I cross my fingers and do not hesitate to ask about whatever obscure build error you might notice on-the- way. Have fun, René -- René Rebe - ExactCODE GmbH - Europe, Germany, Berlin http://exactcode.de | http://t2-project.org | http://rene.rebe.name
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe t2
