* Making a m68k-coff crosscompiler
@ 2000-11-26 3:53 Gerjan Teselink
2000-11-26 22:08 ` Alexandre Oliva
0 siblings, 1 reply; 2+ messages in thread
From: Gerjan Teselink @ 2000-11-26 3:53 UTC (permalink / raw)
To: gcc-help
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2706 bytes --]
Hello,
Â
IÂ have tried to compile m68k-coff on Debian 2.1 and 2.2.
But it won't compile. Binutils 2.10.1 and GCC 2..95.2 have both the
prefix /Local/Pro.
Â
In the 'configure' it detects the includefiles in
/usr/include. When I start to compile I get this errors:
Â
../../gcc-2.95/gcc/libgcc2.c:41: stdlib.h: No such file or
directory ../../gcc-2.95/gcc/libgcc2.c:42: unistd.h: No such file or
directory make[2]: *** [libgcc2.a] Error 1 make[2]: Leaving directory
`/home/teg/gcc-build/gcc' make[1]: *** [stmp-multilib-sub] Error
2 make[1]: Leaving directory `/home/teg/gcc-build/gcc' make: ***
[stmp-multilib] Error 1
Â
I fixed it by copying the complete /usr/include directory to
the gcc-build directory. But that is not a solution because it later on the same
error is in another directory libio
Â
But if i copy it every time I it will
compile till the next 2 errors come and i don't know what i can
do about it:
Â
checking whether the C compiler
(/home/gerjan/build-gcc/gcc/xgcc -B/home/gerjan/build-gcc/gcc/
-B/Local/Pro/m68k-coff/bin/ -g -O2 ) works... no configure: error:
installation or configuration problem: C compiler cannot create
executables. make[1]: Entering directory
`/home/gerjan/build-gcc/m68k-coff/libio' test x"no" != xyes ||\ Â
/home/gerjan/build-gcc/gcc/xgcc -B/home/gerjan/build-gcc/gcc/
-B/Local/Pro/m68k-coff/bin/ -c -g -O2 -I.
-I../../../gcc-2.95.2/libio  ../../../gcc-2.95.2/libio/filedoalloc.c
-o pic/filedoalloc.o /home/gerjan/build-gcc/gcc/xgcc
-B/home/gerjan/build-gcc/gcc/ -B/Local/Pro/m68k-coff/bin/ -c -g -O2 -I.
-I../../../gcc-2.95.2/libio ../../../gcc-2.95.2/libio/filedoalloc.c In
file included from
../../../gcc-2.95.2/libio/libio.h:30, Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
from
../../../gcc-2.95.2/libio/iolibio.h:1, Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
from
../../../gcc-2.95.2/libio/libioP.h:47, Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â
from ../../../gcc-2.95.2/libio/filedoalloc.c:45: _G_config.h:43: parse error
before `_G_sigset_t' _G_config.h:43: warning: data definition has no type or
storage class make[1]: *** [filedoalloc.o] Error 1 make[1]: Leaving
directory `/home/gerjan/build-gcc/m68k-coff/libio' make: ***
[all-target-libio] Error 2
Â
My questions are. Are there more people that have to copy the
/usr/include directory in e.g. the gcc directory? Â
Â
Is this a serious problem? configure: error: installation or
configuration problem: C compiler cannot create executables.
And what can i do about this _G_config.h file error?
Â
Thanks,
Â
Gerjan Teselink
Â
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Making a m68k-coff crosscompiler
2000-11-26 3:53 Making a m68k-coff crosscompiler Gerjan Teselink
@ 2000-11-26 22:08 ` Alexandre Oliva
0 siblings, 0 replies; 2+ messages in thread
From: Alexandre Oliva @ 2000-11-26 22:08 UTC (permalink / raw)
To: Gerjan Teselink; +Cc: gcc-help
On Nov 26, 2000, "Gerjan Teselink" <G.Teselink@jonker.nl> wrote:
> In the 'configure' it detects the includefiles in /usr/include. When I start to compile I get this errors:
Get newlib. The native header files won't do for the cross build.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2000-11-26 22:08 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-11-26 3:53 Making a m68k-coff crosscompiler Gerjan Teselink
2000-11-26 22:08 ` Alexandre Oliva
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).