From: John Dallaway <john@dallaway.org.uk>
To: abhishek srivastava <just_abhi22@yahoo.co.in>
Cc: ecos discuss <ecos-discuss@sourceware.org>
Subject: [ECOS] Re: simple redboot package donot build for i386!
Date: Fri, 04 May 2012 07:46:00 -0000 [thread overview]
Message-ID: <4FA38943.8060203@dallaway.org.uk> (raw)
In-Reply-To: <1336102615.37672.YahooMailNeo@web193501.mail.sg3.yahoo.com>
Abhishek
abhishek srivastava wrote:
> it seems that in my last post i was not clear with my question so no one responded !
> just repeating the question with detailed error
>
> i am trying to generate package "redboot" for i386 (vmware) hardware.
> i have also imported "redboot_FLOOPY.ecm", made no change and tried to build library.
> i got error !!! why?
The error you are seeing may be just an issue with your current build
tree. Try giving your .ecc file a new name ("File->Save As..") and then
building the new configuration.
Once you have overcome the above issue, you will find that you need to
use the current lancepci ethernet driver sources from CVS when building
with i386-elf-gcc 4.3.2. Ref:
http://ecos.sourceware.org/cgi-bin/cvsweb.cgi/ecos/packages/devs/eth/amd/lancepci/current/src/if_lancepci.c.diff?r1=1.3&r2=1.4&cvsroot=ecos
I hope this helps...
John Dallaway
eCos maintainer
http://www.dallaway.org.uk/john
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2012-05-04 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 3:37 [ECOS] " abhishek srivastava
2012-05-04 7:46 ` John Dallaway [this message]
[not found] ` <1336131480.68784.YahooMailNeo@web193504.mail.sg3.yahoo.com>
[not found] ` <1336156315.81731.YahooMailNeo@web193506.mail.sg3.yahoo.com>
2012-05-04 18:38 ` [ECOS] " abhishek srivastava
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=4FA38943.8060203@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-discuss@sourceware.org \
--cc=just_abhi22@yahoo.co.in \
/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).