From: Andrew Lunn <andrew@lunn.ch>
To: "netadmin @dslextreme.com" <netadmin@dslextreme.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] ECOS 2.0 build help: mips_size.ecc: error
Date: Sat, 11 Apr 2009 08:56:00 -0000 [thread overview]
Message-ID: <20090411074103.GW28253@lunn.ch> (raw)
In-Reply-To: <de6ef1900904101552n7d46fb3fn8c2c90b15854c3e1@mail.gmail.com>
On Fri, Apr 10, 2009 at 03:52:06PM -0700, netadmin @dslextreme.com wrote:
> Hi, I am trying to follow the instruction from Netgear GS108T switch
> to build its firmware.
> It is MIPS based chip.? I followed the instruction and download and
> installed ECOS.
> Then I realized the original firmware was based on ECOS 2.0.? So I download from
> the ECOS mirror site the 2.0.
>
> After applied the source code, I ran this command:
> $ECOS_CORE/tools/bin/ecosconfig --config=../mips_size.ecc
> --srcdir=$ECOS_CORE/packages --prefix=$ECOS_CORE/mips_install tree
>
> But I got a lot of errors:
>
> ../mips_size.ecc: error
> ??? Attempt to load an unknown package `CYGPKG_HAL_MIPS_BCM47xx'.
> ../mips_size.ecc: error
> ??? Attempt to load an unknown package `CYGPKG_HAL_MIPS_BCM953710'.
> ../mips_size.ecc: error
> ??? Attempt to load an unknown package `CYGPKG_IO_SERIAL_MIPS_BCM947xx'.
> ../mips_size.ecc: error
> ??? Attempt to load an unknown package `CYGPKG_DEVS_FLASH_MIPS_BCM947xx'.
> ../mips_size.ecc: error
> ??? Attempt to load an unknown package `CYGPKG_LOGGING'.
> ../mips_size.ecc: error
These packages don't exist in eCos 2.0. I guess Netgear have made some
changes to eCos. Did they supply a patch with these new packages?
Andrew
--
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:[~2009-04-11 7:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-11 7:41 netadmin @dslextreme.com
2009-04-11 8:56 ` Andrew Lunn [this message]
2009-04-15 15:48 ` netadmin @dslextreme.com
2009-04-15 18:42 ` Gary Thomas
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=20090411074103.GW28253@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=netadmin@dslextreme.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).