From: Mitch D. <mj...@au...> - 2000-05-10 06:29:24
|
Hello, This past weekend, I imported binutils, GCC and GDB into CVS. I have not had time to extensively test them, so I invite you to. Please note that the CVS name for GCC is "gcc-core". First, it's unclear about which versions to use, so I have used the versions that Greg and I found successful back in February. Unfortunately that means that the version in CVS won't have the most recent improvements, and we will have to do some updating over the next week or so. Here's a rundown on what I've done. (This is from memory, so I can't recall the version numbers). binutils: - Imported from the Cygnus binutils-000206 snapshot. - Applied the bfd fix. - Applied Kaz's patch from around that time. gcc-core: - Imported gcc-core-2.95.2. - Applied Kaz's PIC patch from around that time. - Applied Niibe's visibility patch from around that time. gdb: - Imported gdb-4.18. - Applied Kaz's gdb-sh patch from around that time. Kaz and Niibe (and others if necessary), here's what I recommend doing, if and when you want the tools in CVS to be updated to what you currently have. - Check out binutils/gcc-core/gdb. - Use "diff -u -r --new-file" then the name of the CVS-controlled dir, then the name of your local dir to produce a diff with the changes in it. - I would suggest using the diff "-x" flag to tell diff to ignore certain files, eg, "diff -x CVS -x '*~'" and so on, until the diff just has source differences. - Hand-edit the diff so it has the changes you want applied to CVS. - Mail it to me. I will then check this into CVS. Hopefully within a week the versions in CVS will be the latest and greatest and we can recommend that people start using them. If you have any questions, comments or suggestions, please don't hesitate to mail me. Regards, Mitch. -- | mailto:mj...@au... | Not the official view of: | | mailto:mj...@al... | Australian Calculator Opn | | Certified Linux Evangelist! | Hewlett Packard Australia | |