[ECOS] Re: how to apply the patches for i386

[ECOS] Re: how to apply the patches for i386

[niky]

Hi,

    After I applied the perl script to the patch, there are some problems
from the patchs. I checked out the packages from anoncvs.

patching file hal/i386/arch/current/src/vectors.S
Hunk #7 FAILED at 228.
1 out of 9 hunks FAILED -- saving rejects to file
hal/i386/arch/current/src/vectors.S.rej
...
Reversed (or previously applied) patch detected!  Assume -R? [n]
Apply anyway? [n] y   
Hunk #1 FAILED at 65. 
Hunk #2 FAILED at 92. 
Hunk #3 FAILED at 155.
Hunk #4 FAILED at 170.
Hunk #5 succeeded at 198 (offset -11 lines).
Hunk #6 succeeded at 332 (offset 3 lines).  
Hunk #7 succeeded at 402 (offset -11 lines).
Hunk #8 succeeded at 438 (offset 3 lines).
4 out of 8 hunks FAILED -- saving rejects to file
...
   
    What can I do ?
    Thanks.

Re: [ECOS] Re: how to apply the patches for i386

[Robin Farine]

niky wrote:
> 
> Hi,
> 
>     After I applied the perl script to the patch, there are some problems
> from the patchs. I checked out the packages from anoncvs.
> 
> patching file hal/i386/arch/current/src/vectors.S
> Hunk #7 FAILED at 228.
> 1 out of 9 hunks FAILED -- saving rejects to file
> hal/i386/arch/current/src/vectors.S.rej
> ...
> Reversed (or previously applied) patch detected!  Assume -R? [n]
> Apply anyway? [n] y
> Hunk #1 FAILED at 65.
> Hunk #2 FAILED at 92.
> Hunk #3 FAILED at 155.
> Hunk #4 FAILED at 170.
> Hunk #5 succeeded at 198 (offset -11 lines).
> Hunk #6 succeeded at 332 (offset 3 lines).
> Hunk #7 succeeded at 402 (offset -11 lines).
> Hunk #8 succeeded at 438 (offset 3 lines).
> 4 out of 8 hunks FAILED -- saving rejects to file
> ...
> 
>     What can I do ?
>     Thanks.

Look at hal/i386/arch/current/src/vectors.S.rej, compare with the
original chunks and manually merge the changes.

Robin

RE: [ECOS] Re: how to apply the patches for i386

[Fabrice Gautier]

> -----Original Message-----
> From: niky [ mailto:b4506051@csie.ntu.edu.tw ]
> Sent: Sunday, December 03, 2000 4:30 AM
> To: ecos-discuss@sources.redhat.com
> Subject: [ECOS] Re: how to apply the patches for i386
> 
> 
> Hi,
> 
> 	After I apply the patches for i386, I did
> 	
> 	ecosconfig new pc redboot
> 	ecosconfig tree
> 	make
> 	make tests
> 	
> 	There are something wrong when I made tests

In Fact i don't think i ever tried to make the teest for redboot. This may
explain.


 	
> /usr/local/ecos/redboot/install/lib/extras.o: In function \x04o_load':
> /share/ecos/packages/redboot/current/src/load.c:310: 
> undefined reference to
> \x12am_start'
> /share/ecos/packages/redboot/current/src/load.c:316: 
> undefined reference to
> \x12am_end'
> /share/ecos/packages/redboot/current/src/load.c:361: 
> undefined reference to
> \x05ntry_address'
> /usr/local/ecos/redboot/install/lib/libtarget.a(redboot_io.o):
>  In function
> \x16erify_action':
> /share/ecos/packages/redboot/current/src/io.c:308: undefined 
> reference to
> \x03onsole_selected'
> collect2: ld returned 1 exit status



> 	Before I apply the patches, there is nothing wrong to make tests
> under linux synthesis.
> 	But after patch, it has some errors when I make tests

My 386-PC patch are likely to break the linux synthetic target. At the very
least the synthetic target should be ported to support the virtual vector
stuff.

