public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Dhawal Mer" <merdn@LNTEBG.com>
To: <Eric.Doenges@DynaPel.com>
Cc: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Hi,
Date: Wed, 15 Oct 2003 09:44:00 -0000	[thread overview]
Message-ID: <sf8d6247.057@EBGMAIL> (raw)

Thanx,
I hope you are right.In middle i have tried out other version too. Hence,file might be over written.
I will send you whole details after reinstalling the current/cvs version of eCos tools.
Can you please guide any particular URL for latest CVS for ecos configtool.

Regards,
Dhawal.

>>> Eric Doenges <Eric.Doenges@DynaPel.com> 10/15/03 02:44PM >>>
Dhawal Mer wrote:
> Thanx for quick reply.
> I am referring to the book named 'Embedded Software Development with eCos' written by Author 'Anthony J. Massa'.
> I have already compile the default example ( basic.c ) successfully using the default configuration of i386( with 82559 NIC ).
> The application still making appropriate ' basic.s ' while target set as the 'i386 with 82559 NIC'.
> Hence, i  hope there is no problem in toolchains.
> what do you mean by 'messed up your source tree', if it's there how i should correct.

Well, I find it strange that the linker is complaining about an
undefined reference to CYGARC_PCI_DMA_ADDRESS, supposedly
in <...>/packages/io/fileio/current/src/misc.cxx, when the file in
question does not contain any references to that macro (nor is there
any reason why it should). This means either

a) The linker is mistaken, and the undefined reference occurs in some
    other file.

b) Somehow, the original misc.cxx got overwritten (fully or partially)
    by some other file.

If I were you I would get the latest eCos source code from the CVS
repository and try again, doing a clean reconfiguration and build
of eCos itself.
-- 
--------------------------------------------------------------------
|     Eric Doenges              |     DynaPel Laboratories GmbH    |
|     Tel: +49 89 962428 23     |     Fraunhoferstrasse 9/2        |
|     Fax: +49 89 962428 90     |     D - 85737 Ismaning, Germany  |
--------------------------------------------------------------------



--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

             reply	other threads:[~2003-10-15  9:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15  9:44 Dhawal Mer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-16  3:24 Dhawal Mer
     [not found] <sf8d6247.056@EBGMAIL>
2003-10-15 11:26 ` Eric Doenges
     [not found] <sf8d54d6.023@EBGMAIL>
2003-10-15  9:13 ` Eric Doenges
2003-10-15  8:37 Dhawal Mer
     [not found] <sf8d42b8.006@EBGMAIL>
2003-10-15  7:37 ` Eric Doenges
2003-10-15  7:19 Dhawal Mer
     [not found] <sf8d3344.057@EBGMAIL>
2003-10-15  6:48 ` Eric Doenges
2003-10-15  6:19 Dhawal Mer
2003-10-14 11:44 Dhawal Mer
2003-10-14 11:58 ` Andrew Lunn
2003-10-14 12:01 ` Eric Doenges
2003-10-09  3:23 Dhawal Mer
2003-10-08 10:29 Dhawal Mer
2003-10-08 11:53 ` Eric Doenges

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=sf8d6247.057@EBGMAIL \
    --to=merdn@lntebg.com \
    --cc=Eric.Doenges@DynaPel.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).