Fitting it on the drive

Fitting it on the drive

[Kenneth Porter]

More an NT problem than an eCos problem:

I'm having trouble building eCos because I keep running out of disk
space.

I've got a 2gb FAT16 partition, so the cluster size sucks. I've been
brutally pruning stuff off the drive but I still haven't finished
building the tools because of the production of many small files.

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

I don't want to repartion as it will mess up drive letters for my OS/2
setup. I've got pinball loaded to get HPFS access to my OS/2 partition,
but I don't want to write to it from NT because there's no disk
checking of HPFS partitions under NT.


Kenneth Porter
Kensington Laboratories, Inc.
mailto:kenneth_porter@kensingtonlabs.com
http://www.kensingtonlabs.com

ECOS Re: Fitting it on the drive

[Bart Veer]

>>>>> "Kenneth" == Kenneth Porter <kenneth_porter@kensingtonlabs.com> writes:

    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> I've got a 2gb FAT16 partition, so the cluster size
    Kenneth> sucks. I've been brutally pruning stuff off the drive but
    Kenneth> I still haven't finished building the tools because of
    Kenneth> the production of many small files.

    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?

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

Bart Veer // eCos net maintainer

Re: ECOS Re: Fitting it on the drive

[Bart Veer]

    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