Re: [libposix-development] Some restructuring, preliminary (non-functional) x86-64 port

[Andreas K. <akr...@go...>]

On Thu, Jun 4, 2009 at 2:46 PM, Henrique Almeida <hd...@gm...> wrote:

> 2009/6/4 Andreas Krennmair <akr...@go...>:
> > Why not, if I may ask? It's not like a broken build suddenly stops git
> push
> > from working. Or do you always want to have a functioning build in git
> > master?
>
>  The current message is:
>
> gcc -std=c99 -Iinclude -Icompiler/gcc -Iruntime -Wall -Wextra -g
> -nostdlib -fPIC -Isystem/linux -Isystem/linux/i386 -c
> system/linux/syscalls.c -o output-i386/syscalls.o
> system/linux/syscalls.c:30:26: error: syscall_nums.h: Arquivo ou
> diretório inexistente
> system/linux/syscalls.c: In function ‘write’:
> system/linux/syscalls.c:34: error: ‘LINUX_SYS_write’ undeclared (first
> use in this function)
> system/linux/syscalls.c:34: error: (Each undeclared identifier is
> reported only once
> system/linux/syscalls.c:34: error: for each function it appears in.)
> system/linux/syscalls.c: In function ‘_Exit’:
> system/linux/syscalls.c:39: error: ‘LINUX_SYS_exit’ undeclared (first
> use in this function)
> system/linux/syscalls.c:40: warning: ‘noreturn’ function does return
> make: ** [output-i386/syscalls.o] Erro 1


Please the contents of
http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/compat/linux/arch/i386/linux_syscall.h?rev=1.83&content-type=text/x-cvsweb-markupinto
system/linux/i386/syscall_nums.h, then that should work.


>  SF repository is for code that always work. Broken commits must stay
> in local repositories.


... which depends on the definition of "working" and "broken". Anyway, good
luck with that, not every developer will have all supported operating
systems on all supported architectures available to check for breakages
prior to a commit. Heck,  I don't even have an x86 machine available.

Regards,
Andreas