On Friday 08 September 2006 19:29, Tom Rini wrote:
> On Fri, Sep 08, 2006 at 01:26:48PM +0530, Milind Dumbare wrote:
> >     Moving weak definitions to some other new source file can also get rid
> > of this. We are working on it.
>
> Hmm.  Off-list Andrew suggested to me that it's time we make a
> lib/Kconfig.kgdb for all of our options and such.  I think what we need
> to do (and I'm going to try and do this shortly) is treat this like a
> __HAVE_ARCH_FOO type problem.  Except these general problems are moving
> towards CONFIG_ARCH_FOO and similar things (or implement it
> everywhere/asm-generic), so I'll go that route instead.

Both __HAVE_ARCH_FOO type or lib/Kconfig.kgdb should be fine. Could you please 
post it?

In the mean time I think it'll be good to checking a separate quick fix 
(forgcc-4.patch) with a README entry for the benefit of those who happen to 
run into these kinds of problems. It'll also help those who want to checkout 
for a previous version of KGDB (well, we can't checkin on a previous date, 
but nevertheless they can back port if they want to).
-Amit

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Kgdb-bugreport mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport

Reply via email to