Re: [wgcc-dev] wgcc does not build

[Martin K. <mk...@gm...>]

Hi Markus,

On Tue, 10 Oct 2006, Duft Markus wrote:

> First: I'm really really glad to get some feedback at last ;o) please
> direct your mails to the int...@li... so
> the mails get archived... I'll in any case CC you if you don't want to
> subscribe.

ok, and please cc me.

> The last lines are less interesting than the first errors ;o) could you
> send me a complete output? How are you building, have you read the
> INSTALL file? You could also attach the output from env. Which version
> of Interix are you using, and which version of Windows.

ok, of course. I only took the last lines of the terminal. Now I tried 
2.0.3 too:

$ uname -X
System = Interix
Node = interix3
Release = 3.5
Version = SP-8.0.1969.45
Machine = x86
Processor = Intel_x86_Family15_Model2_Stepping8
HostSystem = Windows
HostRelease = SP4
HostVersion = 5.0

build was successful this time, I had some bad libs in 
CPPFLAGS / LDFLAGS / LIBS, which I cleared now before building. It was 
my fault.

> I did never try to link with wgcc output with ld, why would you like to
> do this? If it works, this could really be worth an extension. Does the
> resulting binary depend on the microsoft runtime, or the interix
> runtime. Can i use the windows api, and more important, can i use the
> microsoft debugger (visual studio).

This works, at least for a simple hello program. Even in both 
directions, i.e. within interix:

interix$ cc -c hello.c
interix$ gcc hello.o

The other direction would be:

interix$ gcc -c hello.c
win32> link.exe (with several options I currently don't have 
available, but I can search them later)

But both gave valid interix (i.e. POSIX CUI) executables.

The intension here is to explicitely not use the VC runtime, but the 
interix runtime and libc and all other libs available there. Therefore 
the Windows API is not and for me should not be available. I don't 
know about debugging support, but I read that it would be possible to 
debug plain POSIX apps with VS.

Debugging is not that important for me, as I currently want to build 
well known apps as bash, gnu make, gnu find etc. with cl.exe, just to 
verify that it works, and to be able to use cl.exe's warnings in 
comparison to gcc's warnings, just to possibly get the code more 
clean. I think it's better when it even works with several compilers.

Linking with gcc/ld is necessary for .so libs.

> Many questions ;o) maybe you want to try (after wgcc works ;o)) to only
> compile with wgcc, and manually link with ld and gather some experience
> in this direction.... I will try too!

Ok, will try with wgcc, too.

Martin