On 09.05.2011 00:01 Wolfgang Denk said the following: > Dear Michael Steiger, > > In message<[email protected]> you wrote: >> >>> I don't see any information that glibc-debuginfo ever existed on any >>> of the mirrors. If you follow the thread, the OP confirmed that he >>> rebuilt the whole ELDK from scratch. >> >> I've seen it but hoped that this file exists somewhere >> >> I assume that you have a build environment setup. Would it be possible >> to create the missing debuginfo file if you can not find it in the backup? > > It's software, so everything is possible. It's just a matter of the > required efforts, and who is paying for these.
I have now tried to find the correct way to get this damned file. The valgrind error message says The package you need valgrind: to install for fix (1) is called valgrind: valgrind: On Debian, Ubuntu: libc6-dbg valgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo I have absolutely no experience compiling linux components including glibc or gcc or ... I can not find a package glibc-debuginfo in the eldk sources and all other SRPMS I have compiled and checked do not contain ld.so* The only glibc-debuginfo I can find on the net is for x86 and a different version eldk is using. I am willing to spend my time to learn about it but could you please tell me what I really have to do to get this beast? > When talking about efforts, we should also decide if it's really worth > putting work into theold ELDK 4.2 release, or if the same effort > should not rather be spent to create a powerpc-spe configuration of > ELDK 5.0 instead. The supplier of the board we are using supports ELDK 4.2 so I can not switch to another release at the moment. BTW, did you find anything in your old backup? Thanks Michael _______________________________________________ eldk mailing list [email protected] http://lists.denx.de/mailman/listinfo/eldk
