public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Ramanujan Puranam Tandalam" <ramanujan.tandalam@wipro.com>
To: <ecos-discuss@sources.redhat.com>
Cc: <ecos-discuss-digest@sources.redhat.com>
Subject: [ECOS] Installation problem
Date: Mon, 04 Feb 2002 04:14:00 -0000	[thread overview]
Message-ID: <001801c1ad76$3b51d750$2c22a8c0@madms31852> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1489 bytes --]

Hello all,

I have done a CVS checkout of the latest sources from the repository. I am trying to compile the Libraries for i386 pc Target. I have choosen the corresponding templates, and started a build. 

But to my surprise the build fails with the errors, which i am pasting here for complete reference:

make[1]: Entering directory `/usr/local/configtool/rama1_build/services/memalloc/common/current'
sh: -c: line 9: syntax error: unexpected end of file
i386-elf-gcc -Wall -Wpointer-arith -Wstrict-prototypes -Winline -Wundef -Woverloaded-virtual -g -O2 -ffunction-sections -fdata-sections -fno-rtti -fno-exceptions -fvtable-gc -finit-priority  -I/usr/local/configtool/rama1_install/include -I/usr/local/ecos/ecos/packages/services/memalloc/common/current -I/usr/local/ecos/ecos/packages/services/memalloc/common/current/src -I/usr/local/ecos/ecos/packages/services/memalloc/common/current/tests -I. -Wp,-MD,heapgen.tmp -E /usr/local/ecos/ecos/packages/services/memalloc/common/current/src/heapgen.cpp -o heapgeninc.tcl
make[1]: *** [heaps.cxx] Error 2
make[1]: Leaving directory `/usr/local/configtool/rama1_build/services/memalloc/common/current'
make: *** [build] Error 2
make -r -C services/memalloc/common/current heaps.cxx


Kindly suggest a solution to this problem.

To make things easier, I had compiled the released ecos-1.3.1.rpm for Linux and it was compiling fine.

Let me know if any further information is needed.

Best Regards
Ramanujan    




[-- Attachment #1.2: Type: text/html, Size: 2775 bytes --]

[-- Attachment #2: Wipro_Disclaimer.txt --]
[-- Type: text/plain, Size: 490 bytes --]

**************************Disclaimer************************************


Information contained in this E-MAIL being proprietary to Wipro Limited
is 'privileged' and 'confidential' and intended for use only by the
individual or entity to which it is addressed. You are notified that any
use, copying or dissemination of the information contained in the E-MAIL
in any manner whatsoever is strictly prohibited.


*****************************************************************************

             reply	other threads:[~2002-02-04 12:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-04  4:14 Ramanujan Puranam Tandalam [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-06  6:13 [ECOS] Installation Problem abhishek kashyap
2001-06-06  6:24 ` Jonathan Larmour
2001-06-06  5:33 [ECOS] installation problem abhishek kashyap
2001-06-06  6:02 ` Jonathan Larmour

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='001801c1ad76$3b51d750$2c22a8c0@madms31852' \
    --to=ramanujan.tandalam@wipro.com \
    --cc=ecos-discuss-digest@sources.redhat.com \
    --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).