[ECOS] Problems building eCos under WinNT

[ECOS] Problems building eCos under WinNT

[Christian Grebe]

Hello list,

we are trying hard to build eCos 1.3.1 for a sh-elf target under WinNT.

With the 1.1.1 cygwin we had problems with strange chars in eCos configtool
generated makefiles. Some faq stated that cygwin 1.1.2 should help and it did.
But now our 2.95.2-1 gcc does not work anymore. Simpliy trying to run gcc gives
following error:

...sh-elf-gcc.exe: *** shared region is corrupted.  inited 15
      0 [main] ? 0 lock_pinfo_for_update: rc 0, pinfo_mutex 0xFFFFFFFF, Win32
error 6

I know this sounds like a cygwin fault but my more general question is:

Is there any combination of tools out there that runs stable for use with eCos?
If yes, please let us know. Thanks in advance.

Greetings,

Christian Grebe

Dipl.-Ing.
ITK Dr. Kassen GmbH
Beim Eberacker 3
D-35633 Lahnau
Tel: +49 6441/6 50 05-14
Fax: +49 6441/6 50 05-29

Re: [ECOS] Problems building eCos under WinNT

[Jonathan Larmour]

Christian Grebe wrote:
> 
> Hello list,
> 
> we are trying hard to build eCos 1.3.1 for a sh-elf target under WinNT.
> 
> With the 1.1.1 cygwin we had problems with strange chars in eCos configtool
> generated makefiles. Some faq stated that cygwin 1.1.2 should help and it did.
> But now our 2.95.2-1 gcc does not work anymore. Simpliy trying to run gcc gives
> following error:
> 
> ...sh-elf-gcc.exe: *** shared region is corrupted.  inited 15
>       0 [main] ? 0 lock_pinfo_for_update: rc 0, pinfo_mutex 0xFFFFFFFF, Win32
> error 6
> 
> I know this sounds like a cygwin fault but my more general question is:

There's a fundamental problem here - this indicates there are two cygwin
dlls on your system, and new tools are unlikely to help. Search your system
for "cygwin1.dll" and be sure to rename away or delete the old one.

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

Re: [ECOS] Problems building eCos under WinNT

[Christian Grebe]

Hello Bart,

Bart Veer wrote:
>    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.


Thank you _very_ much for your hint. That solved the problem. Build runs to
the (successful) end now.

We stumbled over some beginner faults I think:
1) We had more than one 'cygwin1.dll'.
2) We did not save the eCos Configtool configuration file again after
deleting the build tree.
3) We did not mount drive partitions with textmode.

But now, so far (sigh), the tools are running and we can begin with the real
thing.

This list is great.

Greetings,

Christian Grebe

Re: [ECOS] Problems building eCos under WinNT

[Bart Veer]

>>>>> "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

RE: [ECOS] Problems building eCos under WinNT

[Christian Grebe]

Hello list,

Jonathan Larmour wrote:
> There's a fundamental problem here - this indicates there are
> two cygwin
> dlls on your system, and new tools are unlikely to help.
> Search your system
> for "cygwin1.dll" and be sure to rename away or delete the old one.

Yes, you were right! Now gcc runs with no problems.

Now following problem occures: Compiling the first source file there are some
header files missing.
Here's the output...

