Mohan Kumar M <[EMAIL PROTECTED]> writes: > On Thu, Jul 27, 2006 at 11:14:18PM -0600, Eric W. Biederman wrote: >> >> If you can compile the ppc64 code could you please track down >> what undefined symbol in ppc64 purgatory code is? >> >> Unless I can find a good explanation I'm going to reinstitute >> the die when undefined symbols are detected which will kill break >> ppc64. >> > > Hi Eric, > > I will be looking into the issue PPC64 purgatory undefined symbols.
Thanks. The reason I am concerned is that in all cases I have observed an undefined symbol in purgatory is a code bug. Because purgatory is a standalone executable. Having a way to check that at compile time would be ideal, but at least previously we were catching these bugs at run time. > Regarding the gcc 4.1 issues, how we can get rid of those warnings if we need > to > remove casts? Change the types of the data we are dealing with. In general warnings are much better than putting in casts to squelch warnings about mixing signed and unsigned pointers. Eric _______________________________________________ fastboot mailing list [email protected] https://lists.osdl.org/mailman/listinfo/fastboot
