>> ./gcc-4.3.3/configure --target=powerpc-linux --program-prefix=powerpc- >> >> I get this error: >> >> checking for C compiler default output file name... configure: error: >> C compiler cannot create executables > > Producing GCC binaries requires a working C toolchain (C compiler, C > library, assembler, linker,...) for the "host" system, in your case > for OS X 10.5! The GCC "sources" are mostly in 'C' language, so a > working C compiler for the host is required to compile them. In order > to make the executables for the "OS X to Linux/PPC" crosscompiler, > producing executables for OS X 10.5 MUST work ! > > The error tells that now you cannot produce any executables for OS X > 10.5 with the installed "Xcode" (what on earth is that?) ! Hi Kai, Xcode is the mac IDE, but if Xcode is there, then gcc also should be (and on my 10.5.6 intel system it is, and works, to produce binaries). Timur --- do you have multiple copies of Xcode? I think sometimes an earlier version lying around (from an earlier version of the os) can confuse things (although this may be a red herring). That has happened to me, but not on a build of gcc [which i haven't attempted on a mac in a long time]. I think Kai's keen observation about maybe straying into OS 9 land may be right on point, though [but i don't know how the darwin numbers correspond to the OS X numbers, so maybe darwin9 is what you expect, but it sounds funny]. dan > >> and config.log says this: >> >> configure:3194: checking for C compiler default output file name >> configure:3197: gcc conftest.c >&5 >> /usr/libexec/gcc/powerpc-apple-darwin9/4.0.1/ld: warning unknown >> -macosx_version_min parameter value: 10.5.6 ignored (using 10.1) > > This says "powerpc-apple-darwin9"... Is that really the same thing > as "a PowerPC OS X 10.5 system" ? Ie do you really have GCC etc > made for OS X 10.5 ? Not one made for OS X 9.x ? > > >
