This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: create eCos on Linux
- To: Gary Thomas <gthomas at redhat dot com>
- Subject: Re: [ECOS] create eCos on Linux
- From: Guillermo GARCIA <guga at teamlog dot fr>
- Date: Thu, 10 Aug 2000 19:19:50 +0200
- CC: ecos-discuss at sourceware dot cygnus dot com, bartv at redhat dot com
- Organization: teamlog
- References: <XFMail.20000810095659.gthomas@redhat.com>
Gary Thomas a écrit :
> On 10-Aug-2000 Guillermo GARCIA wrote:
> >> Gary> On 10-Aug-2000 Guillermo GARCIA wrote:
> >> >> Hi there,
> >> >>
> >> >> I'm lost with ecosconfig.
> >> >>
> >> >> [root@localhost ecos-work]# ecosconfig new edb7209
> >> >> ecosconfig: Symbol `__vt_9bad_alloc' has different size in shared
> >> >> object, consider re-linking
> >> >> ecosconfig: Symbol `__vt_9exception' has different size in shared
> >> >> object, consider re-linking
> >> >> Unknown target edb7209
> >> >>
> >> >> what did i forget ?
> >> >>
> >> >> the install of gcc, gdb and insight was done without problems.
> >> >> the ecos's rpm was installed without problems too.
> >> >> i set the ECOS_REPOSITORY=/opt/ecos/ecos-1.3.1/packages.
> >> >> i set the
> >> >> PATH=/opt/ecos/ecos-1.3.1/tools/bin:/tools/H-i686-pc-linux-gnu/bin:/sbin:/usr/sbin:/bin:/u
> >> >> sr/bin:/
> >> >> usr/X11R6/bin
> >>
> >> Gary> This looks like an issue with 'ecosconfig' itself.
> >> Gary> What version of Linux are you running?
> >
> > i'm using Mandrake 7.0
> >
>
> Gary> I would be nice to know where the problem with the shared libraries is.
> Gary> Can you send the output from:
> Gary> % ldd `which ecosconfig`
Of course i can, here it comes :
[root@localhost ecos-work]# ldd `which ecosconfig`
libdl.so.2 => /lib/libdl.so.2 (0x4001a000)
libstdc++-libc6.1-1.so.2 => /usr/lib/libstdc++-libc6.1-1.so.2 (0x4001e000)
libm.so.6 => /lib/libm.so.6 (0x4006d000)
libc.so.6 => /lib/libc.so.6 (0x4008b000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
> >> Bart>More accurately, it is a problem with the C++ runtime support that is
> >> Bart>installed. There are complications here depending on which Linux
> >> Bart>distribution you are using, whether or not you have upgraded the gcc
> >> Bart>installation yourself, ... I have not seen the symbol size warnings
> >> Bart>before but I suspect that they are harmless. If ecosconfig starts
> >> Bart>SEGV'ing on you than that is an indication that C++ exception handling
> >> Bart>is not working and that you need to rebuild ecosconfig from source.
> >
> > i use gcc provided by Mandrake 7.0
> > [root@localhost /]# gcc -v
> > Reading specs from /usr/lib/gcc-lib/i586-mandrake-linux/2.95.2/specs
> > gcc version 2.95.2 19991024 (release)
> > what are the steps involved in order to rebuild ecosconfig ?
> >
> >> Gary> However, it doesn't seem to have affected the output. I
> >> Gary> think you need to tell ecosconfig where to find your source
> >> Gary> repository. In my case:
> >> Gary> % ECOS_REPOSITORY=/work2/ecc/ecc
> >
> > what is the source repository because on the docs the ECOS_REPOSITORY is
> > /opt/ecos/ecos-1.3.1/packages.
> >
>
> Gary>What you've chosen is just fine (sorry I missed it during my first reading).
no matter.
> >> Gary> The other thing, you probably want to use 'edb7212', not
> >> Gary> 'edb7209'. The 7209 has no DRAM controller and thus no
> >> Gary> memory. Not much use for anything but ROM based
> >> Gary> applications.
> >
> > but i have the CIRRUS LOGIC EP7209 Development Kit, do i really have to use
> > 'edb7212' instead of 'edb7209' ?
> >
>
> Gary>Yes. Even if your board and chip are labelled 7209, you really have a 7212
> Gary>if the board has any DRAM :-) Of course if you don't have any DRAM that
> Gary>would be a whole other consideration :-)
:-)
> Gary>Based on the information you sent (ecosconfig list) and the fact that you're
> Gary>working from the 1.3.1 version (very old, that), you'll need to do this
> Gary>instead:
??? isn't it the last release ???
if not where can i get the last one ?
> Gary> % ecosconfig new edb7xxx
it generate the file : ecos.ecc but i still have the following output.
ecosconfig: Symbol `__vt_9bad_alloc' has different size in shared object, consider re-linking
ecosconfig: Symbol `__vt_9exception' has different size in shared object, consider re-linking
do i have to rebuild ecosconfig anyway ?
> Gary> % ecosconfig import config.edb7212
[root@localhost ecos-work]# ecosconfig import config.edb7212
ecosconfig: Symbol `__vt_9bad_alloc' has different size in shared object, consider re-linking
ecosconfig: Symbol `__vt_9exception' has different size in shared object, consider re-linking
Invalid savefile "config.edb7212".
couldn't read file "config.edb7212": no such file or directory
i din't have the file "config.edb7212"
> Gary> % ecosconfig tree
>
> Gary>Where 'config.edb7212' looks like this:
>
> Gary>======= cut here - config.edb7212 ===========================================
> Gary>cdl_option CYGHWR_HAL_ARM_EDB7XXX_VARIANT {
> Gary> user_value EP7212
> Gary>};
> Gary>======= cut here - config.edb7212 ===========================================
>
> Gary>Of course, since I know you're wanting to get the GoAhead web server working,
> Gary>you probably really want to use this:
Yes but before i wan't to run eCos because i didn't add the package net-1.0b1.epk and
without this package i suppose the following instructions can't work.
> Gary> % ecosconfig new edb7xxx net
> Gary> % ecosconfig import config.edb7212
> Gary> % ecosconfig tree
>
> Gary>Where 'config.edb7212' looks like this:
>
> Gary>======= cut here - config.edb7212 ===========================================
> Gary>cdl_option CYGHWR_HAL_ARM_EDB7XXX_VARIANT {
> Gary> user_value EP7212
> Gary>};
>
> Gary>cdl_option CYGNUM_LIBC_MALLOC_MEMPOOL_SIZE {
> Gary> user_value 1638400
> Gary>};
> Gary>======= cut here - config.edb7212 ===========================================
>
> Gary>Let me/us know if this helps.
Yes it does help me because now i have the ecos.ecc file but
that's the only change since last time.
thanks
Guillermo.