public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Bart Veer <bartv@cygnus.co.uk>
To: kenneth_porter@kensingtonlabs.com
Cc: ecos-discuss@cygnus.com
Subject: Re: ECOS Re: Fitting it on the drive
Date: Thu, 19 Nov 1998 12:03:00 -0000	[thread overview]
Message-ID: <199811191843.SAA24664@sheesh.cygnus.co.uk> (raw)
In-Reply-To: < 199811182130.VAA18790@sheesh.cygnus.co.uk > (message from BartVeer on Wed, 18 Nov 1998 21:30:39 GMT)

    Kenneth> More an NT problem than an eCos problem: I'm having
    Kenneth> trouble building eCos because I keep running out of disk
    Kenneth> space.

    Kenneth> How do others handle this? Is there a way to overlay
    Kenneth> another (possibly compressing) filesystem on the FAT16
    Kenneth> partition to give me better use of the space?

    Bart> It may be possible to do the toolchain build in stages
    Bart> rather than all at once. You will need to do a single
    Bart> configure to produce a complete build tree. Then you should
    Bart> be able to run "make all install" in each subdirectory,
    Bart> using the order defined in the top-level makefile, followed
    Bart> by a "make clean" to free up the disk space again. It will
    Bart> be a rather tedious process, and occasionally you may have
    Bart> to fix up a couple of things by hand, but there is a good
    Bart> chance it will work.

I have since been informed that there is actually an alternative and
possibly more robust way of doing this sort of thing. The top-level
Makefile provides targets such as all-gcc and install-gcc.
Therefore you should be able to do something like the following at the
top-level of the toolchain build tree

   make all-libiberty install-libiberty clean-libiberty
   make all-texinfo install-texinfo clean-texinfo
   ...

This process is not going to be less tedious than what I suggested
earlier, but it may avoid a few problems here and there.

Bart Veer // eCos net maintainer


      parent reply	other threads:[~1998-11-19 12:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-12 23:39 Kenneth Porter
     [not found] ` < 199811130739.XAA14389@mail.well.com >
1998-11-18 13:30   ` ECOS " Bart Veer
     [not found]     ` < 199811182130.VAA18790@sheesh.cygnus.co.uk >
1998-11-19 12:03       ` Bart Veer [this message]

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=199811191843.SAA24664@sheesh.cygnus.co.uk \
    --to=bartv@cygnus.co.uk \
    --cc=ecos-discuss@cygnus.com \
    --cc=kenneth_porter@kensingtonlabs.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).