Hi Philippe, The configure problem is solved and get the nightly version built, now I guess it's good to go. Struggling in setup the developing, debugging and testing environment now, I got some help from IRC, hopefully could figure out a good way to editing code, build image, load it up and do the test and validation in the coming days. Do you have any suggestion about it? Thanks! Have a good day! George On Thu, Mar 24, 2011 at 6:26 PM, George zhao <raimann.zhao@xxxxxxxxx> wrote: > Hi Philippe, > > Thank you for you reply, and really glad to get so much information from you. > >> Haiku used to have a working PPP stack some years ago, but due to a >> major (and welcome) network stack redesign, it doesn't compile anymore >> and was not ported to new API since. One thing to keep in mind for >> this project is that Haiku network stack is not plain C but "kernel" >> C++, including the previous PPP code, and only the public interface >> between modules are C ones. So you must be skilled enough in C++ >> (included templates), not only C. >> Your experience with PPPoA and PPPoE is definitively a plus ;-) > > About this working PPP stack, is it possible to get that working haiku > version now? It will be help to get a "hello world" PPP link running > at the beginning point, and for the future development. I can look > into the packet during the LCP and IPCP negotiation in the future for > the debugging sake, I think. > > For a debugging environment, does the current system support the step > by step debugging using a GDB server? Can you give me some information > about it. > > In general I have experience in the developing C++ program. Honestly > speaking, in the industry level, I don't have much C++ background, but > I've been using C++ intensively for various project during my > undergraduate(4 years) and PhD program(almost 3 years now). I will > read the current implementation of the whole system, and try to catch > up with the coding style in the student guidance page of the haiku > website, and as long as we get the design part done, I think it will > not be a problem once we come to the coding part. > >> You'll find the current network stack code here: >> >> http://dev.haiku-os.org/browser/haiku/trunk/src/add-ons/kernel/network >> http://dev.haiku-os.org/browser/haiku/trunk/headers/private/net >> (internal headers) >> >> The broken/not-yet-ported PPP sub-stack is here: >> http://dev.haiku-os.org/browser/haiku/trunk/src/add-ons/kernel/network/ppp >> > > Thank you for pointing out the project fold to me. For this part, do > you have any design specification of the PPP module in pocket? The > code is well wrote, I think. Even though I don't have much time to dig > into it, it looks good at the first sight. I saw PPP PAP is there, and > didn't find PPP CHAP, does it mean that in the previous implementation > there is no CHAP module. If it does, then PPP CHAP can be a new > feature to implement during the summer. What do you think? > >> It may not be obvious, but please don't use our last "official" >> r1/alpha2 release as your development target. >> Since this release, a lot of things were changed in Haiku, both on >> content *and* build system. >> Please use instead some recent nightly releases. Another official >> release, dubbed r1/alpha3 is scheduled before GSoC starts, so in every >> case the target will be more recent thant r1/alpha2. >> >> Don't forget that the code of any Haiku's GSoC projects should build >> and run well with both gcc2 and gcc4 ABI, >> so use a gcc hybrid build and get used to build your component for both. >> Read on our web site how to build Haiku (or part of it) for gcc2 or gcc4. > > For the configure checking, I believe that I get all the essential > apps installed in the Snow Leopard, but it always failed in lacking > some .h files, for the gcc2 and gcc4 checking, during the ./configure > execution. Does current cross compiling supports Mac Snow Leopard? I > have installed the Xcode 3 and the latest binutils. Or I have to get > an Ubuntu or Suse to start with, which are the only two systems I can > get up to now. Thanks! > > > Thank you for your time, and have a good day! > George > > > >