[darwinbuild] Building perl-35
Trying to build a patched version of perl, using the perl-35 tree. It's dying at the c compiler stage with the following errors: Operating system name? [darwin] Operating system version? [8.3.0] Build Perl for SOCKS? [n] Use the PerlIO abstraction layer? [y] Build a threading Perl? [y] Use the newer interpreter-based ithreads? [y] Use which C compiler? [cc] cc: Invalid arch name : PPC Uh-oh, the C compiler 'cc' doesn't seem to be working. cc: Invalid arch name : PPC Uh-oh, the C compiler 'cc' doesn't seem to be working. You need to find a working C compiler. Either (purchase and) install the C compiler supplied by your OS vendor, or for a free C compiler try http://gcc.gnu.org/ I cannot continue any further, aborting. make[1]: *** [/private/var/tmp/perl/perl-35.obj/perl/configure-stamp] Error 1 make: *** [installperl] Error 2 Is there something special that one needs to set or do to get a working c compiler? Philip Philip Rinehart Academic Media & Technology Cluster Support Services 203-432-6573 cluster.support@yale.edu philip.rinehart@yale.edu
Hi Philip, I'm curious about the "cc: Invalid arch name : PPC", did you modify your plist at all (specifically, RC_ARCHS)? It would be very helpful if you could attach the full build log, then we could answer questions like the one above on our own. Thanks, Kevin On Dec 20, 2005, at 10:08 AM, Philip Rinehart wrote:
Trying to build a patched version of perl, using the perl-35 tree. It's dying at the c compiler stage with the following errors:
Operating system name? [darwin] Operating system version? [8.3.0] Build Perl for SOCKS? [n] Use the PerlIO abstraction layer? [y] Build a threading Perl? [y] Use the newer interpreter-based ithreads? [y] Use which C compiler? [cc] cc: Invalid arch name : PPC Uh-oh, the C compiler 'cc' doesn't seem to be working. cc: Invalid arch name : PPC Uh-oh, the C compiler 'cc' doesn't seem to be working. You need to find a working C compiler. Either (purchase and) install the C compiler supplied by your OS vendor, or for a free C compiler try http://gcc.gnu.org/ I cannot continue any further, aborting. make[1]: *** [/private/var/tmp/perl/perl-35.obj/perl/configure- stamp] Error 1 make: *** [installperl] Error 2
Is there something special that one needs to set or do to get a working c compiler?
Philip
Philip Rinehart Academic Media & Technology Cluster Support Services 203-432-6573 cluster.support@yale.edu philip.rinehart@yale.edu
Here you go, I had no luck building it as a universal binary, so I dropped back to using just PPC.  Philip On Dec 20, 2005, at 2:11 PM, Kevin Van Vechten wrote:
Hi Philip,
I'm curious about the "cc: Invalid arch name : PPC", did you modify your plist at all (specifically, RC_ARCHS)? It would be very helpful if you could attach the full build log, then we could answer questions like the one above on our own.
Thanks,
Kevin
On Dec 20, 2005, at 10:08 AM, Philip Rinehart wrote:
Trying to build a patched version of perl, using the perl-35 tree. It's dying at the c compiler stage with the following errors:
Operating system name? [darwin] Operating system version? [8.3.0] Build Perl for SOCKS? [n] Use the PerlIO abstraction layer? [y] Build a threading Perl? [y] Use the newer interpreter-based ithreads? [y] Use which C compiler? [cc] cc: Invalid arch name : PPC Uh-oh, the C compiler 'cc' doesn't seem to be working. cc: Invalid arch name : PPC Uh-oh, the C compiler 'cc' doesn't seem to be working. You need to find a working C compiler. Either (purchase and) install the C compiler supplied by your OS vendor, or for a free C compiler try http://gcc.gnu.org/ I cannot continue any further, aborting. make[1]: *** [/private/var/tmp/perl/perl-35.obj/perl/configure- stamp] Error 1 make: *** [installperl] Error 2
Is there something special that one needs to set or do to get a working c compiler?
Philip
Philip Rinehart Academic Media & Technology Cluster Support Services 203-432-6573 cluster.support@yale.edu philip.rinehart@yale.edu
Philip Rinehart Academic Media & Technology Cluster Support Services 203-432-6573 cluster.support@yale.edu philip.rinehart@yale.edu
Case-sensitivity might be an issue with the RC_ARCHS variable. Try RC_ARCHS="i386 ppc". I don't think perl will build 64-bit, but the arch for that would be ppc64. _Mark On Dec 20, 2005, at 11:14 AM, Philip Rinehart wrote:
Here you go, I had no luck building it as a universal binary, so I dropped back to using just PPC.
<perl-35.log~11>
Philip
On Dec 20, 2005, at 2:11 PM, Kevin Van Vechten wrote:
Hi Philip,
I'm curious about the "cc: Invalid arch name : PPC", did you modify your plist at all (specifically, RC_ARCHS)? It would be very helpful if you could attach the full build log, then we could answer questions like the one above on our own.
Thanks,
Kevin
On Dec 20, 2005, at 10:08 AM, Philip Rinehart wrote:
Trying to build a patched version of perl, using the perl-35 tree. It's dying at the c compiler stage with the following errors:
Operating system name? [darwin] Operating system version? [8.3.0] Build Perl for SOCKS? [n] Use the PerlIO abstraction layer? [y] Build a threading Perl? [y] Use the newer interpreter-based ithreads? [y] Use which C compiler? [cc] cc: Invalid arch name : PPC Uh-oh, the C compiler 'cc' doesn't seem to be working. cc: Invalid arch name : PPC Uh-oh, the C compiler 'cc' doesn't seem to be working. You need to find a working C compiler. Either (purchase and) install the C compiler supplied by your OS vendor, or for a free C compiler try http://gcc.gnu.org/ I cannot continue any further, aborting. make[1]: *** [/private/var/tmp/perl/perl-35.obj/perl/configure- stamp] Error 1 make: *** [installperl] Error 2
Is there something special that one needs to set or do to get a working c compiler?
Philip
Philip Rinehart Academic Media & Technology Cluster Support Services 203-432-6573 cluster.support@yale.edu philip.rinehart@yale.edu
Philip Rinehart Academic Media & Technology Cluster Support Services 203-432-6573 cluster.support@yale.edu philip.rinehart@yale.edu
_______________________________________________ darwinbuild mailing list darwinbuild@opendarwin.org http://www.opendarwin.org/mailman/listinfo/darwinbuild
Well, crap that did it. Is there any particular reason darwinbuild is case-sensitive? because of multiple architectures? Philip On Dec 20, 2005, at 2:27 PM, Mark Pauley wrote:
Case-sensitivity might be an issue with the RC_ARCHS variable.
Try RC_ARCHS="i386 ppc". I don't think perl will build 64-bit, but the arch for that would be ppc64.
_Mark
On Dec 20, 2005, at 11:14 AM, Philip Rinehart wrote:
Here you go, I had no luck building it as a universal binary, so I dropped back to using just PPC.
<perl-35.log~11>
Philip
On Dec 20, 2005, at 2:11 PM, Kevin Van Vechten wrote:
Hi Philip,
I'm curious about the "cc: Invalid arch name : PPC", did you modify your plist at all (specifically, RC_ARCHS)? It would be very helpful if you could attach the full build log, then we could answer questions like the one above on our own.
Thanks,
Kevin
On Dec 20, 2005, at 10:08 AM, Philip Rinehart wrote:
Trying to build a patched version of perl, using the perl-35 tree. It's dying at the c compiler stage with the following errors:
Operating system name? [darwin] Operating system version? [8.3.0] Build Perl for SOCKS? [n] Use the PerlIO abstraction layer? [y] Build a threading Perl? [y] Use the newer interpreter-based ithreads? [y] Use which C compiler? [cc] cc: Invalid arch name : PPC Uh-oh, the C compiler 'cc' doesn't seem to be working. cc: Invalid arch name : PPC Uh-oh, the C compiler 'cc' doesn't seem to be working. You need to find a working C compiler. Either (purchase and) install the C compiler supplied by your OS vendor, or for a free C compiler try http://gcc.gnu.org/ I cannot continue any further, aborting. make[1]: *** [/private/var/tmp/perl/perl-35.obj/perl/configure- stamp] Error 1 make: *** [installperl] Error 2
Is there something special that one needs to set or do to get a working c compiler?
Philip
Philip Rinehart Academic Media & Technology Cluster Support Services 203-432-6573 cluster.support@yale.edu philip.rinehart@yale.edu
Philip Rinehart Academic Media & Technology Cluster Support Services 203-432-6573 cluster.support@yale.edu philip.rinehart@yale.edu
_______________________________________________ darwinbuild mailing list darwinbuild@opendarwin.org http://www.opendarwin.org/mailman/listinfo/darwinbuild
Philip Rinehart Academic Media & Technology Cluster Support Services 203-432-6573 cluster.support@yale.edu philip.rinehart@yale.edu
Cool, then the fix should be easy. RC_ARCHS values should be lower case, so "ppc" would get further. If you can attach the log corresponding to the original problem (when trying to build universal), I can help diagnose the initial issue as well... (which you might run into again after correcting RC_ARCHS). - Kevin On Dec 20, 2005, at 11:14 AM, Philip Rinehart wrote:
Here you go, I had no luck building it as a universal binary, so I dropped back to using just PPC.
<perl-35.log~11>
Philip
On Dec 20, 2005, at 2:11 PM, Kevin Van Vechten wrote:
Hi Philip,
I'm curious about the "cc: Invalid arch name : PPC", did you modify your plist at all (specifically, RC_ARCHS)? It would be very helpful if you could attach the full build log, then we could answer questions like the one above on our own.
Thanks,
Kevin
On Dec 20, 2005, at 10:08 AM, Philip Rinehart wrote:
Trying to build a patched version of perl, using the perl-35 tree. It's dying at the c compiler stage with the following errors:
Operating system name? [darwin] Operating system version? [8.3.0] Build Perl for SOCKS? [n] Use the PerlIO abstraction layer? [y] Build a threading Perl? [y] Use the newer interpreter-based ithreads? [y] Use which C compiler? [cc] cc: Invalid arch name : PPC Uh-oh, the C compiler 'cc' doesn't seem to be working. cc: Invalid arch name : PPC Uh-oh, the C compiler 'cc' doesn't seem to be working. You need to find a working C compiler. Either (purchase and) install the C compiler supplied by your OS vendor, or for a free C compiler try http://gcc.gnu.org/ I cannot continue any further, aborting. make[1]: *** [/private/var/tmp/perl/perl-35.obj/perl/configure- stamp] Error 1 make: *** [installperl] Error 2
Is there something special that one needs to set or do to get a working c compiler?
Philip
Philip Rinehart Academic Media & Technology Cluster Support Services 203-432-6573 cluster.support@yale.edu philip.rinehart@yale.edu
Philip Rinehart Academic Media & Technology Cluster Support Services 203-432-6573 cluster.support@yale.edu philip.rinehart@yale.edu
 It appears to be dying in the machine type defs. Philip On Dec 20, 2005, at 2:37 PM, Kevin Van Vechten wrote:
