Sorry if I wasn't precise enough.
1. My hardware is a G4 (i.e. 32bit ppc cpu, no 64bit support) running
Mac OS X 10.4.6, reinstalled in the last month from scratch, i.e.
blank hard disk, formatted HFSX+J.
2. I have Xcode 2.2 installed.
3. I am using a special user portage, group portage, to experiment
with portage-prefix. Homedir is /Volumes/portage, again HFSX+J.
4. I am using portage-alt-prefix-20060406.
5. I have no special environment, i.e. SHELL=/bin/bash, TERM=xterm-
color, PATH=/bin:/sbin:/usr/bin:/usr/sbin, DEFAULT_PATH etc. unset.
6. I try to bootstrap portage using the command
$ ./portage-alt-prefix/scripts/bootstrap-prefix.sh /Volumes/portage/
This script first fetches and compiles odcctools, then gcc-apple-5247.
7. In particular, this script does not pass --disable-multilib to gcc
8. The following make boostrap-lean fails as posted before. As I
suspected, I was not the only one experiencing this bug, even though
the reference in my last mail is to mainline-gnu-gcc.
9. The gcc-people don't seem to consider this a bug, I filed one with
apple, though, to see what they think.
10. In the meantime: What's the correct way to --disable-multilib,
i.e. a profile ppc32 and a profile ppc64, hardcoded in bootstrap or a
bootstrap commandline option --disable-multilibs? What are multilibs,
i.e. does this mean the compiler executable will take advantage of
64bit hardware even if compiled on 32bit hardware or just that the
compiler is able to generate fat binaries? Do we want multilibs in
portage or do we want to give the user a choice? It's Gentoo after
Am 07.04.2006 um 13:09 schrieb Grobian:
> I don't really understand. Unless you really want to build the
> GCC release you probably need to give configure that flag, but for
> Apple's GCC it should just work as far as I know.
> Did you use the bootstrap script? If so does this failure comes
> the bootstrap? Have you tried a recent (== a few days ago) version of
> the bootstrap script?
> On 07-04-2006 13:43:29 +0200, Tobias Hahn wrote:
>> I'm experiencing bug http://gcc.gnu.org/bugzilla/show_bug.cgi?
>> id=26628 (I can't
>> understand marking that bug invalid. It's definitely something
>> autoconf should
>> be able to detect. But support for machines that don't understand
>> tail -n seems
>> to be more of a priority to the gcc people...) since I'm still on
>> a G4. Where's
>> the correct point to --disable-multilib (profile, bootstrap-script?)
>> Adding multilib support to Makefile in ../../../gcc-5247/libstdc++-v3
>> Running configure in multilib subdirs ppc64
>> pwd: /tmp/gcc-apple/build/powerpc-apple-darwin8/libstdc++-v3
>> Running configure in multilib subdir ppc64
>> pwd: /tmp/gcc-apple/build/powerpc-apple-darwin8
>> configure: creating cache ./config.cache
>> checking build system type... powerpc-apple-darwin8
>> checking host system type... powerpc-apple-darwin8
>> checking target system type... powerpc-apple-darwin8
>> checking for a BSD-compatible install... /usr/bin/install -c
>> checking whether build environment is sane... yes
>> checking for gawk... no
>> checking for mawk... no
>> checking for nawk... no
>> checking for awk... awk
>> checking whether make sets $(MAKE)... yes
>> checking for powerpc-apple-darwin8-gcc... /tmp/gcc-apple/build/gcc/
>> -B/tmp/gcc-apple/build/gcc/ -B/tmp/gcc-apple/usr/powerpc-apple-
>> -B/tmp/gcc-apple/usr/powerpc-apple-darwin8/lib/ -isystem
>> /tmp/gcc-apple/usr/powerpc-apple-darwin8/include -isystem
>> /tmp/gcc-apple/usr/powerpc-apple-darwin8/sys-include -m64
>> checking for C compiler default output file name... a.out
>> checking whether the C compiler works... configure: error: cannot
>> run C
>> compiled programs.
>> If you meant to cross compile, use `--host'.
>> See `config.log' for more details.
>> make: *** [configure-target-libstdc++-v3] Error 1
>> make: *** Waiting for unfinished jobs....
>> firstname.lastname@example.org mailing list
> Fabian Groffen
> Gentoo for Mac OS X Project
> email@example.com mailing list
firstname.lastname@example.org mailing list