Contributing code...

Contributing code...

[Scott Bambrough]

Hello,

My name is Scott Bambrough.  I work for Corel Computer, a division of Corel
Corporation that manufactures a small computer based on the DEC (now Intel)
SA110 processor.  Several  months ago, working with a some clever folks in
Great Britain we began to modify GCC 2.8.1, BINUTILS 2.9.1 and GLIBC 2.1 to
understand the ELF binary format on the ARM port of Linux we use on the
NetWinder.  Today we now have a complete functioning ELF Linux system allowing
to run XFree86, KDE, WordPerfect etc.  More to the point for this list, is the
fact that I modified GDB 4.17 to run on the NetWinder and would like to
contribute these changes to the open source community.

A copyright assignment for GLIBC was signed November 25 for GLIBC and all our
changes have now been integrated into the CVS source tree. I received word on
December 11 that the Corel now has copyright assignments in place for GCC,
BINUTILS, and GDB.  So that leads me to following: I would like to contribute
the code if you are interested.

Let me describe what I did to accomplish this.  I took the released GDB 4.17
distribution, and moved the gdb, readline and sim subdirectories into my
binutils tree and started from there.  I know the porting manual says not to
do this, but the number changes required to BFD and time constraints precluded
any other choice.  I then started with the target for Acorn RISCOS machines. 
I tried to separate what was there into ARM specific code and Acorn specific
code and then added a new target, host for ARM Linux.  I then added any code
required for the NetWinder and the Linux kernel use at the time and voila
after some heartache I had a working debugger.

My patches are not based on the latest snapshot, and are admittedly not
perfect.  But if no one is working on this and you are interested I would like
to contribute my code, fix up the problems, and actively maintain the port. 
Assuming you are interested, and no one else is working on it (there wasn't in
the last snapshot, but I haven't checked the one announced today) what is the
best way to approach this.

Let me know if you are interested in the code.  Looking forward to hearing
from you.

Seasons Greetings,

Scott Bambrough
CCC

Re: Contributing code...

[Stan Shebs]

   Date: Wed, 16 Dec 1998 23:28:04 -0500
   From: "Scott Bambrough" <scottb@corelcomputer.com>

   My name is Scott Bambrough.  I work for Corel Computer, a division of Corel
   Corporation that manufactures a small computer based on the DEC (now Intel)
   SA110 processor.  Several  months ago, working with a some clever folks in
   Great Britain we began to modify GCC 2.8.1, BINUTILS 2.9.1 and GLIBC 2.1 to
   understand the ELF binary format on the ARM port of Linux we use on the
   NetWinder.  Today we now have a complete functioning ELF Linux system allowing
   to run XFree86, KDE, WordPerfect etc.  More to the point for this list, is the
   fact that I modified GDB 4.17 to run on the NetWinder and would like to
   contribute these changes to the open source community.

Cool!  I'd certainly like to get these into 4.18 if possible!

   A copyright assignment for GLIBC was signed November 25 for GLIBC and all our
   changes have now been integrated into the CVS source tree. I received word on
   December 11 that the Corel now has copyright assignments in place for GCC,
   BINUTILS, and GDB.  So that leads me to following: I would like to contribute
   the code if you are interested.

I don't think I've seen a note from the FSF yet, but sometimes it takes
a couple weeks.

   My patches are not based on the latest snapshot, and are admittedly not
   perfect.  But if no one is working on this and you are interested I would like
   to contribute my code, fix up the problems, and actively maintain the port. 
   Assuming you are interested, and no one else is working on it (there wasn't in
   the last snapshot, but I haven't checked the one announced today) what is the
   best way to approach this.

Send your diffs (-p preferably) from the base version you started
with, to gdb-patches@cygnus.com, and we can start sorting things.  If
you could spare some time to look at a recent snapshot and see how
your patches would play with that, it would help in speeding things
along.  Martin Hunt (hunt@cygnus.com) has expressed a special interest
in this, feel free to correspond with him directly also.

Thanks again for contributing to GDB!

								Stan