This is the mail archive of the
gdb@sourceware.cygnus.com
mailing list for the GDB project.
Re: RDI target patch question
- To: grante at visi dot com
- Subject: Re: RDI target patch question
- From: Stan Shebs <shebs at cygnus dot com>
- Date: Mon, 25 Oct 1999 14:09:13 -0700
- CC: gdb at sourceware dot cygnus dot com
Date: Mon, 25 Oct 1999 14:13:21 -0500
From: Grant Edwards <grante@visi.com>
I've gotten my RDI target changes cleaned up to the point where
they're only a minor embarrassment, and I want to generate a patch
against 4.18.
Excellent!
I have two questions:
1) One of the changes involved renaming rdi-share/endian.h
to rdi-share/anendian.h. Is there way to generate a patch that,
in effect, renames a file?
I think I might be able to come up with a patch file that does
this, but it would have to delete every single line from the old
file and insert it into the new one. Thus the patch file would
contain two copies of the entire contents of the renamed file.
This seems a bit inelegant.
I suppose it looks a little funny, but the two copies is the usual way
to go. If you use diff -N, you will get the right thing automatically,
and I'll be able to cope with it.
1) I modified rdi-share/Makefile.in so that the Makefile
generated by configure contains the renamed include file.
I tried to changing Makefile.am and regenerating Makefile.in
using automake, but at the end of the process I never ended
up with a Makefile that worked.
Should I just make corresponding changes by hand to Makefile.in
and Makefile.am and generate a patch from that?
You may be getting hosed by a combination of autofoo versions and
random stuff found in your path. I usually debug by diffing
generated files from before and after the change, sometimes you
find changes you didn't expect...
In any case, yeah, make the right changes manually. I'll do a bit
of checking before committing the changes.
Stan