public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Bhanu Prakash Adhikari" <bhanua@aztecsoft.com>
To: "Gary Thomas" <gary@mlbassoc.com>
Cc: <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] Failed to build ecos - redboot
Date: Mon, 26 Feb 2007 13:34:00 -0000	[thread overview]
Message-ID: <93F0E3CFC1ABB646B8808894FC7CDD2509EE4DA2@azindbaex01.aztec.soft> (raw)



Gary, Thanks a lot. I could make it.

I'm rejuvenated with thousand elephants' energy, kudos for your support
and time.

My sincere apologies for resending the mail, it was with the impression
that my first mail was not reached.



-----Original Message-----
From: Gary Thomas [mailto:gary@mlbassoc.com]
Sent: Monday, February 26, 2007 6:50 PM
To: Bhanu Prakash Adhikari
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Failed to build ecos - redboot

Bhanu Prakash Adhikari wrote:
>
>
> Hi,
>
> I tried to build RedBoot for se7751 and e7t but failed miserably.
>
> I have firewall which doesn't allow to download and install through
"sh
> ecos-install.tcl".
>
> I download the snapshots of
>
>
> 1. Toolchains from http://public.planetmirror.com/pub/sourceware/ecos
>
> 2. ecos-2.0.i386linux.tar.bz2 from
>
http://sources-redhat.oc1.mirrors.redwire.net/ecos/releases/ecos-2.0/eco
> s-2.0.i386linux.tar.bz2
>
>
> I followed the instructions mentioned at
> http://ecos.sourceware.org/docs-latest/redboot/rebuilding-redboot.html
> to find not working.
>
> I feel the document provided by ecos is not so friendly. I felt unless
> we go through all the documents it's hard to build the redboot image.
>
>
> Do we have any cooked up document or any pointer where can I build
> successfully?
>
>
> My environment file -
>
>
>       1
>       2 #run "source $0"
>       3
>       4 ROOTDIR=`pwd`
>       5
>       6 export ECOS_REPOSITORY=${ROOTDIR}/packages
>       7
>       8 PATH_1=${ROOTDIR}/tools/bin:$PATH
>       9 #export PATH=${ROOTDIR}/../gnutools/arm-elf/bin:$PATH_1
>      10 export PATH=/opt/ecos/gnutools/sh-elf/bin:$PATH_1
>      11
>      12 #export ECOS_REPOSITORY
>      13 #export PATH
>
> Compilation error I'm getting -
>
>
> make -r -C hal/sh/arch/v2_0
>
/home/bhanup/redboot/ecos/ecos-2.0/install/include/cyg/hal/sh_offsets.in
> c
> make[1]: Entering directory
> `/home/bhanup/redboot/ecos/ecos-2.0/hal/sh/arch/v2_0'
> sh-elf-gcc -ml -m3 -Wall -Wpointer-arith -Wstrict-prototypes -Winline
> -Wundef -Woverloaded-virtual -ggdb -O2 -ffunction-sections
> -fdata-sections -fno-rtti -fno-exceptions -fvtable-gc -finit-priority
> -I/home/bhanup/redboot/ecos/ecos-2.0/install/include
> -I/home/bhanup/redboot/ecos/ecos-2.0/packages/hal/sh/arch/v2_0
> -I/home/bhanup/redboot/ecos/ecos-2.0/packages/hal/sh/arch/v2_0/src
> -I/home/bhanup/redboot/ecos/ecos-2.0/packages/hal/sh/arch/v2_0/tests
-I.
> -Wp,-MD,sh_offsets.tmp -o hal_mk_defs.tmp -S
>
/home/bhanup/redboot/ecos/ecos-2.0/packages/hal/sh/arch/v2_0/src/hal_mk_
> defs.c
> In file included from
>
/home/bhanup/redboot/ecos/ecos-2.0/packages/hal/sh/arch/v2_0/src/hal_mk_
> defs.c:57:
>
/home/bhanup/redboot/ecos/ecos-2.0/install/include/cyg/hal/hal_arch.h:37
> 3:5: warning: "CYGINT_HAL_I386_MEM_REAL_REGION_TOP" is not defined
> In file included from
>
/home/bhanup/redboot/ecos/ecos-2.0/install/include/cyg/hal/pcmb_intr.h:6
> 7,
>                  from
>
/home/bhanup/redboot/ecos/ecos-2.0/install/include/cyg/hal/plf_intr.h:71
> ,
>                  from
>
/home/bhanup/redboot/ecos/ecos-2.0/install/include/cyg/hal/var_intr.h:71
> ,
>                  from
>
/home/bhanup/redboot/ecos/ecos-2.0/install/include/cyg/hal/hal_intr.h:66
> ,
>                  from
>
/home/bhanup/redboot/ecos/ecos-2.0/packages/hal/sh/arch/v2_0/src/hal_mk_
> defs.c:58:
>
/home/bhanup/redboot/ecos/ecos-2.0/install/include/pkgconf/hal_i386_pcmb
> .h:16:1: warning: "CYGNUM_HAL_RTC_PERIOD" redefined
> In file included from
> /home/bhanup/redboot/ecos/ecos-2.0/install/include/pkgconf/hal.h:13,
>                  from
>
/home/bhanup/redboot/ecos/ecos-2.0/packages/hal/sh/arch/v2_0/src/hal_mk_
> defs.c:55:
>
/home/bhanup/redboot/ecos/ecos-2.0/install/include/pkgconf/hal_sh.h:22:1
> : warning: this is the location of the previous definition
> In file included from
>
/home/bhanup/redboot/ecos/ecos-2.0/install/include/cyg/hal/plf_io.h:57,
>                  from
>
/home/bhanup/redboot/ecos/ecos-2.0/install/include/cyg/hal/hal_io.h:63,
>                  from
>
/home/bhanup/redboot/ecos/ecos-2.0/install/include/cyg/hal/pcmb_intr.h:7
> 2,
>                  from
>
/home/bhanup/redboot/ecos/ecos-2.0/install/include/cyg/hal/plf_intr.h:71
> ,
>                  from
>
/home/bhanup/redboot/ecos/ecos-2.0/install/include/cyg/hal/var_intr.h:71
> ,
>                  from
>
/home/bhanup/redboot/ecos/ecos-2.0/install/include/cyg/hal/hal_intr.h:66
> ,
>                  from
>
/home/bhanup/redboot/ecos/ecos-2.0/packages/hal/sh/arch/v2_0/src/hal_mk_
> defs.c:58:
>
/home/bhanup/redboot/ecos/ecos-2.0/install/include/pkgconf/hal_i386_pc.h
> :12:1: warning: "HAL_PLATFORM_CPU" redefined
> In file included from
> /home/bhanup/redboot/ecos/ecos-2.0/install/include/pkgconf/hal.h:17,

Firstly, there's no need to send the same message multiple times (twice
within an hour).  This is a volunteer project; you'll get help when
folks
have time.

I just built RedBoot for this platform, following the quoted steps.  No
problems encountered.

   % export ECOS_REPOSITORY=/work2/ecos/packages
   % mkdir /tmp/se_test
   % cd se_test
   % ecosconfig new se7751 redboot
   % ecosconfig import
${ECOS_REPOSITORY}/hal/sh/se7751/current/misc/redboot_RAM.ecm
   % ecosconfig tree
   % make

 From the errors you listed above, my guess is that you tried to build
RedBoot in a non-clean directory.  Always start with an empty tree when
you run 'ecosconfig new'

Also, I'd suggest that you get sources that are newer than 2.0 (which
is now approaching 5 years old!).  eCosCentric has snapshots of the
latest CVS tree for those behind firewalls.

--
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


The information contained in, or attached to, this e-mail, contains confidential information and is intended solely for the use of the individual or entity to whom they are addressed and is subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email.

www.aztecsoft.com

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

             reply	other threads:[~2007-02-26 13:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-26 13:34 Bhanu Prakash Adhikari [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-26 12:51 Bhanu Prakash Adhikari
2007-02-26 13:20 ` Gary Thomas
2007-02-26 12:10 Bhanu Prakash Adhikari

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=93F0E3CFC1ABB646B8808894FC7CDD2509EE4DA2@azindbaex01.aztec.soft \
    --to=bhanua@aztecsoft.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=gary@mlbassoc.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).