public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@cygnus.co.uk>
To: Robert Cragie <rcc@jennic.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Rebuilding using ecosconfig (plain text)
Date: Thu, 02 Nov 2000 19:42:00 -0000	[thread overview]
Message-ID: <3A023424.31FCBDD3@cygnus.co.uk> (raw)
In-Reply-To: <NDBBLOIOMLKELOJBAPAGEELCCBAA.rcc@jennic.com>

Robert Cragie wrote:
[building cygmon]
> This works fine. However, if I update either the ecos.ecc file, or any of
> the sources in the repository, the output from make seems to show them being
> rebuilt (I haven't studied it carefully), but the image files do not seem to
> change. They do not seem to change even if I do a 'make clean; make' at the
> top The only way I seem to be able to rebuild properly is by deleting the
> whole tree except for ecos.ecc, touching ecos.ecc and starting again from
> 'ecosconfig tree'. Surely the build system should be able to be a bit
> cleverer about dependencies? Or am I missing something?

Sorry it took so long to get back on this. It is a dependency problem on
cygmon. Add these extra dependencies to the make rule in
CYGBLD_BUILD_CYGMON in packages/cygmon/VERSION/cdl/cygmon.cdl (i.e. at end
of the very long line beginning <PREFIX>/bin/cygmon.elf)

$(PREFIX)/lib/target.ld $(PREFIX)/lib/vectors.o $(PREFIX)/lib/libtarget.a
$(PREFIX)/lib/libextras.a 

I've also applied this to our CVS repository.

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-11-02 19:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-28  8:40 Robert Cragie
2000-11-02 19:42 ` Jonathan Larmour [this message]
2000-09-28  9:08 AshCan

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=3A023424.31FCBDD3@cygnus.co.uk \
    --to=jlarmour@cygnus.co.uk \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=rcc@jennic.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).