Re: [ECOS] Problems building eCos under WinNT

[Bart Veer <bartv at redhat dot com>]

>>>>> "Christian" == Christian Grebe <cg-itk@t-online.de> writes:

    <snip>

    Christian> pkgconf/infra.h: No such file or directory
    Christian> make[1]: ***
    Christian> [//D/Programme/REDHAT~1/eCos/7708EVBMinimal_install/include/cyg/hal/sh_offsets.i
    Christian> nc] Error 1
    Christian> make[1]: Leaving directory `/d/Programme/Red
    Christian> Hat/eCos/7708EVBMinimal_build/hal/sh/arch/v1_3_1'
    Christian> make: *** [build] Error 2

    Christian> *** Process 255 terminated (rc=2)

    Christian> Browsing the directories and looking at the makefiles I
    Christian> could not find a clue where the missing file 'hal.h'
    Christian> could come from.

Configuration header files are generated by the config tools when you
create the build tree. See a previous posting
http://sourceware.cygnus.com/ml/ecos-discuss/2000-06/msg00222.html
and specifically John Dallaway's response.

    Christian> Another strange thing is sometimes the path notation
    Christian> '//D/...' is used and sometimes '/d/...'.

    Christian> Any ideas for this?

Generally you can ignore this.

The basic problem is that some tools, especially GNU make, are
fundamentally incompatible with path names containing a : character.
Fixing the tools is non-trivial, and risks breaking existing
makefiles. Obviously this is a problem when it comes to Windows drive
letters, so cygwin needs to work around this.

The preferred approach is to use mount points, for example to mount
drive c: as /d. This means that all cygwin apps operate in an
environment with Unix-style pathnames, at the cost of a small
performance penalty because all I/O operations involving filenames
need an translation phase.

cygwin also provides an alternative mechanism where you can use //d to
refer to d: without having to mount the drive explicitly. Sometimes
this is useful, sometimes it causes other problems. I believe the
cygwin maintainers would like to eliminate this feature in time.

All these things have changed over the years, and exactly what appears
in messages depends on when the tool was ported to cygwin, or even
when a particular subsystem was ported, or which releases of cygwin
are supported by the code, or ...

Bart Veer // eCos net maintainer