> 
> /usr/local/ecos/linux/install/lib/libtarget.a(kernel_intr.o): 
> In function
> \x03yg_Interrupt::configure_interrupt(unsigned int, int, int)':
> /share/ecos/packages/kernel/current/src/intr/intr.cxx:659: undefined
> reference to \bal_interrupt_handlers'
> /share/ecos/packages/kernel/current/src/intr/intr.cxx:659: undefined
> reference to \bal_vsr_table'
> /share/ecos/packages/kernel/current/src/intr/intr.cxx:659: undefined
> reference to \bal_pc_generic_irq'
> /share/ecos/packages/kernel/current/src/intr/intr.cxx:659: undefined
> reference to \bal_interrupt_data'
> /share/ecos/packages/kernel/current/src/intr/intr.cxx:659: undefined
> reference to \bal_interrupt_objects'
> /share/ecos/packages/kernel/current/src/intr/intr.cxx:659: undefined
> reference to \bal_interrupt_handlers'
> /share/ecos/packages/kernel/current/src/intr/intr.cxx:659: undefined
> reference to \bal_interrupt_data'
> /share/ecos/packages/kernel/current/src/intr/intr.cxx:659: undefined
> reference to \bal_interrupt_handlers'
> /share/ecos/packages/kernel/current/src/intr/intr.cxx:659: undefined
> reference to \bal_default_isr'
> /share/ecos/packages/kernel/current/src/intr/intr.cxx:659: undefined
> reference to \bal_interrupt_objects'
> collect2: ld returned 1 exit status

I think all theses are because I had to change the name of this variable in
order to use the common virtual vector stuff.

Regards,

-- 
Fabrice Gautier
fabrice_gautier@sdesigns.com 

[ECOS] Re: how to apply the patches for i386

[niky]

Hi,

	After I apply the patches for i386, I did
	
	ecosconfig new pc redboot
	ecosconfig tree
	make
	make tests
	
	There are something wrong when I made tests
	
/usr/local/ecos/redboot/install/lib/extras.o: In function \x04o_load':
/share/ecos/packages/redboot/current/src/load.c:310: undefined reference to
\x12am_start'
/share/ecos/packages/redboot/current/src/load.c:316: undefined reference to
\x12am_end'
/share/ecos/packages/redboot/current/src/load.c:361: undefined reference to
\x05ntry_address'
/usr/local/ecos/redboot/install/lib/libtarget.a(redboot_io.o): In function
\x16erify_action':
/share/ecos/packages/redboot/current/src/io.c:308: undefined reference to
\x03onsole_selected'
collect2: ld returned 1 exit status

	Before I apply the patches, there is nothing wrong to make tests
under linux synthesis.
	But after patch, it has some errors when I make tests

/usr/local/ecos/linux/install/lib/libtarget.a(kernel_intr.o): In function
\x03yg_Interrupt::configure_interrupt(unsigned int, int, int)':
/share/ecos/packages/kernel/current/src/intr/intr.cxx:659: undefined
reference to \bal_interrupt_handlers'
/share/ecos/packages/kernel/current/src/intr/intr.cxx:659: undefined
reference to \bal_vsr_table'
/share/ecos/packages/kernel/current/src/intr/intr.cxx:659: undefined
reference to \bal_pc_generic_irq'
/share/ecos/packages/kernel/current/src/intr/intr.cxx:659: undefined
reference to \bal_interrupt_data'
/share/ecos/packages/kernel/current/src/intr/intr.cxx:659: undefined
reference to \bal_interrupt_objects'
/share/ecos/packages/kernel/current/src/intr/intr.cxx:659: undefined
reference to \bal_interrupt_handlers'
/share/ecos/packages/kernel/current/src/intr/intr.cxx:659: undefined
reference to \bal_interrupt_data'
/share/ecos/packages/kernel/current/src/intr/intr.cxx:659: undefined
reference to \bal_interrupt_handlers'
/share/ecos/packages/kernel/current/src/intr/intr.cxx:659: undefined
reference to \bal_default_isr'
/share/ecos/packages/kernel/current/src/intr/intr.cxx:659: undefined
reference to \bal_interrupt_objects'
collect2: ld returned 1 exit status

	Anything I did wrong ?