public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
* Problems in building gcc on linux
@ 2000-09-06  6:41 RakeshN
  2000-09-06  8:15 ` [crossgcc]Problems " thunder7
  0 siblings, 1 reply; 4+ messages in thread
From: RakeshN @ 2000-09-06  6:41 UTC (permalink / raw)
  To: 'gcc-help@gcc.gnu.org', 'crossgcc@sources.redhat.com'

 
Hi ,

I am building gcc on linux 6.1 .

My configuration command is ----

configure --target=h8300-hms --host=i386-coff-go32 --build=sun4 --prefix=/b/dosbin

My target is hitachi h8/300 processor for MS-DOS.

After configuring successfully i gave the command

make all

make info 

make install. But there are some errors....

My queries are

1] There is a makefile in each and every directory. Should i make them all individually?

2] There are errors reported during make. Please clarify these errors?

In make all--------

make[1]: i386-coff-go32-ar: Command not found
make[1]: *** [libiberty.a] Error 127
make: *** [all-libiberty] Error 2

In make info-------

make[1]: i386-coff-go32-ar: Command not found
make[1]: *** [libiberty.a] Error 127
make: *** [all-libiberty] Error 2

In make install-----

In file included from /root/rakesh/src/gcc/gencheck.c:21:
hconfig.h:1: auto-build.h: No such file or directory
make[1]: *** [gencheck.o] Error 1
make: *** [install-gcc] Error 2

Thanks in advance


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [crossgcc]Problems in building gcc on linux
  2000-09-06  6:41 Problems in building gcc on linux RakeshN
@ 2000-09-06  8:15 ` thunder7
  0 siblings, 0 replies; 4+ messages in thread
From: thunder7 @ 2000-09-06  8:15 UTC (permalink / raw)
  To: crossgcc

On Wed, Sep 06, 2000 at 07:12:13PM +0530, RakeshN wrote:
>  
> Hi ,
> 
> I am building gcc on linux 6.1 .
> 
> My configuration command is ----
> 
> configure --target=h8300-hms --host=i386-coff-go32 --build=sun4 --prefix=/b/dosbin
> 
> My target is hitachi h8/300 processor for MS-DOS.
> 
IIRC --host=i386-coff-go32 means you are building it on an
i386-coff-go32 machine, which you are not, since you are in fact
building it on a linux machine. You cannot create a compiler to run on
the hitachi without first creating a cross compiler from linux to the
hitachi and with that gcc (often called i386-go32-gcc or something like
that) compile the compiler you want.

I suggest finding the crossgcc FAQ and following the steps detailed
therein.

Good luck,
Jurriaan
-- 
Gypsie Borg: You'll soon be assimilated by a tall dark stranger
GNU/Linux 2.2.18pre2 SMP 2 users load av: 0.12 0.20 0.09

------
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] 4+ messages in thread

* Re: Problems in building gcc on linux
@ 2000-09-06  7:50 Michael Sokolov
  0 siblings, 0 replies; 4+ messages in thread
From: Michael Sokolov @ 2000-09-06  7:50 UTC (permalink / raw)
  To: crossgcc, gcc-help, rakeshn

RakeshN <rakeshn@kpit.com> wrote:

> I am building gcc on linux 6.1 .
>
> My configuration command is ----
>
> configure --target=h8300-hms --host=i386-coff-go32 --build=sun4 --prefix=/b/dosbin
>
> My target is hitachi h8/300 processor for MS-DOS.
>
> [...]
>
> make[1]: i386-coff-go32-ar: Command not found

What you are doing is called a Canadian cross. Since your compiler is going to
be hosted on a system (MS-DOS) other than the one you are building it on
(Linux), you must build it on your Linux box with a Linux x MS-DOS cross-
compiler. I.e., you must first build that and then use it to build your MS-DOS
x H8/300 compiler. Building a cross-compiler with a cross-compiler is called
Canadian cross. You must also build a Linux x H8/300 cross-compiler before you
build your MS-DOS x H8/300 cross-compiler, because building the latter will
need it to build target libraries. This is all explained very well in Ian Lance
Taylor's "The GNU configure and build system", see:

http://www.airs.com/ian/configure/

> 1] There is a makefile in each and every directory. Should i make them all individually?

No, you just run make in the top level build directory and it will
automatically descend into every subdirectory.

--
Michael Sokolov		Harhan Engineering Laboratory
Public Service Agent	International Free Computing Task Force
			International Engineering and Science Task Force
			615 N GOOD LATIMER EXPY STE #4
			DALLAS TX 75204-5852 USA

Phone: +1-214-824-7693 (Harhan Eng Lab office)
E-mail: msokolov@ivan.Harhan.ORG (ARPA TCP/SMTP) (UUCP coming soon)

------
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] 4+ messages in thread

* RE: Problems in building gcc on linux
@ 2000-09-06  6:54 Clive Davies
  0 siblings, 0 replies; 4+ messages in thread
From: Clive Davies @ 2000-09-06  6:54 UTC (permalink / raw)
  To: 'RakeshN', 'gcc-help@gcc.gnu.org',
	'crossgcc@sources.redhat.com'

You just have to run make in the top level directory (the same place you ran
configure)

As for the errors, it looks like make can't find binutils for your target.
Assuming you've built/installed them, have a poke around in the gcc
makefiles to figure out why it can't find them.

Clive

-----Original Message-----
From: RakeshN [ mailto:rakeshn@kpit.com ]
Sent: 06 September 2000 14:42
To: 'gcc-help@gcc.gnu.org'; 'crossgcc@sources.redhat.com'
Subject: Problems in building gcc on linux


 

------
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] 4+ messages in thread

end of thread, other threads:[~2000-09-06  8:15 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-09-06  6:41 Problems in building gcc on linux RakeshN
2000-09-06  8:15 ` [crossgcc]Problems " thunder7
2000-09-06  6:54 Problems " Clive Davies
2000-09-06  7:50 Michael Sokolov

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).