linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: oliver.amft@ch.abb.com
To: Mark Hatle <fray@mvista.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: GLibC cross compile for ppc-linux
Date: Tue, 25 Jul 2000 11:23:14 +0200	[thread overview]
Message-ID: <41256927.0038C99E.00@mail1.ch.abb.com> (raw)


Hi Mark, hi all,

sorry for the delay!
In between i've managed to get arround this: "isomac" checks the header files
and can't find an #include <{asm,linux}/errno.h> within the errno.h it is
checking. So, two links to the linux include dir (asm,linux) will help, since
the configure switch "--with-headers=$linux-dir/include" doesn't work at this
point.

Oliver




|---------->
|          |
|          |
|---------->
  >------------------------------------------------------------------------|
  |Mark Hatle <fray@mvista.com>                                            |
  |2000-07-17 19:00                                                        |
  >------------------------------------------------------------------------|



I've been cross-compiling glibc-2.1.3 for ppc 7xx and 8xx for a while
now.  I've yet to see any problems like that.  What if your host OS,
(i.e. RedHat, debian etc? and it's version.)  And what are you
targeting?

--Mark

oliver.amft@ch.abb.com wrote:
>
> Hi all,
>
> i'm trying to build the glibc 2.1.3 on a i686-linux machine for a
powerpc-linux
> embedded target. The make command works fine (...no errors) but somehow "make
> check" stops in the "stdlib tests" part when it is invoking the "isomac"
command
> for the first time (after compiling it):
>


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

             reply	other threads:[~2000-07-25  9:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-25  9:23 oliver.amft [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-07-17  8:39 GLibC cross compile for ppc-linux oliver.amft
2000-07-17 17:00 ` Mark Hatle

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=41256927.0038C99E.00@mail1.ch.abb.com \
    --to=oliver.amft@ch.abb.com \
    --cc=fray@mvista.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).