Cool, then the fix should be easy. RC_ARCHS values should be lower case, so "ppc" would get further.
If you can attach the log corresponding to the original problem (when trying to build universal), I can help diagnose the initial issue as well... (which you might run into again after correcting RC_ARCHS).
- Kevin
On Dec 20, 2005, at 11:14 AM, Philip Rinehart wrote:
Here you go, I had no luck building it as a universal binary, so I dropped back to using just PPC.
<perl-35.log~11>
Philip
On Dec 20, 2005, at 2:11 PM, Kevin Van Vechten wrote:
Hi Philip,
I'm curious about the "cc: Invalid arch name : PPC", did you modify your plist at all (specifically, RC_ARCHS)? It would be very helpful if you could attach the full build log, then we could answer questions like the one above on our own.
Thanks,
Kevin
On Dec 20, 2005, at 10:08 AM, Philip Rinehart wrote:
Trying to build a patched version of perl, using the perl-35 tree. It's dying at the c compiler stage with the following errors:
Operating system name? [darwin] Operating system version? [8.3.0] Build Perl for SOCKS? [n] Use the PerlIO abstraction layer? [y] Build a threading Perl? [y] Use the newer interpreter-based ithreads? [y] Use which C compiler? [cc] cc: Invalid arch name : PPC Uh-oh, the C compiler 'cc' doesn't seem to be working. cc: Invalid arch name : PPC Uh-oh, the C compiler 'cc' doesn't seem to be working. You need to find a working C compiler. Either (purchase and) install the C compiler supplied by your OS vendor, or for a free C compiler try http://gcc.gnu.org/ I cannot continue any further, aborting. make[1]: *** [/private/var/tmp/perl/perl-35.obj/perl/configure- stamp] Error 1 make: *** [installperl] Error 2
Is there something special that one needs to set or do to get a working c compiler?
Philip
Philip Rinehart Academic Media & Technology Cluster Support Services 203-432-6573 cluster.support@yale.edu philip.rinehart@yale.edu
Philip Rinehart Academic Media & Technology Cluster Support Services 203-432-6573 cluster.support@yale.edu philip.rinehart@yale.edu
Philip Rinehart Academic Media & Technology Cluster Support Services 203-432-6573 cluster.support@yale.edu philip.rinehart@yale.edu
Interesting, so the error appears to be: /usr/include/machine/_types.h:28:25: i386/_types.h: No such file or directory But /usr/include/i386/_types.h should be defined by xnu, which is in your list of installed roots. However, I'm noticing the xnu root checksum in your build log (cfff9c6ca1a8d8e0dee68ddea386e844c2e817a5) differs from the one in the 8F46 roots on opendarwin.org (c651cd7d2d8d102b4e297effb5fa951989fc2ba1), so I'm guessing you built xnu locally, with RC_ARCHS="ppc", and it therefore doesn't have the i386 headers? - Kevin On Dec 20, 2005, at 11:41 AM, Philip Rinehart wrote:
<perl-35.log~1>
It appears to be dying in the machine type defs.
Philip
ah, so that's interesting, if you build xnu as ppc, you then need to build all further projects as ppc only? Philip On Dec 20, 2005, at 3:52 PM, Kevin Van Vechten wrote:
Interesting, so the error appears to be:
/usr/include/machine/_types.h:28:25: i386/_types.h: No such file or directory
But /usr/include/i386/_types.h should be defined by xnu, which is in your list of installed roots.
However, I'm noticing the xnu root checksum in your build log (cfff9c6ca1a8d8e0dee68ddea386e844c2e817a5) differs from the one in the 8F46 roots on opendarwin.org (c651cd7d2d8d102b4e297effb5fa951989fc2ba1), so I'm guessing you built xnu locally, with RC_ARCHS="ppc", and it therefore doesn't have the i386 headers?
- Kevin
On Dec 20, 2005, at 11:41 AM, Philip Rinehart wrote:
<perl-35.log~1>
It appears to be dying in the machine type defs.
Philip
Philip Rinehart Academic Media & Technology Cluster Support Services 203-432-6573 cluster.support@yale.edu philip.rinehart@yale.edu
On Dec 20, 2005, at 1:03 PM, Philip Rinehart wrote:
ah, so that's interesting, if you build xnu as ppc, you then need to build all further projects as ppc only?
Correct. I realize we're lacking documentation in this area, so I'm really glad you're asking these questions. Hopefully I can put together some more complete documentation soon. Here's the overall flow of darwinbuild: 1. you invoke darwinbuild perl 2. darwinbuild asks darwinxref for the list of build-time dependencies needed for perl 3. darwinbuild looks for the roots for each of these dependencies a. in the local Roots directory b. at each of the binary_sites URLs in the plist 4. dependencies are copied into the BuildRoot 5. the build is started The reason for 3.a. is to allow you to make changes to projects and use those in your subsequent builds. For example, if you were to build a modified Libc, then a Libsystem, you probably want the Libsystem to pick up your Libc modifications. If you build a root ppc-only, then it's not going to have the necessary i386 parts that another project might depend on. In the case of xnu, it doesn't produce the necessary i386 header files. In the case of a dynamic library, it won't have the i386 symbols that another project needs to link against. Hope that helps shed some light on what's going on. - Kevin
If a requires b and b only has ppc bits, then you can only build the ppc bits for a, the linker likes to keep architectures separate. I think this is actually one of the main features Mach-o format. The other question you asked is why the values for RC_ARCHS need to be lower case. I'm thinking this has to do with the fact that all of the tools want the values to be lowercase (man lipo for details). I have no idea how this came about. _Mark On Dec 20, 2005, at 1:03 PM, Philip Rinehart wrote:
ah, so that's interesting, if you build xnu as ppc, you then need to build all further projects as ppc only?
Philip
On Dec 20, 2005, at 3:52 PM, Kevin Van Vechten wrote:
Interesting, so the error appears to be:
/usr/include/machine/_types.h:28:25: i386/_types.h: No such file or directory
But /usr/include/i386/_types.h should be defined by xnu, which is in your list of installed roots.
However, I'm noticing the xnu root checksum in your build log (cfff9c6ca1a8d8e0dee68ddea386e844c2e817a5) differs from the one in the 8F46 roots on opendarwin.org (c651cd7d2d8d102b4e297effb5fa951989fc2ba1), so I'm guessing you built xnu locally, with RC_ARCHS="ppc", and it therefore doesn't have the i386 headers?
- Kevin
On Dec 20, 2005, at 11:41 AM, Philip Rinehart wrote:
<perl-35.log~1>
It appears to be dying in the machine type defs.
Philip
Philip Rinehart Academic Media & Technology Cluster Support Services 203-432-6573 cluster.support@yale.edu philip.rinehart@yale.edu
_______________________________________________ darwinbuild mailing list darwinbuild@opendarwin.org http://www.opendarwin.org/mailman/listinfo/darwinbuild
participants (3)
-
Kevin Van Vechten
-
Mark Pauley
-
Philip Rinehart