[go-nuts] GCCGO instalation
Karla Falcão
/usr/include/linux/errno.h:4:23: erro fatal: asm/errno.h: No such file or directory
compilation terminated.
make[3]: ** [_muldi3.o] Error 1
make[3]: Leaving directory `/home/karla/cvs/objdir/i686-pc-linux-gnu/libgcc'
make[2]: ** [all-stage1-target-libgcc] Error 2
make[2]: Leaving directory `/home/karla/cvs/objdir'
make[1]: ** [stage1-bubble] Error 2
make[1]: Leaving directory `/home/karla/cvs/objdir'
make: ** [all] Error 2
I'll have to install the errno and restart the installation from scratch?
--Karla
Ian Lance Taylor
Yes.
On Ubuntu /usr/include/asm/errno.h is in the linux-libc-dev package. On
Fedora it's in the kernel-headers package.
Ian
Karla Falcão
Now, there was another problem which I tried to solve by installing packages and reinstalling everything, but I did not progress:
/opt/gold/bin/ld: cannot find -lc
collect2: ld returned 1 exit status
make[3]: ** [libgcc_s.so] Erro 1
make[3]: Saindo do diretório `/home/karla/cvs/objdir/i686-pc-linux-gnu/libgcc'
make[2]: ** [all-stage1-target-libgcc] Erro 2
make[2]: Saindo do diretório `/home/karla/cvs/objdir'
make[1]: ** [stage1-bubble] Erro 2
make[1]: Saindo do diretório `/home/karla/cvs/objdir'
make: ** [all] Erro 2
--Karla
> I already have installed this package, and yet on the installation failureDoes the file /usr/include/asm/errno.h exist on your system?
If not, you will need to figure out which package provides it for your
system.
Ian
Ian Lance Taylor
> Ok, problem solved!
>
> Now, there was another problem which I tried to solve by installing packages
> and reinstalling everything, but I did not progress:
>
> /opt/gold/bin/ld: cannot find -lc
> collect2: ld returned 1 exit status
> make[3]: ** [libgcc_s.so] Erro 1
> make[3]: Saindo do diretório
> `/home/karla/cvs/objdir/i686-pc-linux-gnu/libgcc'
> make[2]: ** [all-stage1-target-libgcc] Erro 2
> make[2]: Saindo do diretório `/home/karla/cvs/objdir'
> make[1]: ** [stage1-bubble] Erro 2
> make[1]: Saindo do diretório `/home/karla/cvs/objdir'
> make: ** [all] Erro 2
I assume you are building a native compiler, which is what happens by
default. The error "cannot find -lc" on GNU/Linux implies that you are
missing the file /usr/lib/libc.so. Does that file exist on your system?
Ian
Karla Falcão
>>default. The error "cannot find -lc" on GNU/Linux implies that you are
>>missing the file /usr/lib/libc.so. Does that file exist on your system?
--Karla
Ian Lance Taylor
>>>I assume you are building a native compiler, which is what happens by
>>>default. The error "cannot find -lc" on GNU/Linux implies that you are
>>>missing the file /usr/lib/libc.so. Does that file exist on your system?
>
> The file /usr/lib/libc.so does not exist. How do I get it? I already have
> installed the package linux-libc-dev.
On my Ubuntu Lucid based system the file /usr/lib/libc.so is in the
libc6-dev package.
Ian
Karla Falcão
De: Karla Falcão <icgop...@gmail.com>
Data: 17 de maio de 2011 14:42
Assunto: Re: [go-nuts] GCCGO instalation
Para: Ian Lance Taylor <ia...@google.com>
Which files that specify the semantics of Go in gccgo compiler?
--Karla
> Now ... If I change something, I'll have to make again? Where can I find aIf you change in something in the gccgo source code, then you have to
> better specification about it?
run make again to rebuild gccgo, yes.
I don't know what kind of specification you are looking for. gccgo
works like the rest of gcc, and there is a lot of documentation about
gcc available.
Ian
Ian Lance Taylor
> Which files that specify the semantics of Go in gccgo compiler?
The ones in gcc/go. In gcc/go/gofrontend you will find expressions.cc,
statements.cc, and types.cc.
Ian
Karla Falcão
Thanks.
--Karla
> The full typechecker are types.cc and types.h files?In general I would prefer that questions be asked on the mailing list
rather than to me directly. Thanks.
No, type checking is done in the check_types pass, and each Statement
and Expression has its own appropriate implementation.
Ian
Karla Falcão
-o generic-morestack-thread.o -MT generic-morestack-thread.o -MD -MP -MF generic-morestack-thread.dep -fexceptions -c ../../../gccgo/libgcc/generic-morestack-thread.c
../../../gccgo/libgcc/generic-morestack-thread.c: In the função ‘__wrap_pthread_create’:
../../../gccgo/libgcc/generic-morestack-thread.c:156:12: error: ‘EAGAIN’ undeclared (first use in this function)
../../../gccgo/libgcc/generic-morestack-thread.c:156:12: note: each undeclared identifier is reported only once for each function it appears in
make[3]: ** [generic-morestack-thread.o] Erro 1
make[3]: Leaving the directory `/home/karla/GCCGO/objdir/i686-pc-linux-gnu/libgcc'
make[2]: ** [all-stage1-target-libgcc] Erro 2
make[1]: ** [stage1-bubble] Erro 2
make: ** [all] Error 2
--Karla
Ian Lance Taylor
> What does this error :
>
> -o generic-morestack-thread.o -MT generic-morestack-thread.o -MD -MP -MF
> generic-morestack-thread.dep -fexceptions -c
> ../../../gccgo/libgcc/generic-morestack-thread.c
> ../../../gccgo/libgcc/generic-morestack-thread.c: In the função
> ‘__wrap_pthread_create’:
> ../../../gccgo/libgcc/generic-morestack-thread.c:156:12: error: ‘EAGAIN’
> undeclared (first use in this function)
> ../../../gccgo/libgcc/generic-morestack-thread.c:156:12: note: each
> undeclared identifier is reported only once for each function it appears in
> make[3]: ** [generic-morestack-thread.o] Erro 1
> make[3]: Leaving the directory
> `/home/karla/GCCGO/objdir/i686-pc-linux-gnu/libgcc'
> make[2]: ** [all-stage1-target-libgcc] Erro 2
> make[2]: Leaving the directory `/home/karla/GCCGO/objdir'
> make[1]: ** [stage1-bubble] Erro 2
> make[1]: Leaving the directory `/home/karla/GCCGO/objdir'
> make: ** [all] Error 2
Looks like the file gcc/generic-morestack-thread.c should have the line
#include <errno.h>
right by the existing line
#include <pthread.h>
I guess on some versions of GNU/Linux <pthread.h> includes <errno.h>, or
something like that. Rather odd that nobody else has noticed this,
though, as this file is compiled for all languages, not just for Go.
Ian