From: greyham@research.canon.com.au (Graham Stoney)
To: eclarke@aminocom.com (Elizabeth Clarke)
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: glibc-2.1.2 cross-compile problem
Date: Fri, 28 Apr 2000 10:42:54 +1000 (EST) [thread overview]
Message-ID: <20000428004254.2D5043C978@elph.research.canon.com.au> (raw)
In-Reply-To: <39084D22.417A2FC3@aminocom.com> from "Elizabeth Clarke" at Apr 27, 2000 02:22:26 PM
Hi Elizabeth,
Elizabeth Clarke writes:
> /usr/local/src/gcc-2.95.2/gcc/xgcc -B/usr/local/src/gcc-2.95.2/gcc/
> -B/usr/local/powerpc-linux/bin/ -c -g -O2 -I. -I. -D_IO_MTSAFE_IO
> iogetline.c -o pic/iogetline.o
> /usr/local/src/gcc-2.95.2/gcc/xgcc -B/usr/local/src/gcc-2.95.2/gcc/
> -B/usr/local/powerpc-linux/bin/ -c -g -O2 -I. -I. -D_IO_MTSAFE_IO
> iogetline.c
> In file included from iolibio.h:1,
> from libioP.h:47,
> from iogetline.c:26:
> libio.h:30: _G_config.h: No such file or directory
> make[1]: *** [iogetline.o] Error 1
> make[1]: Leaving directory
> `/usr/local/src/gcc-2.95.2/powerpc-linux/libio'
>
> So now I'm where Graham Stoney was at Date: Thu, 12 Aug 1999 14:34:44
> -0400.
Can't remember what I did to solve this, but I got past it somehow. Try
doing a "make install", and see if it installs enough of the compiler to go
ahead with the glibc build. I found I had to build gcc in two passes, firstly
with --with-newlib, and then without once glibc was installed.
> Surely its should not be as bad as this?
Agreed. Funnily enough though, it's better than it used to be. I remember when
I was a lad, before "configure" was around...
Good luck,
Graham
--
Graham Stoney
Principal Hardware/Software Engineer
Canon Information Systems Research Australia
Ph: +61 2 9805 2909 Fax: +61 2 9805 2929
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-04-28 0:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-20 16:43 glibc-2.1.2 cross-compile problem Elizabeth Clarke
2000-04-26 0:24 ` Graham Stoney
2000-04-26 14:37 ` Elizabeth Clarke
2000-04-26 16:58 ` David Edelsohn
2000-04-26 19:01 ` Matt Porter
2000-04-27 14:22 ` Elizabeth Clarke
2000-04-28 0:42 ` Graham Stoney [this message]
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=20000428004254.2D5043C978@elph.research.canon.com.au \
--to=greyham@research.canon.com.au \
--cc=eclarke@aminocom.com \
--cc=linuxppc-dev@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).