* building gcc m68k-coff
@ 2000-10-11 11:26 ron tal
2000-10-11 12:01 ` Aaron J. Grier
0 siblings, 1 reply; 6+ messages in thread
From: ron tal @ 2000-10-11 11:26 UTC (permalink / raw)
To: crossgcc
Hi,
continuing from earlier email:
this is the output that I get when I do make:
as you can see, there are two libraries that the compiler
did not find.
let me know if you can help, ronen.
/home/ronenl/usr/local/make
make[1]: Entering directory
`/home/users/ronenl/usr/local/binutils-2.10/libiberty'
test x"no" != xyes || \
gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include -W -Wall
-Wtraditional argv.c -o pic/argv.o
gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include -W -Wall
-Wtraditional argv.c
argv.c:38: string.h: No such file or directory
argv.c:39: stdlib.h: No such file or directory
make[1]: *** [argv.o] Error 1
make[1]: Leaving directory
`/home/users/ronenl/usr/local/binutils-2.10/libiberty'
make: *** [all-libiberty] Error 2
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com .
Share information about yourself, create your own public profile at
http://profiles.msn.com .
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: building gcc m68k-coff
2000-10-11 11:26 building gcc m68k-coff ron tal
@ 2000-10-11 12:01 ` Aaron J. Grier
0 siblings, 0 replies; 6+ messages in thread
From: Aaron J. Grier @ 2000-10-11 12:01 UTC (permalink / raw)
To: ron tal; +Cc: crossgcc
On Wed, Oct 11, 2000 at 06:26:10PM +0000, ron tal wrote:
> /home/ronenl/usr/local/make
> make[1]: Entering directory
> `/home/users/ronenl/usr/local/binutils-2.10/libiberty'
> test x"no" != xyes || \
> gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include -W -Wall
> -Wtraditional argv.c -o pic/argv.o
> gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include -W -Wall
> -Wtraditional argv.c
> argv.c:38: string.h: No such file or directory
> argv.c:39: stdlib.h: No such file or directory
> make[1]: *** [argv.o] Error 1
> make[1]: Leaving directory
> `/home/users/ronenl/usr/local/binutils-2.10/libiberty'
> make: *** [all-libiberty] Error 2
this appears to be an even more basic problem... your system compiler
appears to be missing header files.
does a simple program which #includes string.h and stdlib.h, and calls
functions like atoi and strlen compile and execute properly on your
system with the native compiler?
--
Aaron J. Grier | Frye Electronics, Tigard, OR | aaron@frye.com
"Add [Windows] ME to an old PC with a `mere' 32 MB of memory, and your
hard disk will be busier than a one-armed man juggling knives."
-- Winn L. Rosch
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: building gcc m68k-coff
2000-10-11 11:25 ` Aaron J. Grier
@ 2000-10-12 15:10 ` Michael Schwingen
0 siblings, 0 replies; 6+ messages in thread
From: Michael Schwingen @ 2000-10-12 15:10 UTC (permalink / raw)
To: crossgcc
On Wed, Oct 11, 2000 at 11:24:40AM -0700, Aaron J. Grier wrote:
>
> another alternative is to use the "one tree" method of building, as
> shown in http://www.objsw.com/CrossGCC/FAQ-4.html#ss4.2 . I have
> succesfully used the process to build m68k-rtems-elf, and m68k-elf, and
> a canadian cross for m68k-rtems-elf running on i386-cygwin.
I would also suggest going that way - I have successfully used it for
linux-hosted cross-compilers for m68k-coff, powerpc-eabi, sh-coff, and for
cross-compiling cygwin-to-sh/powerpc-compilers under linux.
The nice thing is that once you have everything set up, you get all the
needed tools in one go, with one simple command - building a new compiler
version or a compiler for a different target is quite easy then.
cu
Michael
--
Michael Schwingen, Ahornstrasse 36, 52074 Aachen
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: building gcc m68k-coff
2000-10-11 9:53 ron tal
@ 2000-10-11 11:25 ` Aaron J. Grier
2000-10-12 15:10 ` Michael Schwingen
0 siblings, 1 reply; 6+ messages in thread
From: Aaron J. Grier @ 2000-10-11 11:25 UTC (permalink / raw)
To: crossgcc
On Wed, Oct 11, 2000 at 04:52:36PM +0000, ron tal wrote:
> the major problem I was facing: argv.c lines 38,39 : <stdlib.h>
> <string.h> could Not be find.
>
> I was suggested to do:
>
> --with-headers /newlib/libc/include which copied the directory
> but still did not solved the problem.
look at the output of your make and notice the flags being passed to the
compiler. there should be a -I<directory where newlib string.h is>. if
that is not there, you can manually edit the makefile to add it. (why
isn't it added? I do not know, but the answer could be found by digging
through the autoconf / automake configuration files.)
another alternative is to use the "one tree" method of building, as
shown in http://www.objsw.com/CrossGCC/FAQ-4.html#ss4.2 . I have
succesfully used the process to build m68k-rtems-elf, and m68k-elf, and
a canadian cross for m68k-rtems-elf running on i386-cygwin.
--
Aaron J. Grier | Frye Electronics, Tigard, OR | aaron@frye.com
"Add [Windows] ME to an old PC with a `mere' 32 MB of memory, and your
hard disk will be busier than a one-armed man juggling knives."
-- Winn L. Rosch
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* building gcc m68k-coff
@ 2000-10-11 11:25 ron tal
0 siblings, 0 replies; 6+ messages in thread
From: ron tal @ 2000-10-11 11:25 UTC (permalink / raw)
To: crossgcc
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com .
Share information about yourself, create your own public profile at
http://profiles.msn.com .
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* building gcc m68k-coff
@ 2000-10-11 9:53 ron tal
2000-10-11 11:25 ` Aaron J. Grier
0 siblings, 1 reply; 6+ messages in thread
From: ron tal @ 2000-10-11 9:53 UTC (permalink / raw)
To: crossgcc
Hi,
CrossGCC FAQ: "How to configure, build, and install GCC as cross-compiler"
This is the document that I have been working all along for the past week,
which did NOT lead to any progress.
It seems to me at this point that there is really NO absolute
reliable documentation for how to configure, build, and install
cross-compiler.
I would like to know: what is the likelyhood that someone who grabs
this document and follow the procedure, will get a working version
in his 1st trial (or, second)?
from my exeperience, searching in all kinds of FAQ, for suitable
document to answer for clean answer of how to configure/build/install
the gcc as cross-compiler, the answers varies so much, and the patches
the each one of you had to work around are huge.
We all know that working with a new tool at first time is the hardest thing;
especially, when working with an open source that can be touched
and changed by many people. I get advices from you, according for your
experience with the gcc configure; with luck, we are working on the same
platform and having the same problem.
I am so frustrated from all of this.
I will put down as much info as I can (detailed) and I would expect
to get an inteligent answer for what I should do, and why I should do
that...without understanding of the the reasoning, I would be lost.
I am working on sun_sparc_solaris computer, and I would like to get a
cross compiler for the m68k-coff cpu.
that what I have in my direcory:
/home/users/ronenl/
newlib-1.8.2/ unpacked
gdb-5.0/ unpacked
gcc-2.95.2/ unpacked
binutils-2.10/ unpacked
build-binutils/ empty
buils-gcc/ empty
build-newlib/ empty
build-gdb/ empty
I am quoting from the documnt:
( http://www.objsw.com/CrossGCC/FAQ-4.html )
cd /home/foo
host=sparc-sun-solaris
target=m68k-coff
prefix=/bar
i=$prefix/bin --> what is the use of i???
mkdir build-binutils build-gcc build-newlib build-gdb
cd build-binutils
../binutils-2.9/configure --target=$target --prefix=$prefix -v
make all install
Q: can someone take the time and give me a specific details of what I need
to change to be able to pass this stage (I am not talking
yet of the next steps).
the major problem I was facing: argv.c lines 38,39 : <stdlib.h>
<string.h> could Not be find.
I was suggested to do:
--with-headers /newlib/libc/include which copied the directory
but still did not solved the problem.
I am sure that alot of people here dealt with this kind of problem,
and I suggest that we should strive to have a least one
documet that is reliable enough to the gcc beginners.
thanx, ronen.
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com .
Share information about yourself, create your own public profile at
http://profiles.msn.com .
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2000-10-12 15:10 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-10-11 11:26 building gcc m68k-coff ron tal
2000-10-11 12:01 ` Aaron J. Grier
-- strict thread matches above, loose matches on Subject: below --
2000-10-11 11:25 ron tal
2000-10-11 9:53 ron tal
2000-10-11 11:25 ` Aaron J. Grier
2000-10-12 15:10 ` Michael Schwingen
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).