public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: mike@penbex.com.tw (mike)
To: <crossgcc@sources.redhat.com>
Subject: Re:
Date: Sun, 01 Apr 2001 00:00:00 -0000	[thread overview]
Message-ID: <003a01c07c65$c3469da0$9e0150c0@penbex.com.tw> (raw)
Message-ID: <20010401000000.qNdDuhM2MqvxX86SA3n9oAKmtLOvE5Zh-jvcoUl9ZZs@z> (raw)
In-Reply-To: <NEBBJIKLHKODECFJDDFGOEGFCDAA.kcmahadev@zilogindia.com>

Hi, Mahadev.
I'm also works with m68k-coff, and succeed build on my windoze.
The problem you got is lack of header files, because gcc needs
them to build libgcc.a. Therefore, get newlib package and put
them in the directory the same as gcc (/home/kc), and run
configure script of gcc again. If you have put newlib in
other directory, it's ok, using
'--with-header=/somewhere/newlib/libc/include' with
configure script of gcc.

----- Original Message -----
From: "Mahadev K Cholachagudda" <kcmahadev@zilogindia.com>
To: "Crossgcc-Help" <crossgcc@sources.redhat.com>
Sent: Friday, January 12, 2001 7:21 PM
Subject: FW:


>
> Hello all,
>
> I want to compile and build the gcc ( cross compiler) for m68k-coff on
> Linux.
> I successfully built the cross compiler by using the FAQ provided by the
> www.obsw.com and running the shell script. But i want to build the tools
one
> by one and I got the errors as below.
>
> I performed the following.
>
> /home/kc> mkdir build-bin
> /home/kc> cd build-bin
> /home/kc/build-bin>
> ../binutils-2.9.1/configure --target=m68k-coff --prefix=/home/kc/gnu-tools
>
> ....
> /home/kc/build-bin> make all install
> /home/kc/build-bin> mkdir ../build-gcc
> /home/kc/build-bin> cd ../build-gcc
> /home/kc/build-bin>
>
../gcc-2.95.2/configure --target=m68k-coff --prefix=/home/kc/gnu-tools --wit
> h-local-prefix=/home/kc/gnu-tools --with-newlib --enable-languages="c"
>
> ..... successfully
>
> /home/kc/build-bin> make all install
> :
> :
> ../../gcc-2.95.2/gcc/libgcc2.c:41: stdlib.h: No such file or directory
> ../../gcc-2.95.2/gcc/libgcc2.c:42: unistd.h: No such file or directory
> make[3]: *** [libgcc2.a] Error 1
> make[3]: Leaving directory `/home/kc/build-gcc/gcc'
> make[2]: *** [stmp-multilib-sub] Error 2
> make[2]: Leaving directory `/home/kc/build-gcc/gcc'
> make[1]: *** [stmp-multilib] Error 1
> make[1]: Leaving directory `/home/kc/build-gcc/gcc'
> make: *** [all-gcc] Error 2
> /home/kc/build-bin>
>
>
> Could any one point me where can i get these header files in order to
> compile the gcc ?
>
> Thanks for any help
>
> With best regards,
>
> \/ \/   Mahadev K. Cholachagudda
> O . O   mailto:kcmahadev@zilogindia.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
>


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

  reply	other threads:[~2001-04-01  0:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-11 21:46 FW: Mahadev K Cholachagudda
2001-01-11 23:09 ` mike [this message]
2001-01-12  4:04   ` gcc-m68k cross compiler problem gcc2.95.2 Mahadev K Cholachagudda
2001-01-12  5:38     ` Pierre Saucourt-Harmel (r54698)
2001-01-12 22:54       ` Mahadev K Cholachagudda
2001-04-01  0:00         ` Mahadev K Cholachagudda
2001-04-01  0:00       ` Pierre Saucourt-Harmel (r54698)
2001-04-01  0:00     ` Mahadev K Cholachagudda
2001-04-01  0:00   ` mike
2001-04-01  0:00 ` FW: Mahadev K Cholachagudda
     [not found] <362839576.2566860.1706922246488.ref@mail.yahoo.com>
2024-02-03  1:04 ` Re, Ellen Hester
  -- strict thread matches above, loose matches on Subject: below --
2003-03-01  6:38 Windows.net
2003-03-01  6:38 RE: Windows.net
2003-03-01  6:38 RE: Windows.net
2003-03-01  6:38 RE: Windows.net
2000-07-18  3:42 Fw: alexperi
2000-07-18  6:54 ` Matthew Majka
1998-05-19  9:59 No Subject Pete Popov
1998-05-22  9:56 ` Pete Popov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='003a01c07c65$c3469da0$9e0150c0@penbex.com.tw' \
    --to=mike@penbex.com.tw \
    --cc=crossgcc@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).