public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: David Fernandez <dfernandez@cct.co.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: eCos Disuss <ecos-discuss@ecos.sourceware.org>,
	";	John Dallaway" <jld@ecoscentric.com>
Subject: Re: [ECOS] Problems building ecos sources
Date: Fri, 24 Feb 2006 22:00:00 -0000	[thread overview]
Message-ID: <1140799114.2884.16.camel@software.cct.co.uk> (raw)
In-Reply-To: <1140770157.2884.2.camel@software.cct.co.uk>

		On Fri, 2006-02-24 at 08:35 +0000, David Fernandez wrote:
> > 
> > Hi David
> > 
> > A shot in the dark. Try this:
> > 
> > Index: eCosSocket.h
> > ===================================================================
> > RCS file: /cvs/ecos/ecos/host/tools/Utils/common/eCosSocket.h,v
> > retrieving revision 1.2
> > diff -u -r1.2 eCosSocket.h
> > --- eCosSocket.h        19 Sep 2000 05:53:51 -0000      1.2
> > +++ eCosSocket.h        23 Feb 2006 18:09:34 -0000
> > @@ -75,6 +75,7 @@
> > 
> >  class CeCosSocket {
> >  public:
> > +        friend class CeCosSerial;
> >         static const String GetHostByName(LPCTSTR pszHost);
> > 
> >    // These functions must be called before any other operation is carried out:
> > 
> >         Andrew
> 
> Hi Andrew,
> 
> It worked !, the utility is running now.
> 
> Thank you very much for your help. I'll keep exploring this eCos
> thing...
> 
> 
> David.
> 

	Hi Andrew,

	Acouple of things more:

	1- When trying to use the internal help viewer, I get a segmentation
fault in configtool. (Probably something for John to look at)

	2- When trying to build REDBOOT as per the instructions in the ecos
documentation, and using ecosconfig:

[dfernandez@software RB]$ ecosconfig new pc_i82559 redboot U
CYGSEM_HAL_USE_ROM_MONITOR, new inferred value 0
U CYGIMP_HAL_COMMON_INTERRUPTS_USE_INTERRUPT_STACK, new inferred value 0
[dfernandez@software RB]$ ecosconfig
import /opt/ecos/packages/hal/i386/pc/cu..rrent/misc/redboot_FLOPPY_SMP.ecm
...change prefix to i586-elf...
[dfernandez@software RB]$ ecosconfig check
Target: pc_i82559
Template: redboot
Added:
 CYGPKG_IO_ETH_DRIVERS
No conflicts
[dfernandez@software RB]$ ecosconfig tree
[dfernandez@software RB]$ make
...
make[1]: Leaving directory
`/home/dfernandez/Projects/eCos/RB/infra/current'
make -r -C redboot/current build
make[1]: Entering directory
`/home/dfernandez/Projects/eCos/RB/redboot/current'
i586-elf-gcc -c  -I/home/dfernandez/Projects/eCos/RB/install/include
-I/opt/ecos/packages/redboot/current
-I/opt/ecos/packages/redboot/current/src
-I/opt/ecos/packages/redboot/current/tests -I.
-I/opt/ecos/packages/redboot/current/src/ -finline-limit=7000 -Wall
-Wpointer-arith -Wstrict-prototypes -Winline -Wundef  -g -O2
-ffunction-sections -fdata-sections  -fno-exceptions
-Wp,-MD,src/main.tmp -o
src/redboot_main.o /opt/ecos/packages/redboot/current/src/main.c
/opt/ecos/packages/redboot/current/src/main.c: In function ‘cyg_start’:
/opt/ecos/packages/redboot/current/src/main.c:397: error: invalid lvalue
in assignment
/opt/ecos/packages/redboot/current/src/main.c: In function ‘do_go’:
/opt/ecos/packages/redboot/current/src/main.c:597: error: invalid lvalue
in assignment
make[1]: *** [src/main.o.d] Error 1
make[1]: Leaving directory
`/home/dfernandez/Projects/eCos/RB/redboot/current'
make: *** [build] Error 2

	May be that there's something wrong with this ecos version?
	Any ideas about that?

David.


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

  parent reply	other threads:[~2006-02-24 16:38 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-22 16:49 David Fernandez
2006-02-22 16:54 ` Andrew Lunn
     [not found]   ` <1140627369.2878.18.camel@software.cct.co.uk>
2006-02-22 21:39     ` Andrew Lunn
2006-02-23 11:33       ` David Fernandez
2006-02-23 15:02         ` Andrew Lunn
2006-02-23 15:37           ` David Fernandez
2006-02-23 15:51             ` Andrew Lunn
2006-02-23 16:48             ` [ECOS] " John Dallaway
     [not found]               ` <1140716284.2885.45.camel@software.cct.co.uk>
2006-02-24  6:11                 ` Andrew Lunn
2006-02-24 16:38                   ` David Fernandez
2006-02-24 17:14                     ` Andrew Lunn
2006-02-24 22:00                     ` David Fernandez [this message]
2006-02-26  5:19                       ` [ECOS] " Andrew Lunn
2006-02-27 10:09                         ` David Fernandez
2006-02-27 11:25                           ` Andrew Lunn
2006-02-27 15:35                             ` David Fernandez
     [not found]                             ` <1141032779.2878.13.camel@software.cct.co.uk>
2006-02-27 18:14                               ` Andrew Lunn
2006-02-27 22:48                                 ` David Fernandez
2006-05-14  2:51                                   ` Frank Pagliughi
2006-02-26 23:13                       ` Chuck McManis
2006-02-27  9:33                         ` David Fernandez
2006-02-23 17:30         ` Andrew Lunn

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=1140799114.2884.16.camel@software.cct.co.uk \
    --to=dfernandez@cct.co.uk \
    --cc=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=jld@ecoscentric.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).