Re: [Oslib-devel] compiling ok on cygwin, but clean goes badly

[Luca A. <luc...@em...>]

Hi Paul,

as I previously wrote, cygwin is not supported (since I have not a
cygwin installation for testing).
There are some problems to be solved:
- cygwin uses a different executable format (not ELF nor COFF). Not a
big problem: we can generate a multiboot compliant image.
- the usual problem with the "_" prefix that some compilers attach to
all symbols as a prefix (this is the reason why you cannot use linux.mk,
as you already discovered)
- cygwin seems to introduce a call to alloca() in the startup of all
programs, and I do not know why...

Some time ago, I started to hack on it, and I wrote an patch:
http://sourceforge.net/tracker/index.php?func=detail&aid=718981&group_id=14468&atid=314468
(it basically introduces some new win32*.mk configuration files).
With such patch, it is possible to compile oslib with cygwin, but the
resulting executables _will not work_.
The patch is there just in case someone is willing to work on it and to
debug the problem (I think that the alloca() call is responsable for the
crash...).

If someone on the list has more knowledge about cygwin (in particular,
why is it insertig the malloca() call? Just to get the stack pointer?)
and is willing to help, let me know...

> I just had the idea of copying my oslib directory in cygwin, run a bash 
> shell
> and try make in the oslib directory...
> 
> It compiled without problems!
As you already discovered, it will not link :(
 
				Luca
-- 
_____________________________________________________________________________
Copy this in your signature, if you think it is important:
                               N O    W A R ! ! !



--
Email.it, the professional e-mail, gratis per te: http://www.email.it/f

Sponsor:
Sei un webmaster, vuoi guadagnare? Affiliati ad Artefiori. Clicca qui!
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=751&d=10-7