All of lore.kernel.org
 help / color / mirror / Atom feed
From: david@mind.be
To: BREUVART Jean-Charles <jean-charles.breuvart@airbus.com>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: pb compiling cross gcc, binutils, glibc and so on ...
Date: Thu, 19 Dec 2002 16:31:22 +0100	[thread overview]
Message-ID: <20021219163121.T810@mind.be> (raw)
In-Reply-To: <36EB27C27D93D4119DE500508BDF85B30B2D710A@TOCOMEXC03>; from jean-charles.breuvart@airbus.com on Thu, Dec 19, 2002 at 03:52:06PM +0100


Hello,

> RedHat 8.0 comes with gcc 3.2, binutils 2.13.90.0.2, make 3.79.1, I don't
> know how to get the libc version ...

You can get the libc version by directly executing /lib/libc.so.6

> Here is the trouble :
>
> choose-temp.c:29: stdio.h: Aucun fichier ou r?pertoire de ce type
> choose-temp.c:30: sys/types.h: Aucun fichier ou r?pertoire de ce type
> choose-temp.c:32: unistd.h: Aucun fichier ou r?pertoire de ce type
> choose-temp.c:35: stdlib.h: Aucun fichier ou r?pertoire de ce type
> choose-temp.c:38: sys/file.h: Aucun fichier ou r?pertoire de ce type

These errors tell you it can't find the header files for your specific target
platform.
You can either copy these from an existing PPC system, or build glibc from
scratch for your system.
A good guide for creating glibc from scratch is to be found at:

http://penguinppc.org/embedded/cross-compiling/

I hope this helps.

Best regards,
David Mazur
--
Mind: Embedded Linux, eCos and JVM development in Europe
http://mind.be                        tel +32-16-309.666

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

  reply	other threads:[~2002-12-19 15:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19 14:52 pb compiling cross gcc, binutils, glibc and so on BREUVART Jean-Charles
2002-12-19 15:31 ` david [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-19 15:14 Claus Gindhart
2002-12-20  1:57 Liu Fred-a18596
2002-12-20 14:12 James Don

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=20021219163121.T810@mind.be \
    --to=david@mind.be \
    --cc=jean-charles.breuvart@airbus.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.