From: Leandro Fanzone <leandro@hasar.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Floppy option
Date: Thu, 11 Dec 2003 17:21:00 -0000 [thread overview]
Message-ID: <3FD89B83.2050005@hasar.com> (raw)
Hello, I'm a newbie with eCos, and I was experimenting a bit with the
hello world application. If I compile it to run on RAM, it compiles OK,
but if I change "Statup type" to FLOPPY I got the following error:
config_install/lib/vectors.o:/tmp/ccypm71S.s:1
296: undefined reference to 'hal_saved_interrupt_state'
collect2: ld returned 1 exit status
I'm on i386 under WindowsXP/Cygwin. Am I doing something wrong?
Thank you in advance,
Leandro Fanzone
Buenos Aires, Argentina
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next reply other threads:[~2003-12-11 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 17:21 Leandro Fanzone [this message]
2003-12-12 15:50 ` Leandro Fanzone
2003-12-12 16:53 ` Nick Garnett
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=3FD89B83.2050005@hasar.com \
--to=leandro@hasar.com \
--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).