linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wang Yong <wung_y@263.net>
To: Momchil Velikov <velco@fadata.bg>
Cc: linux-ce-devel <linuxce-devel@linuxce.org>,
	linuxppc embedded mail list
	<linuxppc-embedded@lists.linuxppc.org>,
	linux-ppc <linuxppc-dev@lists.linuxppc.org>
Subject: Re: help, build Cross GCC
Date: Sat, 30 Oct 1999 09:48:47 +0800	[thread overview]
Message-ID: <381A4E7F.558A54C0@263.net> (raw)
In-Reply-To: 38199B27.492FE947@fadata.bg


thank you sir, i have got xgcc. but now the problem is glibc. it seems
glibc2.0 still support PPC. GNU say glibc for ppc is still under
development.
how about libc?

Momchil Velikov wrote:
> 
> I built a cross-dev environment sometime ago. Here's what I did:
> 
> 0. got glibc-?.tar.gz from the usual places
>    get binutils-?.tar.gz
>    get egcs-?.tar.gz
> 
> 1. Built and installed binutils
> 
> 2. Began with the egcs
>    configure --prefix=/usr/local                   \
>              --build=i686-pc-linux-gnu             \
>              --host=i686-pc-linux-gnu              \
>              --target=powerpc-unknown-linux-gnu
>    make LANGUAGES=c
>    make -k
> /* make fails, trying to build libgcc.a */
> 
>    make -k LANGUAGES=c install
> /* now we have a compiler, which compiles. We can't link yet, so
>  * we can't create shared libs or executables, but we _can_ create
>  * static glibc
>  */
> 
> 3. Began with glibc
>    configure --prefix=/usr/local                 \
>              --build=i686-pc-linux-gnu           \
>              --host=powerpc-unknown-linux-gnu    \
>              --enable-add-ons=crypt,linuxthreads \
>              --disable-profile
> 
>    make -k
> /* build fails when trying to link some execitables
>  * and some shared libs
>  */
> 
>    make -k install install_root=whatever
> /* now we have enough headers and static librararies to complete
>  * the build of gcc
>  */
> 
> 4. Back to egcs
>    make
>    make install
> /* no errors at this point, now we have complete gcc */
> 
> 5. Back to glibc
>    make
>    make install install_root=whatever
> /* no errors anymore */
> 
> That's all. Don't rely on the exact parameters to configure,
> I got them from memory.
> 
> Regards,
> -velco

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~1999-10-30  1:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-28 13:00 help, build Cross GCC Wang Yong
1999-10-28 13:21 ` Andreas Tobler
1999-10-28 16:25   ` Dan Malek
1999-10-29  3:21     ` Wang Yong
1999-10-29 13:03       ` Momchil Velikov
1999-10-30  1:48         ` Wang Yong [this message]
1999-10-28 15:15 ` Grant Erickson

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=381A4E7F.558A54C0@263.net \
    --to=wung_y@263.net \
    --cc=linuxce-devel@linuxce.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=velco@fadata.bg \
    /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 NNTP newsgroup(s).