nanogui: ask for c++ compiler of m68k
Subject:
RE: [nanogui] ask for c++ compiler of m68k
From:
"L.Lehuerou" ####@####.####
Date:
20 Jul 2001 10:46:30 -0000
Message-Id: <4BF7E5384A8ED411A4A100E02900BC56265DA1@NETMAIL>
daniel ####@####.#### wrote :
> but i got this complier from others, only find m68k-pic-coff-gcc
> in /usr/loca/gnu/bin, there is no g++ compiler.
>
> cuz of i am a newbie about gcc, could tell me some conception?
> can gcc compile c++ program ? in X86 platfrom i use g++ not
> gcc to do this.
> as u said, i only should correct the links or add some path,
> can u tell hwo to do in detail?
>
I suppose you are working on a UNIX-like host.
IMPORTANT : as I am not used to LINUX/UNIX environment, someone
else should give a more accurate answer or correct the following.
(1) Either you have a path to /usr/loca/gnu/bin and m68k-pic-coff-gcc
is a symbolic link to another location (e.g to
/usr/local/m68k-pic-coff/bin).
Perhaps /usr/loca/gnu/bin/m68k-pic-coff-gcc link fails
reaching m68k-pic-coff-g++ as it's actual location is
/usr/local/m68k-pic-coff/bin/.
You could add the links to g++ and
all other gcc stuff (as, ar, c++, etc) in /usr/loca/gnu/bin
pointing to /usr/local/m68k-pic-coff/bin ones (you'd better do
that in a shell script and invoque this each time you want gcc
to point to the cross m68k-pic-coff cross version).
(2) or m68k-pic-coff-g++ is simply missing ! Try getting it from
the same place you found m68k-pic-coff-gcc ...
...or look at www.microcross.com. They have binaries covering a
great range of targets (for near the cost of shipment and media).
Note that I did not find a documentation on paths for gcc *standard*
location (i.e. documented), that match *usual*
paths of the binary distribution of those cross-compilers.
BTW if anyone knows about good and practical docs on this
subject, I'am interested (i.e. what is the general philosophy
and the practical usage of --prefix in configure option).
>
> And another thing make me confuse is what's the difference
> between m68k-pic-coff-gcc and m68k-coff-gcc.
The name of the actual gcc compiler is created by the *target*
option of "configure" when generating the compiler.
My m68k-coff-gcc comes from --target=m68k-coff in this case.
Look at gcc documentation at gnu.org or cygnus, about cross versions.
When you invoke "gcc" whithout options, it often means you use the
native (host X host) compiler.
Dragon Ball (your's) and 68060 (mine) targets are not the same and
some specific stuff has probably to be done in each version of the compiler.
Regards,
Luc.
