Dear Wolfgang, On Sat, 15 Sep 2012 10:59:04 +0200 Wolfgang Denk <[email protected]> wrote:
> Dear Sergei, > > In message <1347698143.3627.27.camel@mehome> you wrote: > > > > > Thnaks for pointing out. Do you see any problems with the demo > > > programs, except for this warning message? > > > > We are just tried to start the application, it was one of the first > > attempts to try out our kernel port with the real filesystem. The > > framebuffer driver is not yet ready so we didn't expect much of that > > attempt. > > > > > I mean, is it just a nuisance, or a real problem? > > I understand you cannot answer this yet? > Yes, correct. > In my tests, I don't remember any such message, so I wonder what the > difference might be... > I did "ldd" to the application and didn't notice direct dependency on the libicu library in the list. Apparently, it is loaded at runtime by dl_load(). I'd think it's something in the default environment which triggers dl_load() on libicu. Anyway, libicu isn't present on the qte-sdk image, unlike of the "basic" image. > > BTW, is there a package in the ELDK-5 which allows to quick-start > > the ramdisk development, like the SELF package in ELDK-4? > > That would be the core-image-minimal image, for example. > Thanks. Regards, Sergei > Best regards, > > Wolfgang Denk > _______________________________________________ eldk mailing list [email protected] http://lists.denx.de/mailman/listinfo/eldk
