From: "survey liu" <liuxw@263.net>
To: "Trenton D. Adams" <trent.nospam@telusplanet.net>
Cc: "'eCos Discussion'" <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] RAM FileSystem memory usage
Date: Wed, 01 Aug 2001 22:33:00 -0000 [thread overview]
Message-ID: <000d01c11b14$e3f93320$fca210ac@utszrtsurveyl> (raw)
In-Reply-To: <000001c11b0b$013f4b40$0307a8c0@ab.hsia.telus.net>
Hi,
What does this error mean? Maybe a bug?
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c: In function `hal_pc_fpe_dsr':
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:88: `cyg_handle_t' undeclared (first use in this function)
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:88: (Each undeclared identifier is reported only once
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:88: for each function it appears in.)
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:88: parse error before `me'
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:103: `me' undeclared (first use in this function)
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:103: warning: implicit declaration of function `cyg_thread_self'
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:109: warning: implicit declaration of function `cyg_thread_get_stack_base'
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:111: `cyg_addrword_t' undeclared (first use in this function)
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c: At top level:
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:137: parse error before `hal_pc_fpe_interrupt_object'
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:137: warning: type defaults to `int' in declaration of `hal_pc_fpe_interrupt_object'
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:137: warning: data definition has no type or storage class
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:138: parse error before `hal_pc_fpe_interrupt'
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:138: warning: type defaults to `int' in declaration of `hal_pc_fpe_interrupt'
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:138: warning: data definition has no type or storage class
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c: In function `hal_platform_init':
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:170: warning: implicit declaration of function `cyg_interrupt_create'
file://G/new/packages/hal/i386/pc/v1_3_1/src/plf_misc.c:173: warning: implicit declaration of function `cyg_interrupt_attach'
make[1]: *** [src/plf_misc.o.d] Error 1
make[1]: Leaving directory `/cygdrive/f/liuxw_4/liuxw4_build/hal/i386/pc/v1_3_1'
make: *** [build] Error 2
david
next prev parent reply other threads:[~2001-08-01 22:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 15:13 Trenton D. Adams
2001-08-01 20:07 ` Jonathan Larmour
2001-08-01 21:24 ` Trenton D. Adams
2001-08-01 22:33 ` survey liu [this message]
2001-08-02 0:44 ` [ECOS] Build error [Re: [ECOS] RAM FileSystem memory usage] Jesper Skov
[not found] ` <007e01c11b33$dffa4f10$fca210ac@utszrtsurveyl>
2001-08-02 2:24 ` Jesper Skov
[not found] ` <001401c11b4a$81af3e40$fca210ac@utszrtsurveyl>
2001-08-02 5:04 ` Jesper Skov
2001-08-02 10:03 ` [ECOS] RAM FileSystem memory usage Jonathan Larmour
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='000d01c11b14$e3f93320$fca210ac@utszrtsurveyl' \
--to=liuxw@263.net \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=trent.nospam@telusplanet.net \
/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).