* Problems when compiling gcc-2.95.1 for H8/300 target.
@ 1999-10-25 10:51 Eric Huiban
1999-10-26 4:44 ` Kai Ruottu
1999-10-31 13:57 ` Eric Huiban
0 siblings, 2 replies; 4+ messages in thread
From: Eric Huiban @ 1999-10-25 10:51 UTC (permalink / raw)
To: help-gcc
Hello,
I'm trying to compile gcc-2.95.1 for "H8/300-hms" on a "i586-pc-linux-gnulibc1
host". I previously compiled the native gcc 2.95.1 using the gcc-2.7.2.3 :
everything looked perfect. I'm compiling in a separate directory and use the
commands : "../gcc-2.95.1/configure --target=h8300-hms --with-gnu-as
--with-gnu-as" (no error messages) and "make bootstrap" or "make LANGUAGES=c".
Here the result is that no stdlib.h and no unistd.h files are found.
The binutils were also well compiled.
Does someone know or feel where i am doing a bad configuration ? I'm quite
new with gcc cross-compiler generation and use but i really don't think that
such error can be a remaining bug.
Here is the "end" of the screen output :
----top of listing----
make[3]: Entering directory `/mnt/hdb1/usr/src/gccobjdir/gcc'
rm -f libgcc2.a
if [ -d . ]; then \ cd .; \
rm -f libgcc.a ; \
else true; \
fi
make GCC_FOR_TARGET="./xgcc -B/usr/local/h8300-hms/bin/ -B./ -I/usr/local/h8300-hms/include" \
AR_FOR_TARGET="ar" \
AR_FLAGS_FOR_TARGET="rc" \
CC="gcc" CFLAGS="-g" \
HOST_PREFIX="" HOST_PREFIX_1="loser-" \
LANGUAGES="c " \
LIBGCC2_CFLAGS="-O2 -DCROSS_COMPILE -DIN_GCC -g -I./include -DDF=SF -DDI=SI -g1 -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED " libgcc2.a
make[4]: Entering directory `/mnt/hdb1/usr/src/gccobjdir/gcc'
rm -f tmplibgcc2.a
for name in _muldi3 _divdi3 _moddi3 _udivdi3 _umoddi3 _negdi2 _lshrdi3 _ashldi3 _ashrdi3 _ffsdi2 _udiv_w_sdiv _udivmoddi4 _cmpdi2 _ucmpdi2 _floatdidf _floatdisf _fixunsdfsi _fixunssfsi _fixunsdfdi _fixdfdi _fixunssfdi _fixsfdi _fixxfdi _fixunsxfdi _floatdixf _fixunsxfsi _fixtfdi _fixunstfdi _floatditf __gcc_bcmp _varargs __dummy _eprintf _bb _shtab _clear_cache _trampoline __main _exit _ctors _pure; \
do \
echo ${name}; \
./xgcc -B/usr/local/h8300-hms/bin/ -B./ -I/usr/local/h8300-hms/include -O2 -DCROSS_COMPILE -DIN_GCC -g -I./include -DDF=SF -DDI=SI -g1 -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I../../gcc-2.95.1/gcc -I../../gcc-2.95.1/gcc/config -I../../gcc-2.95.1/gcc/../include -c -DL${name} \
../../gcc-2.95.1/gcc/libgcc2.c -o ${name}.o; \
if [ $? -eq 0 ] ; then true; else exit 1; fi; \
ar rc tmplibgcc2.a ${name}.o; \
rm -f ${name}.o; \
done
_muldi3
./../gcc-2.95.1/gcc/libgcc2.c:41: stdlib.h: No such file or directory
./../gcc-2.95.1/gcc/libgcc2.c:42: unistd.h: No such file or directory
make[4]: *** [libgcc2.a] Error 1
make[4]: Leaving directory `/mnt/hdb1/usr/src/gccobjdir/gcc'
make[3]: *** [stmp-multilib-sub] Error 2
make[3]: Leaving directory `/mnt/hdb1/usr/src/gccobjdir/gcc'
make[2]: *** [stmp-multilib] Error 1
make[2]: Leaving directory `/mnt/hdb1/usr/src/gccobjdir/gcc'
make[1]: *** [bootstrap] Error 2
make[1]: Leaving directory `/mnt/hdb1/usr/src/gccobjdir/gcc'
make: *** [bootstrap] Error 2
bash#
----end of listing-----
Thank you !
Eric.
--
---------------------------------------------------------
Eric Huiban. Toulouse/France. E-mail : ehuiban@pyrenet.fr
Fidonet : 2:324/105, 2:324/105.351 Sparknet : 74:424/101
GedDoc BBS : 33 (0)5 6171 0229
---------------------------------------------------------
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Problems when compiling gcc-2.95.1 for H8/300 target.
1999-10-25 10:51 Problems when compiling gcc-2.95.1 for H8/300 target Eric Huiban
@ 1999-10-26 4:44 ` Kai Ruottu
1999-10-31 13:57 ` Kai Ruottu
1999-10-31 13:57 ` Eric Huiban
1 sibling, 1 reply; 4+ messages in thread
From: Kai Ruottu @ 1999-10-26 4:44 UTC (permalink / raw)
To: help-gcc
On Mon, 25 Oct 1999 19:39:28 +0200, Eric Huiban <ehuiban@pyrenet.fr>
wrote:
>I'm trying to compile gcc-2.95.1 for "H8/300-hms" on a "i586-pc-linux-gnulibc1
>host". I previously compiled the native gcc 2.95.1 using the gcc-2.7.2.3 :
>everything looked perfect. I'm compiling in a separate directory and use the
>commands : "../gcc-2.95.1/configure --target=h8300-hms --with-gnu-as
>--with-gnu-as" (no error messages) and "make bootstrap" or "make LANGUAGES=c".
>Here the result is that no stdlib.h and no unistd.h files are found.
>
>The binutils were also well compiled.
>
>Does someone know or feel where i am doing a bad configuration ? I'm quite
>new with gcc cross-compiler generation and use but i really don't think that
>such error can be a remaining bug.
For a compiler toolset one normally needs:
1. binutils with assembler, linker etc.
2. the C/C++ compiler binaries.
3. the C-library with headers and libs.
4. the debugger (with a possible simulator for the target).
Now you have the 1. and 2. but not the 3. and 4.
Solutions for the C-library :
1. build the C-library yourself, the Cygnus newlib is the recommended
one (there aren't alternatives...). Please see:
http://sourceware.cygnus.com/newlib
be prepared to struggle with the 'chicken and egg' problems...
2. get a precompiled gcc-2.95.1 for some other host, with prebuilt
libs and headers. Install the libs and headers and continue
building the extra libs... Or just use also these libs from the
distribution, neglecting the 'reinventing the wheel'. Please see:
http://www.nettilinja.fi/~ankosken/embtools.htm
Solutions for the debugger with a H8/300[HS]-simulator:
1. get GDB sources, configure and build for h8300-hms target. The
result is a text-based one. Use it with the 'ddd' GUI, using the
option '--debugger h8300-hms-gcc' when starting (if you use the
default name for the h8300-hms target GDB)
2. get Insight sources, configure and build for h8300-hms target.
The result is a tcl/tk-GUI-based one.
For the GDB/Insight sources, please see:
http://sourceware.cygnus.com/insight
and see the screenshots, link to the 'ddd' etc. The appearance is
quite the same under Linux as it is under Win32, www.nettilinja.fi/...
Cheers, Kai
^ permalink raw reply [flat|nested] 4+ messages in thread
* Problems when compiling gcc-2.95.1 for H8/300 target.
1999-10-25 10:51 Problems when compiling gcc-2.95.1 for H8/300 target Eric Huiban
1999-10-26 4:44 ` Kai Ruottu
@ 1999-10-31 13:57 ` Eric Huiban
1 sibling, 0 replies; 4+ messages in thread
From: Eric Huiban @ 1999-10-31 13:57 UTC (permalink / raw)
To: help-gcc
Hello,
I'm trying to compile gcc-2.95.1 for "H8/300-hms" on a "i586-pc-linux-gnulibc1
host". I previously compiled the native gcc 2.95.1 using the gcc-2.7.2.3 :
everything looked perfect. I'm compiling in a separate directory and use the
commands : "../gcc-2.95.1/configure --target=h8300-hms --with-gnu-as
--with-gnu-as" (no error messages) and "make bootstrap" or "make LANGUAGES=c".
Here the result is that no stdlib.h and no unistd.h files are found.
The binutils were also well compiled.
Does someone know or feel where i am doing a bad configuration ? I'm quite
new with gcc cross-compiler generation and use but i really don't think that
such error can be a remaining bug.
Here is the "end" of the screen output :
----top of listing----
make[3]: Entering directory `/mnt/hdb1/usr/src/gccobjdir/gcc'
rm -f libgcc2.a
if [ -d . ]; then \ cd .; \
rm -f libgcc.a ; \
else true; \
fi
make GCC_FOR_TARGET="./xgcc -B/usr/local/h8300-hms/bin/ -B./ -I/usr/local/h8300-hms/include" \
AR_FOR_TARGET="ar" \
AR_FLAGS_FOR_TARGET="rc" \
CC="gcc" CFLAGS="-g" \
HOST_PREFIX="" HOST_PREFIX_1="loser-" \
LANGUAGES="c " \
LIBGCC2_CFLAGS="-O2 -DCROSS_COMPILE -DIN_GCC -g -I./include -DDF=SF -DDI=SI -g1 -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED " libgcc2.a
make[4]: Entering directory `/mnt/hdb1/usr/src/gccobjdir/gcc'
rm -f tmplibgcc2.a
for name in _muldi3 _divdi3 _moddi3 _udivdi3 _umoddi3 _negdi2 _lshrdi3 _ashldi3 _ashrdi3 _ffsdi2 _udiv_w_sdiv _udivmoddi4 _cmpdi2 _ucmpdi2 _floatdidf _floatdisf _fixunsdfsi _fixunssfsi _fixunsdfdi _fixdfdi _fixunssfdi _fixsfdi _fixxfdi _fixunsxfdi _floatdixf _fixunsxfsi _fixtfdi _fixunstfdi _floatditf __gcc_bcmp _varargs __dummy _eprintf _bb _shtab _clear_cache _trampoline __main _exit _ctors _pure; \
do \
echo ${name}; \
./xgcc -B/usr/local/h8300-hms/bin/ -B./ -I/usr/local/h8300-hms/include -O2 -DCROSS_COMPILE -DIN_GCC -g -I./include -DDF=SF -DDI=SI -g1 -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I../../gcc-2.95.1/gcc -I../../gcc-2.95.1/gcc/config -I../../gcc-2.95.1/gcc/../include -c -DL${name} \
../../gcc-2.95.1/gcc/libgcc2.c -o ${name}.o; \
if [ $? -eq 0 ] ; then true; else exit 1; fi; \
ar rc tmplibgcc2.a ${name}.o; \
rm -f ${name}.o; \
done
_muldi3
./../gcc-2.95.1/gcc/libgcc2.c:41: stdlib.h: No such file or directory
./../gcc-2.95.1/gcc/libgcc2.c:42: unistd.h: No such file or directory
make[4]: *** [libgcc2.a] Error 1
make[4]: Leaving directory `/mnt/hdb1/usr/src/gccobjdir/gcc'
make[3]: *** [stmp-multilib-sub] Error 2
make[3]: Leaving directory `/mnt/hdb1/usr/src/gccobjdir/gcc'
make[2]: *** [stmp-multilib] Error 1
make[2]: Leaving directory `/mnt/hdb1/usr/src/gccobjdir/gcc'
make[1]: *** [bootstrap] Error 2
make[1]: Leaving directory `/mnt/hdb1/usr/src/gccobjdir/gcc'
make: *** [bootstrap] Error 2
bash#
----end of listing-----
Thank you !
Eric.
--
---------------------------------------------------------
Eric Huiban. Toulouse/France. E-mail : ehuiban@pyrenet.fr
Fidonet : 2:324/105, 2:324/105.351 Sparknet : 74:424/101
GedDoc BBS : 33 (0)5 6171 0229
---------------------------------------------------------
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Problems when compiling gcc-2.95.1 for H8/300 target.
1999-10-26 4:44 ` Kai Ruottu
@ 1999-10-31 13:57 ` Kai Ruottu
0 siblings, 0 replies; 4+ messages in thread
From: Kai Ruottu @ 1999-10-31 13:57 UTC (permalink / raw)
To: help-gcc
On Mon, 25 Oct 1999 19:39:28 +0200, Eric Huiban <ehuiban@pyrenet.fr>
wrote:
>I'm trying to compile gcc-2.95.1 for "H8/300-hms" on a "i586-pc-linux-gnulibc1
>host". I previously compiled the native gcc 2.95.1 using the gcc-2.7.2.3 :
>everything looked perfect. I'm compiling in a separate directory and use the
>commands : "../gcc-2.95.1/configure --target=h8300-hms --with-gnu-as
>--with-gnu-as" (no error messages) and "make bootstrap" or "make LANGUAGES=c".
>Here the result is that no stdlib.h and no unistd.h files are found.
>
>The binutils were also well compiled.
>
>Does someone know or feel where i am doing a bad configuration ? I'm quite
>new with gcc cross-compiler generation and use but i really don't think that
>such error can be a remaining bug.
For a compiler toolset one normally needs:
1. binutils with assembler, linker etc.
2. the C/C++ compiler binaries.
3. the C-library with headers and libs.
4. the debugger (with a possible simulator for the target).
Now you have the 1. and 2. but not the 3. and 4.
Solutions for the C-library :
1. build the C-library yourself, the Cygnus newlib is the recommended
one (there aren't alternatives...). Please see:
http://sourceware.cygnus.com/newlib
be prepared to struggle with the 'chicken and egg' problems...
2. get a precompiled gcc-2.95.1 for some other host, with prebuilt
libs and headers. Install the libs and headers and continue
building the extra libs... Or just use also these libs from the
distribution, neglecting the 'reinventing the wheel'. Please see:
http://www.nettilinja.fi/~ankosken/embtools.htm
Solutions for the debugger with a H8/300[HS]-simulator:
1. get GDB sources, configure and build for h8300-hms target. The
result is a text-based one. Use it with the 'ddd' GUI, using the
option '--debugger h8300-hms-gcc' when starting (if you use the
default name for the h8300-hms target GDB)
2. get Insight sources, configure and build for h8300-hms target.
The result is a tcl/tk-GUI-based one.
For the GDB/Insight sources, please see:
http://sourceware.cygnus.com/insight
and see the screenshots, link to the 'ddd' etc. The appearance is
quite the same under Linux as it is under Win32, www.nettilinja.fi/...
Cheers, Kai
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~1999-10-31 13:57 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-10-25 10:51 Problems when compiling gcc-2.95.1 for H8/300 target Eric Huiban
1999-10-26 4:44 ` Kai Ruottu
1999-10-31 13:57 ` Kai Ruottu
1999-10-31 13:57 ` Eric Huiban
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).