linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Sangmoon Kim" <dogoil@etinsys.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Cross compiling glibc-2.2.3
Date: Wed, 17 Apr 2002 10:10:13 +0900	[thread overview]
Message-ID: <004e01c1e5ac$a084adf0$1a11efcb@industrialDiv.hanasys.co.kr> (raw)


Hi, IGOR LURI

> Anybody has already crosscompiled glibc 2.2.3 for mpc8xx?
I crosscompiled glibc-2.2.5.

> I know that for glibc-2.1.2 there is a patch in denx page, but for glibc
> 2.2.3 is there any patch?

I referenced the patch in denx page, and fixed the crosscompile problem by following procedure.

1. Move the sysdeps/powerpc/fclrexcpt.c to sysdeps/powerpc/fpu/
mv sysdeps/powerpc/fclrexcpt.c sysdeps/powerpc/fpu/

2. Delete the sysdeps/powerpc/memset.S
rm sysdeps/powerpc/memset.S

3. Edit the sysdeps/powerpc/Makefile
#ifeq ($(subdir),gmon)
#libm-support += fenv_const fe_nomask
#endif

4. Compile
CC=${TARGET}-gcc AR=${TARGET}-ar RANLIB=${TARGET}-ranlib \
        CFLAGS="-msoft-float -D_SOFT_FLOAT -mcpu=860 -O2" \
        ../${GLIBC}/configure --host=$TARGET --prefix=${PREFIX} \
        --enable-add-ons=linuxthreads --with-headers=${PREFIX}/include \
        --without-fp

Good luck.
- Sangmoon Kim -


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

             reply	other threads:[~2002-04-17  1:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-17  1:10 Sangmoon Kim [this message]
     [not found] <3.0.3.32.20020417095725.006a2034@spudcentral.com>
2002-04-18  1:36 ` Cross compiling glibc-2.2.3 Sangmoon Kim
2002-04-18  1:48   ` Dr. Craig Hollabaugh
  -- strict thread matches above, loose matches on Subject: below --
2002-04-16 15:30 IGOR LURI

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='004e01c1e5ac$a084adf0$1a11efcb@industrialDiv.hanasys.co.kr' \
    --to=dogoil@etinsys.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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).