*** Process 255 created "make -j1"
make -r -C hal/sh/arch/v1_3_1 headers
make[1]: Entering directory `/d/Programme/Red
Hat/eCos/7708EVBMinimal_build/hal/sh/arch/v1_3_1'
make[1]: Leaving directory `/d/Programme/Red
Hat/eCos/7708EVBMinimal_build/hal/sh/arch/v1_3_1'
make -r -C hal/sh/edk/v1_3_1 headers
make[1]: Entering directory `/d/Programme/Red
Hat/eCos/7708EVBMinimal_build/hal/sh/edk/v1_3_1'
make[1]: Leaving directory `/d/Programme/Red
Hat/eCos/7708EVBMinimal_build/hal/sh/edk/v1_3_1'
make -r -C io/serial/v1_3_1 headers
make[1]: Entering directory `/d/Programme/Red
Hat/eCos/7708EVBMinimal_build/io/serial/v1_3_1'
make[1]: Leaving directory `/d/Programme/Red
Hat/eCos/7708EVBMinimal_build/io/serial/v1_3_1'
make -r -C hal/common/v1_3_1 headers
make[1]: Entering directory `/d/Programme/Red
Hat/eCos/7708EVBMinimal_build/hal/common/v1_3_1'
make[1]: Leaving directory `/d/Programme/Red
Hat/eCos/7708EVBMinimal_build/hal/common/v1_3_1'
make -r -C io/common/v1_3_1 headers
make[1]: Entering directory `/d/Programme/Red
Hat/eCos/7708EVBMinimal_build/io/common/v1_3_1'
make[1]: Leaving directory `/d/Programme/Red
Hat/eCos/7708EVBMinimal_build/io/common/v1_3_1'
make -r -C infra/v1_3_1 headers
make[1]: Entering directory `/d/Programme/Red
Hat/eCos/7708EVBMinimal_build/infra/v1_3_1'
make[1]: Leaving directory `/d/Programme/Red
Hat/eCos/7708EVBMinimal_build/infra/v1_3_1'
make -r -C error/v1_3_1 headers
make[1]: Entering directory `/d/Programme/Red
Hat/eCos/7708EVBMinimal_build/error/v1_3_1'
make[1]: Leaving directory `/d/Programme/Red
Hat/eCos/7708EVBMinimal_build/error/v1_3_1'
headers finished
make -r -C hal/sh/arch/v1_3_1
//D/Programme/REDHAT~1/eCos/7708EVBMinimal_install/include/cyg/hal/sh_offsets.in
c
make[1]: Entering directory `/d/Programme/Red
Hat/eCos/7708EVBMinimal_build/hal/sh/arch/v1_3_1'
sh-elf-gcc -mb -m3 -Wall -Wpointer-arith -Wstrict-prototypes -Winline -Wundef -W
overloaded-virtual -g -O2 -ffunction-sections -fdata-sections -fno-rtti -fno-exc
eptions -fvtable-gc -finit-priority  -I//D/Programme/REDHAT~1/eCos/7708EVBMinima
l_install/include -I//D/Programme/REDHAT~1/eCos/packages/hal/sh/arch/v1_3_1 -I//
D/Programme/REDHAT~1/eCos/packages/hal/sh/arch/v1_3_1/src -I//D/Programme/REDHAT
~1/eCos/packages/hal/sh/arch/v1_3_1/tests -I. -Wp,-MD,sh_offsets.tmp -o
hal_mk_defs.tmp -S
//D/Programme/REDHAT~1/eCos/packages/hal/sh/arch/v1_3_1/src/hal_mk_defs.c
//D/Programme/REDHAT~1/eCos/packages/hal/sh/arch/v1_3_1/src/hal_mk_defs.c:46:
pkgconf/hal.h: No such file or directory
In file included from
//D/Programme/REDHAT~1/eCos/packages/hal/sh/arch/v1_3_1/src/hal_mk_defs.c:48:
//D/Programme/REDHAT~1/eCos/7708EVBMinimal_install/include/cyg/hal/hal_arch.h:48
: pkgconf/hal.h: No such file or directory
In file included from
//D/Programme/REDHAT~1/eCos/packages/hal/sh/arch/v1_3_1/src/hal_mk_defs.c:49:
//D/Programme/REDHAT~1/eCos/7708EVBMinimal_install/include/cyg/hal/hal_intr.h:53
: pkgconf/hal.h: No such file or directory
In file included from
//D/Programme/REDHAT~1/eCos/7708EVBMinimal_install/include/cyg/hal/hal_intr.h:17
3,
                 from
//D/Programme/REDHAT~1/eCos/packages/hal/sh/arch/v1_3_1/src/hal_mk_defs.c:49:
//D/Programme/REDHAT~1/eCos/7708EVBMinimal_install/include/cyg/infra/cyg_ass.h:5
7: pkgconf/infra.h: No such file or directory
make[1]: ***
[//D/Programme/REDHAT~1/eCos/7708EVBMinimal_install/include/cyg/hal/sh_offsets.i
nc] Error 1
make[1]: Leaving directory `/d/Programme/Red
Hat/eCos/7708EVBMinimal_build/hal/sh/arch/v1_3_1'
make: *** [build] Error 2

*** Process 255 terminated (rc=2)

Browsing the directories and looking at the makefiles I could not find a clue
where the missing file 'hal.h' could come from.
Another strange thing is sometimes the path notation '//D/...' is used and
sometimes '/d/...'.

Any ideas for this?

Greetings,

Christian Grebe

Dipl.-Ing.
ITK Dr. Kassen GmbH
Beim Eberacker 3
D-35633 Lahnau
Tel: +49 6441/6 50 05-14
Fax: +49 6441/6 50 05-29