* problems with powerpc64-unknown-linux-gnu
@ 2002-04-12 19:02 Janis Johnson
2002-04-12 19:46 ` David Edelsohn
0 siblings, 1 reply; 4+ messages in thread
From: Janis Johnson @ 2002-04-12 19:02 UTC (permalink / raw)
To: gcc
I'm playing with changes to the support for -fprefetch-loop-arrays on
ia64 and want to see how they affect other architectures, so I obtained
access to a powerpc64-unknown-linux-gnu system. My first naive attempt
to build the 3.1-20020408 snapshot there failed. I started over, this
time specifying "--host=powerpc-unknown-linux-gnu" for configure, but
"make bootstrap" failed with an assertion error building libstdc++.
A current bootstrap of only C is making good progress, but I'd like to
be able to test with C++ and Fortran 77. Should I expect to be able to
build all default languages there? Are there configuration options I
need to use? I don't care whether I can have 64-bit binaries or not.
Janis
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: problems with powerpc64-unknown-linux-gnu
2002-04-12 19:02 problems with powerpc64-unknown-linux-gnu Janis Johnson
@ 2002-04-12 19:46 ` David Edelsohn
2002-04-13 2:06 ` Janis Johnson
0 siblings, 1 reply; 4+ messages in thread
From: David Edelsohn @ 2002-04-12 19:46 UTC (permalink / raw)
To: Janis Johnson; +Cc: gcc
I am not aware of problem building ppc64 GCC 3.1. The ppc64 Linux
development team uses it regularly. Do you have ppc64 binutils and ppc64
glibc installed on the test system?
David
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: problems with powerpc64-unknown-linux-gnu
2002-04-12 19:46 ` David Edelsohn
@ 2002-04-13 2:06 ` Janis Johnson
2002-04-13 3:01 ` Alan Modra
0 siblings, 1 reply; 4+ messages in thread
From: Janis Johnson @ 2002-04-13 2:06 UTC (permalink / raw)
To: David Edelsohn; +Cc: Janis Johnson, gcc
On Fri, Apr 12, 2002 at 10:08:18PM -0400, David Edelsohn wrote:
> I am not aware of problem building ppc64 GCC 3.1. The ppc64 Linux
> development team uses it regularly. Do you have ppc64 binutils and ppc64
> glibc installed on the test system?
I don't have access to the system right now, but it probably doesn't have
ppc64 tools. My first attempt failed with an assembler error so I built
new binutils which were apprently ppc64, and the second attempt failed
because xxx/xxx64/crti.o (can't remember the real name) wasn't found, so
that probably means there was no ppc64 glibc. Then I rebuilt the new
binutils with host=powerpc-unknown-linux-gnu. I'll find out Monday if
I can install ppc64 binutils and glibc. If not, should I be able to
build and use a 32-bit GCC 3.1 on such a system?
Sorry, I should look into this more myself before asking here.
Janis
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: problems with powerpc64-unknown-linux-gnu
2002-04-13 2:06 ` Janis Johnson
@ 2002-04-13 3:01 ` Alan Modra
0 siblings, 0 replies; 4+ messages in thread
From: Alan Modra @ 2002-04-13 3:01 UTC (permalink / raw)
To: Janis Johnson; +Cc: gcc
On Fri, Apr 12, 2002 at 10:53:55PM -0700, Janis Johnson wrote:
>
> I don't have access to the system right now, but it probably doesn't have
> ppc64 tools. My first attempt failed with an assembler error so I built
> new binutils which were apprently ppc64, and the second attempt failed
> because xxx/xxx64/crti.o (can't remember the real name) wasn't found, so
> that probably means there was no ppc64 glibc.
Yes, trying to build --enable-shared without glibc installed is doomed.
Starting off without any tools, the sequence is:
o Build and install binutils. Use --disable-shared. eg. configure
/src/binutils/configure --prefix=/usr/local \
--build=powerpc-linux --host=powerpc-linux --target=powerpc64-linux \
--disable-nls --disable-shared
o Build and install gcc. Use --disable-shared --enable-languages=c
and use exactly the same --prefix, --build, --host and --target as
you used for binutils. eg. configure
/src/gcc/configure --prefix=/usr/local \
--build=powerpc-linux --host=powerpc-linux --target=powerpc64-linux \
--disable-nls --disable-shared --enable-languages=c
o Build and install glibc. If you're building cross-tools, then use
--prefix=$prefix/$target, where $prefix and $target are the values
used for --prefix and --target respectively when compiling binutils.
For native targets, use the same --prefix as binutils. eg. configure
/src/glibc/configure --prefix=/usr/local/powerpc64-linux \
--build=powerpc-linux --host=powerpc64-linux --target=powerpc64-linux \
--with-headers=/src/linux-2.4.18-ppc/include --without-cvs \
--enable-add-ons --disable-profile --enable-shared \
--disable-sanity-checks
o Rebuild gcc with --enable-shared --enable-languages=<as_you_like>
You'll note in the above, I've treated powerpc64-linux as a cross-target
from powerpc-linux, even though they might be running on the same machine.
There are a few tool and glibc issues yet to be ironed out...
--
Alan Modra
IBM OzLabs - Linux Technology Centre
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2002-04-13 9:21 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-04-12 19:02 problems with powerpc64-unknown-linux-gnu Janis Johnson
2002-04-12 19:46 ` David Edelsohn
2002-04-13 2:06 ` Janis Johnson
2002-04-13 3:01 ` Alan Modra
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 read-only IMAP folder(s) and NNTP newsgroup(s).