public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* [ECOS] Conflict
@ 2003-12-01 14:59 Santha Kumar
  2003-12-01 16:28 ` [ECOS] Conflict John Dallaway
  2003-12-01 16:30 ` [ECOS] Conflict Andrew Lunn
  0 siblings, 2 replies; 3+ messages in thread
From: Santha Kumar @ 2003-12-01 14:59 UTC (permalink / raw)
  To: ecos-discuss


Hello all

 I am using sh3(se7729) solution engine board as the target. I am trying to build the hello.c example. As described in the manual I did the compilation through the shell using the command "sh-elf-gcc......."(as like in the manual).
While compiling I am getting an error message like compiled for little endian but the target is big endian.

I went back to the configuration tool and selected the use bigendian mode under the hal architecture. The configuration tool shows conflict.when I am trying to resolve the conflict it is deselecting the endian mode. 

I tried changing in the basetype.h in the install directory but that also does not work. while compiling I am getting the same error.

 What to do? some suggestion pls. 

Regards
Santha kumar

     



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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [ECOS] Re: Conflict
  2003-12-01 14:59 [ECOS] Conflict Santha Kumar
@ 2003-12-01 16:28 ` John Dallaway
  2003-12-01 16:30 ` [ECOS] Conflict Andrew Lunn
  1 sibling, 0 replies; 3+ messages in thread
From: John Dallaway @ 2003-12-01 16:28 UTC (permalink / raw)
  To: Santha Kumar; +Cc: ecos-discuss

Santha Kumar wrote:

>  I am using sh3(se7729) solution engine board as the target. I am trying to build the hello.c example. As described in the manual I did the compilation through the shell using the command "sh-elf-gcc......."(as like in the manual).
> While compiling I am getting an error message like compiled for little endian but the target is big endian.

Try building hello.c using the supplied Makefile. For example:

   cd /opt/ecos/ecos-2.0/examples
   make INSTALL_DIR=/path/to/myconfig_install

John Dallaway
eCosCentric Limited



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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [ECOS] Conflict
  2003-12-01 14:59 [ECOS] Conflict Santha Kumar
  2003-12-01 16:28 ` [ECOS] Conflict John Dallaway
@ 2003-12-01 16:30 ` Andrew Lunn
  1 sibling, 0 replies; 3+ messages in thread
From: Andrew Lunn @ 2003-12-01 16:30 UTC (permalink / raw)
  To: Santha Kumar; +Cc: ecos-discuss

On Mon, Dec 01, 2003 at 08:29:48PM +0530, Santha Kumar wrote:
> 
> Hello all
> 
>  I am using sh3(se7729) solution engine board as the target. I am trying to build the hello.c example. As described in the manual I did the compilation through the shell using the command "sh-elf-gcc......."(as like in the manual).
> While compiling I am getting an error message like compiled for little endian but the target is big endian.
> 

> I went back to the configuration tool and selected the use bigendian
> mode under the hal architecture. The configuration tool shows
> conflict.when I am trying to resolve the conflict it is deselecting
> the endian mode.

It appears the HAL only supports little endian.

What endian's are you compiling the hello.c program?

     Andrew

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2003-12-01 16:30 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-12-01 14:59 [ECOS] Conflict Santha Kumar
2003-12-01 16:28 ` [ECOS] Conflict John Dallaway
2003-12-01 16:30 ` [ECOS] Conflict Andrew Lunn

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).