This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: create eCos on Linux


>>>>> "Gary" == Gary Thomas <gthomas@redhat.com> writes:

    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:/usr/bin:/
    >> usr/X11R6/bin

    Gary> This looks like an issue with 'ecosconfig' itself.  
    Gary> What version of Linux are you running?

More accurately, it is a problem with the C++ runtime support that is
installed. There are complications here depending on which Linux
distribution you are using, whether or not you have upgraded the gcc
installation yourself, ... I have not seen the symbol size warnings
before but I suspect that they are harmless. If ecosconfig starts
SEGV'ing on you than that is an indication that C++ exception handling
is not working and that you need to rebuild ecosconfig from source.

    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

    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.

Another thing worth trying is "ecosconfig list". That will tell you
about all the packages and targets, in your current eCos repository.

Bart Veer // eCos net maintainer

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]