public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Danny" <daniel@fh-konstanz.de>
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] Problem with malloc Implementation header
Date: Thu, 21 Jul 2005 10:50:00 -0000	[thread overview]
Message-ID: <200507211050.j6LAoXrw001575@s2802.fh-konstanz.de> (raw)

Hello list!

I have following problem:

I have installed eCos with the default repository. To get the current
version of the repository, I have downloaded it via cvs. After that, I have
adapted the eCos repository path to the current repository.

My problem appears during my eCos Configuration:

As hardware template I have choosen the ARM Industrial Module AIM 711; as
software template, I have choosen the “net” package. 
Then I want to activate the option “Malloc Implemantation header” under the
package ISO C and Posix Infrastructure and the component “Standard general
utility functions. As value of this option a had to declare a path in the
build directory, where to find the header. I have declared this value with:
<pkgconf/memalloc.h>   
Then I have started the build process by clicking on the “Library” button.
But during the build process, I get an error like this:

In file included from
/ecos-c/Projekt/All/untitled_install/include/cyg/libc/stdio/streambuf.hxx:15
7,
                 from
/ecos-c/Projekt/All/untitled_install/include/cyg/libc/stdio/stream.hxx:67,
                 from
/ecos-c/Projekt/All/untitled_install/include/cyg/libc/stdio/stdiofiles.hxx:6
3,
                 from
/ecos-c/cygwin/opt/aim/ecos/packages/language/c/libc/stdio/current/src/commo
n/fclose.cxx:69:
/ecos-c/Projekt/All/untitled_install/include/cyg/libc/stdio/streambuf.inl:
In 
   destructor `Cyg_StdioStreamBuffer::~Cyg_StdioStreamBuffer()':
/ecos-c/Projekt/All/untitled_install/include/cyg/libc/stdio/streambuf.inl:10
4: `
   free' undeclared (first use this function)
/ecos-c/Projekt/All/untitled_install/include/cyg/libc/stdio/streambuf.inl:10
4: (Each
   undeclared identifier is reported only once for each function it appears 
   in.)
make[1]: Leaving directory
`/ecos-c/Projekt/All/untitled_build/language/c/libc/stdio/current'
make[1]: *** [src/common/fclose.o.d] Error 1
make: Leaving directory `/ecos-c/Projekt/All/untitled_build'
make: *** [build] Error 2


What is the failure? Is the path for the malloc impl. header not right?
When I have activated addition options like “Mallinfo Implementation header”
or “memset Implementation header” (under String functions) I get more
errors. What can I do? Do I need a patch for eCos or do I need additional
header-Files. 
Thanks for answering!

   




 





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

             reply	other threads:[~2005-07-21 10:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-21 10:50 Danny [this message]
2005-07-21 16:38 ` Andrew Lunn
  -- strict thread matches above, loose matches on Subject: below --
2005-07-21  9:39 Danny

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=200507211050.j6LAoXrw001575@s2802.fh-konstanz.de \
    --to=daniel@fh-konstanz.de \
    --cc=ecos-discuss@sources.redhat.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).