* Ecos with i386 synthetizer
@ 2006-03-05 16:41 Tyler
2006-03-05 23:02 ` Bart Veer
0 siblings, 1 reply; 3+ messages in thread
From: Tyler @ 2006-03-05 16:41 UTC (permalink / raw)
To: ecos-devel
Hi all,
I try to use ecos on a i386 synthetizer target.
I've build the environment with configtool and build the synthetizer
too. I've compiled the hello.c programm with the following command :
gcc -g -IBASE_DIR/ecos-work/install/include hello.c \
-LBASE_DIR/ecos-work/install/lib -Ttarget.ld -nostdlib
but when I execute the file a.out, with "gdb -nw a.out", the following
error appears :
Program received signal SIGSEGV, Segmentation fault.
_stext () at /tmp/cc6DVBi1.s:1163
1163 /tmp/cc6DVBi1.s: no such file.
in /tmp/cc6DVBi1.s
Current language: auto; currently asm
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Ecos with i386 synthetizer
2006-03-05 16:41 Ecos with i386 synthetizer Tyler
@ 2006-03-05 23:02 ` Bart Veer
2006-03-06 17:44 ` Tyler
0 siblings, 1 reply; 3+ messages in thread
From: Bart Veer @ 2006-03-05 23:02 UTC (permalink / raw)
To: tyler; +Cc: ecos-devel
>>>>> "Tyler" == Tyler <tyler@agat.net> writes:
Tyler> Hi all,
Tyler> I try to use ecos on a i386 synthetizer target. I've build
Tyler> the environment with configtool and build the synthetizer
Tyler> too. I've compiled the hello.c programm with the following
Tyler> command :
Tyler> gcc -g -IBASE_DIR/ecos-work/install/include hello.c \
Tyler> -LBASE_DIR/ecos-work/install/lib -Ttarget.ld -nostdlib
Tyler> but when I execute the file a.out, with "gdb -nw a.out",
Tyler> the following error appears :
Tyler> Program received signal SIGSEGV, Segmentation fault.
Tyler> _stext () at /tmp/cc6DVBi1.s:1163
Tyler> 1163 /tmp/cc6DVBi1.s: no such file.
Tyler> in /tmp/cc6DVBi1.s
Tyler> Current language: auto; currently asm
Which version of eCos are you using? And which version of Linux?
If you are trying to use eCos 2.0 then you will need to upgrade to
anoncvs. There have been incompatible changes in behaviour in some
Linux distributions, especially Fedora, which break the old synthetic
target code. The version in anoncvs has been updated to work around
these changes.
Bart
--
Bart Veer eCos Configuration Architect
http://www.ecoscentric.com/ The eCos and RedBoot experts
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Ecos with i386 synthetizer
2006-03-05 23:02 ` Bart Veer
@ 2006-03-06 17:44 ` Tyler
0 siblings, 0 replies; 3+ messages in thread
From: Tyler @ 2006-03-06 17:44 UTC (permalink / raw)
To: ecos-devel
>>>>>> "Tyler" == Tyler <tyler@agat.net> writes:
>
> Tyler> Hi all,
> Tyler> I try to use ecos on a i386 synthetizer target. I've build
> Tyler> the environment with configtool and build the synthetizer
> Tyler> too. I've compiled the hello.c programm with the following
> Tyler> command :
>
> Tyler> gcc -g -IBASE_DIR/ecos-work/install/include hello.c \
> Tyler> -LBASE_DIR/ecos-work/install/lib -Ttarget.ld -nostdlib
>
> Tyler> but when I execute the file a.out, with "gdb -nw a.out",
> Tyler> the following error appears :
>
> Tyler> Program received signal SIGSEGV, Segmentation fault.
> Tyler> _stext () at /tmp/cc6DVBi1.s:1163
> Tyler> 1163 /tmp/cc6DVBi1.s: no such file.
> Tyler> in /tmp/cc6DVBi1.s
> Tyler> Current language: auto; currently asm
>
> Which version of eCos are you using? And which version of Linux?
>
> If you are trying to use eCos 2.0 then you will need to upgrade to
> anoncvs. There have been incompatible changes in behaviour in some
> Linux distributions, especially Fedora, which break the old synthetic
> target code. The version in anoncvs has been updated to work around
> these changes.
>
> Bart
>
Ok, Thanks.
I've use the cvs version of ecos and the hello programm works.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-03-06 17:44 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-03-05 16:41 Ecos with i386 synthetizer Tyler
2006-03-05 23:02 ` Bart Veer
2006-03-06 17:44 ` Tyler
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).