This may be a random thought, but... I believe the Lynx OS was set up for embedded use. As such, it may be optimized for relatively small memories and this may carry over to display support. Would TinyX be easier to start from? Paul Sherman Biomedical Engineer VA Center for Engineering & Occupational Safety and Health (CEOSH) St. Louis, MO Paul.Sherman@med.va.gov > -----Original Message----- > From: Adrian Wild [SMTP:adw@primagraphics.co.uk] > Subject: XFree86 cross development > > I have succesfully built XFree86 for various linux target platforms (intel > and power pc) but I am now trying to build XFree86 for a LynxOS (3.1.0) > powerpc platform. I have tried to build a native XFree86 on a Motorola > MVME2604 701 ppc with 32M of ram but seem to have problems in linking > certain "large" objects - there seems ot be a limit of 16M which causes > failure (note I have tried this with a lot of virtual memory, e.g. 128M, > 1G etc..) and I guess is specific to the ppc or Lynxos kernel but cannot > seems to find any mention of such a limitation anywhere. I therefore > resorted to cross-compiling off a sun host and I am having problems, > specifically:- > > 1) ensuring the correct compiler is being used at the approriate time in > the build of XFree86 (e.g. in generating the makefile for the host and > object files for the target) > 2) using the correct .def configuration files for the host/target at the > at the approriate time in the build of XFree86. > > Has XFree86 been build in any similar cross-development evironment? and > can anyone shed light onto the why the MVME2064 host build of Xfree86 with > Lynxos 3.1.0 suffers from an apparent 16M limit? > > Any help would be greatly appreciated > > Adrian D.W. _______________________________________________ Newbie@XFree86.Org *** To unsubscribe , or change message options, see: http://XFree86.Org/mailman/listinfo/newbie
