From: Gary Thomas <gthomas@redhat.com>
To: "Trenton D. Adams" <tadams@theone.dnsalias.com>
Cc: eCos Discussion <ecos-discuss@sourceware.cygnus.com>
Subject: RE: [ECOS] Confirmed error in eth_drv.c
Date: Mon, 20 Aug 2001 09:56:00 -0000 [thread overview]
Message-ID: <XFMail.20010820110010.gthomas@redhat.com> (raw)
In-Reply-To: <002101c12997$d6f81e70$090110ac@TRENT>
Note: this error would only occur if you turn _LOCK_WITH_ROM_MONITOR off,
which obviously we don't think is a good idea.
I'll change the source to build in this case anyway.
On 20-Aug-2001 Trenton D. Adams wrote:
> I get the following output from the config tool v2.04
>
> /cygdrive/C/MyDocuments/eCosRepository/ecos/packages/io/eth/current/src/
> net/eth_drv.c
> /cygdrive/C/MyDocuments/eCosRepository/ecos/packages/io/eth/current/src/
> net/eth_drv.c: In function `eth_drv_send':
> /cygdrive/C/MyDocuments/eCosRepository/ecos/packages/io/eth/current/src/
> net/eth_drv.c:617: parse error before `static'
> make[1]: Leaving directory
> `/c/MyDocuments/eCosBuilds/RAMSupport_build/io/eth/current'
> /cygdrive/C/MyDocuments/eCosRepository/ecos/packages/io/eth/current/src/
> net/eth_drv.c:629: `mbuf_key' undeclared (first use in this function)
> make: Leaving directory `/c/MyDocuments/eCosBuilds/RAMSupport_build'
> /cygdrive/C/MyDocuments/eCosRepository/ecos/packages/io/eth/current/src/
> net/eth_drv.c:629: (Each undeclared identifier is reported only once
> /cygdrive/C/MyDocuments/eCosRepository/ecos/packages/io/eth/current/src/
> net/eth_drv.c:629: for each function it appears in.)
> /cygdrive/C/MyDocuments/eCosRepository/ecos/packages/io/eth/current/src/
> net/eth_drv.c:504: warning: `m0' might be used uninitialized in this
> function
> /cygdrive/C/MyDocuments/eCosRepository/ecos/packages/io/eth/current/src/
> net/eth_drv.c: At top level:
> /cygdrive/C/MyDocuments/eCosRepository/ecos/packages/io/eth/current/src/
> net/eth_drv.c:284: warning: `eth_drv_tx_done' used but never defined
> make[1]: *** [src/net/eth_drv.o.d] Error 1
>
>
> It would appear that the #ifdef _LOCK_WITH_ROM_MONITOR begins before the
> end of the while loop and ends after the while loop. So, this would
> naturally cause a parse error!
>
> It appears to have been done on 2001-08-14 which is probably why I never
> seen it before.
>
> So, just move the "#endif // _LOCK_WITH_ROM_MONITOR" and "#undef
> _LOCK_WITH_ROM_MONITOR" up above the end of the while loop.
>
> Works for me now! :)
>
>
>#ifdef _LOCK_WITH_ROM_MONITOR
> // Unlock the driver & hardware. It can once again be safely
> shared.
> if (need_lock) {
> cyg_drv_dsr_unlock();
>#ifdef _LOCK_USING_INTERRUPTS
> HAL_RESTORE_INTERRUPTS(ints);
>#endif
> }
> } // this here appears to me to be the end of the while loop
>#endif // _LOCK_WITH_ROM_MONITOR
>#undef _LOCK_WITH_ROM_MONITOR
>
>
>
> Trenton D. Adams
> Extreme Engineering
>#17, 6025 - 12 St. SE
> Calgary, Alberta, Canada
> T2H 2K1
>
> Phone: 403 640 9494 ext-208
> Fax: 403 640 9599
>
> http://www.extremeeng.com
next prev parent reply other threads:[~2001-08-20 9:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-20 9:47 Trenton D. Adams
2001-08-20 9:56 ` Gary Thomas [this message]
2001-08-20 10:05 ` Trenton D. Adams
2001-08-20 10:12 ` Gary Thomas
2001-08-20 10:14 ` Trenton D. Adams
2001-08-20 10:18 ` Gary Thomas
2001-08-20 9:59 ` 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=XFMail.20010820110010.gthomas@redhat.com \
--to=gthomas@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=tadams@theone.dnsalias.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).