public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@cygnus.co.uk>
To: "Natarajan, Mekala (CTS)" <NMekala@CHN.CTS-CORP.COM>
Cc: "'ecos-discuss@sourceware.cygnus.com'"
	<ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] build error for i386
Date: Fri, 08 Dec 2000 14:47:00 -0000	[thread overview]
Message-ID: <3A3164F4.5646C5DB@cygnus.co.uk> (raw)
In-Reply-To: <8F1D166D08ACD41196EE00B0D020944B0BB693@CTSINENTSXUB>

"Natarajan, Mekala (CTS)" wrote:
> 
> hi all,
>         i upgraded the cygwin installation to latest version(1.1.6)and tried
> building the kernel agin from config tool..
> it reported the following error:
> In file included from
> //D/sample/samp_install/include/cyg/memalloc/dlmalloc.hxx:76,
>                  from
> //d/eCos/packages/services/memalloc/common/current/src/dlmalloc.cxx:208:
> //D/sample/samp_install/include/cyg/memalloc/dlmallocimpl.hxx:67:
> pkgconf/heaps.hxx: No such file or directory
> //D/sample/samp_install/include/cyg/memalloc/dlmallocimpl.hxx:69: warning:
> `CYGMEM_HEAP_COUNT' is not defined
> make[1]: *** [src/dlmalloc.o.d] Error 1
> make[1]: Leaving directory
> `/d/sample/samp_build/services/memalloc/common/current'
> make: *** [build] Error 2
> 
> Can someone suggest a solution..

Did you use a new built tree? It's just that pkgconf/heaps.hxx really
should exist after heapgen.tcl has been executed.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

  reply	other threads:[~2000-12-08 14:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-08  8:43 Natarajan, Mekala (CTS)
2000-12-08 14:47 ` Jonathan Larmour [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-09-15  0:19 [ECOS] build error for I386 adon@walkersun
2000-09-15 10:32 ` Jonathan Larmour
2000-09-15 11:03   ` adon@walkersun
2000-09-15 11:26     ` 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=3A3164F4.5646C5DB@cygnus.co.uk \
    --to=jlarmour@cygnus.co.uk \
    --cc=NMekala@CHN.CTS-CORP.COM \
    --cc=ecos-discuss@sourceware.cygnus.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).