From: Fabrice Gautier <Fabrice_Gautier@sdesigns.com>
To: 'niky' <b4506051@csie.ntu.edu.tw>, ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] Re: how to apply the patches for i386
Date: Mon, 04 Dec 2000 12:07:00 -0000 [thread overview]
Message-ID: <B1F6452C89AFD411AE0800A0CC734C23015046@EMAIL1> (raw)
> -----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
next reply other threads:[~2000-12-04 12:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-04 12:07 Fabrice Gautier [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-03 4:30 niky
2000-11-29 19:04 niky
2000-11-30 2:07 ` Robin Farine
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B1F6452C89AFD411AE0800A0CC734C23015046@EMAIL1 \
--to=fabrice_gautier@sdesigns.com \
--cc=b4506051@csie.ntu.edu.tw \
--cc=ecos-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).