This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 17. feb. 2011 17:41, ng@piments.com wrote: > On 02/15/11 16:07, Per Arnold Blåsmo wrote: >> Have a look at http://distribute.atmel.no/tools/opensource/ >> for some patches. I added gdb 6.7.1 patches. > > > Thanks Per, it looks like that is more upto date than what I was using > from the other download. > > > All: > > I added usual structures at the same level as the stock ct-ng patch > directory and added the patches . ct-ng build started well and binutils > patches all applied cleanly , but then it got confused in gcc-4.3.3. > The patches is applied using the following code: function apply_patches() { local workdir=$1 local patchdir=$2 do_pushd ${workdir} # Patch Categories # 0x = Distribution specific (distro names and versions) # 1x = Host platform specific # 2x = Build system specific # 3x = New target features # 4x = Patches to fix target bugs # 5x = New devices for i in ${patchdir}/*.patch ; do echo "Patch: $i" >> patch.log patch --verbose --strip=0 --input="$i" >> patch.log || task_error "Patching failed." done do_popd } 'workdir' is the top level of the source folder i.e. for binutls, gcc, etc... 'patchdir' is the folder where the patches are. > > > > diff -rupwN gcc/calls.c gcc/calls.c > --- gcc/calls.c 2008-06-24 02:58:17.000000000 -0500 > +++ gcc/calls.c 2010-08-26 11:56:14.000000000 -0500 > @@ -3466,7 +3466,7 @@ emit_library_call_value_1 (int retval, r > for (; count < nargs; count++) > { > rtx val = va_arg (p, rtx); > - enum machine_mode mode = va_arg (p, enum machine_mode); > + enum machine_mode mode = va_arg (p, int); > > /* We cannot convert the arg value to the mode the library wants > here; > must do it earlier where we know the signedness of the arg. */ > diff -rupwN gcc/config/avr32/avr32.c gcc/config/avr32/avr32.c > --- gcc/config/avr32/avr32.c 1969-12-31 18:00:00.000000000 -0600 > +++ gcc/config/avr32/avr32.c 2010-08-26 11:59:24.000000000 -0500 > @@ -0,0 +1,8090 @@ > +/* > > > The latter snip "worked" because it created a new file (althought it > created it at the wrong level) , all other parts of the patch, like the > first snip here, failed to find the targer file. > > > here's the first binutls patch that did work: > > diff -Nwarup ./config/override.m4 > ../avr32-binutils-trunk/config/override.m4 > --- ./config/override.m4 2010-03-03 19:28:57.000000000 +0530 > +++ ../avr32-binutils-trunk/config/override.m4 2010-04-01 > 19:28:34.968750000 +0530 > @@ -52,7 +52,7 @@ dnl Or for updating the whole tree at on > AC_DEFUN([_GCC_AUTOCONF_VERSION_CHECK], > [m4_if(m4_defn([_GCC_AUTOCONF_VERSION]), > m4_defn([m4_PACKAGE_VERSION]), [], > - [m4_fatal([Please use exactly Autoconf ]_GCC_AUTOCONF_VERSION[ > instead of ]m4_defn([m4_PACKAGE_VERSION])[.])]) > + [m4_errprintn([Please use exactly Autoconf ]_GCC_AUTOCONF_VERSION[ > instead of ]m4_defn([m4_PACKAGE_VERSION])[.])]) > ]) > m4_define([AC_INIT], m4_defn([AC_INIT])[ > _GCC_AUTOCONF_VERSION_CHECK > > > > comparing the formats it seems like they were not created in the same way. > > if I add ./ to all file names and add -a to diff it works: > > diff -rupwNa ./gcc/calls.c ./gcc/calls.c > --- ./gcc/calls.c 2008-06-24 02:58:17.000000000 -0500 > +++ ./gcc/calls.c 2010-08-26 11:56:14.000000000 -0500 > > > I guess this was some kind of error in preparation of those patches but > it's a headache. > > Can anyone suggest a simple means to correct this ? I presume ct-ng is a > bit stubborn about what format it expects so I'm looking for an > alternative to hand editing every line of each hunk. > > There's a lot of files with lots of hunks. > > Is there an obvious trick I'm missing? > > TIA,. > > > > -- > For unsubscribe information see http://sourceware.org/lists.html#faq > > -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |