The environment variables CC and CXX are set during the configure phase if use_configure is yes (the default)., configure.cxx, and configure.cpp are set.This means that, unless instructed otherwise, each Portfile will have access to a compiler for both of these languages. C and C++ are fully supported in the base. These commands do nothing more than set environment variables during the configure phase if use_configure is yes. However, some language have direct support in the MacPorts base. The port lapack-manpages builds documentation by calling doxygen.Ĭommonality among several ports can be gathered into a portgroup.įor example, there is a portgroup that facilitates building projects written in Rust. The lowest level of support is for a Portfile to call the appropriate build command. The flexibility of a Portfile allows MacPorts to support a wide variety of languages. I'll retry make when you guys let me know how to fix up libquadmath.The following most-commonly used Portfile commands will choose a set of appropriate compilers with the required capability for a given OS version:įor further details and more related options, please read on. Is there any way to force libquadmath to compile in 32-bit mode? (If that's impossible, is it skippable?) I'll try to attach the "config.log" file. I didn't reach the error I reported with MacPorts' build yet. It seems that it tried to build "libquadmath" thinking all PowerPC systems are 64-bit, while mine is 32-bit. If you meant to cross compile, use `-host'. configure: error: in `/Users/daryle/Documents/Projects/GCC/gcc-obj/powerpc-apple-darwin8.11.0/ppc64/libquadmath':Ĭonfigure: error: cannot run C compiled programs. a.outĬhecking whether the C compiler works. Users/daryle/Documents/Projects/GCC/gcc-obj/./gcc/xgcc -B/Users/daryle/Documents/Projects/GCC/gcc-obj/./gcc/ -B/usr/local/powerpc-apple-darwin8.11.0/bin/ -B/usr/local/powerpc-apple-darwin8.11.0/lib/ -isystem /usr/local/powerpc-apple-darwin8.11.0/include -isystem /usr/local/powerpc-apple-darwin8.11.0/sys-include -m64Ĭhecking for C compiler default output file name. GNUĬhecking for powerpc-apple-darwin8.11.0-gcc. noĬhecking for style of include used by make. yesĬhecking for -enable-version-specific-runtime-libs. Note that it used the system compiler, Apple's GCC 4.0.1, and not anything from MacPorts for the first compiler phase.) It didn't build all the way through here's the last few lines:Ĭhecking whether make sets $(MAKE). (I'm using GMP, MPFR, and MPC from MacPorts. gcc/configure -with-gmp=/opt/local -with-mpfr=/opt/local -with-mpc=/opt/local Svn co svn:///svn/gcc/tags/gcc_4_7_1_release gcc > (Should I try building GCC 4.7.1 straight from you guys, without going through (Should I try building GCC 4.7.1 straight from you guys, without going through MacPorts?) (But this is probably more of a MacPorts problem than a GCC one, so don't worry about it.) I'm totally screwed for now, except for the copy of GCC 4.6 I have lying around. It can print out the version information, but attempting to compile a program results in a link error with LibPPI. The last version, which should be GCC 4.7.0, is still installed. The worst part is that I can't even go back. For all I know, the MacPorts program may read the supported-architectures list and ban you from downloading it.) (I don't know how to kick-start the process on a PowerPC system that never had "gcc47" on it. Use "port log gcc47 > gcc47.log" to get the log so I can attach it here (This requires MacPorts' version of Apple-provided GCC 4.2 to beĤ. "sudo port upgrade gcc47 piler=apple-gcc-4.2" Comment out the ban so you can try it.)Ģ. (They "dealt" with the build problems on PowerPC by summarily executing Comment-out the "supported_archs i386 x86_64" line to: Use "sudo port edit -editor nano gcc47" to edit the Portfile for GCC-4.7ġa. Unlike some earlier GCC versions on MacPorts, like GCC 4.4 and 4.5, I don't think GCC 4.7 uses any patched files issues with LibFFI on earlier versions may have been integrated into the source, but now I'm not so sure.ġ. From a brief glance at the logs, something about a linking error with your included version of libFFI came up. I'm frustrated since GCC 4.7.0 built fine with some tweaks provided by the MacPorts team. I'm on a Tiger, PowerPC, and 32-bit system any of those puts me in near-abandoned status, so the fact I'm all 3 meant that their team abandoned me to fix the problem on my own, possibly with your help. GCC is one of the software packages offered by MacPorts. I'm using an August-2002 Apple eMac, with a PowerPC-G4 chip.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |