PPC Mac Mini, Mac OS X 10.4.8, I'm following along in README.macosx
and I've done this:
export SDK=/Developer/SDKs/MacOSX10.4u.sdk
and I call
./Configure -Accflags="-nostdinc -b$SDK/user/include/gcc -B$SDK/usr/
lib/gcc -isystem$SDK/usr/include -F$SDK/System/Library/Frameworks" -
Aldflags="-W1,-syslibroot,$SDK"
as suggested. I take defaults until it checks the compiler. Here's
the what happens there:
--------------------------
Use which C compiler? [cc]
powerpc-apple-darwin8-gcc-4.0.1: '-b' must come at the start of the
command line
Uh-oh, the C compiler 'cc' doesn't seem to be working.
powerpc-apple-darwin8-gcc-4.0.1: '-b' must come at the start of the
command line
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.
--------------------------
The README indicates that the parameters are useful for making perl
aware of the SDK, as I understand it, so I'm going to try this
without parameters.
But I thought I'd go ahead and ask if anyone can confirm that these
parameters aren't necessary if I'm not making the parallel install
aware of the sdk, or if anyone can give me a hint about what I'm
doing. (I've never used such parameters when compiling perl in the
past, haven't done an install in a year or so.)
There is a possibility I erased part of the SDK when I was intending
to move an alias to XCode into the applications folder and forgot
that the actual bundle moves when users that can modify the
applications folder (admin users) drag and drop wtihout the option key.
Also, the notes in README.macosx seem to indicate that shared
libraries and threads are now functional. Anyone on the list here
using them with (parallel installs of) apache 2 and mod_perl?
Sherm Pendley - 28 Oct 2006 13:36 GMT
> PPC Mac Mini, Mac OS X 10.4.8, I'm following along in README.macosx
> and I've done this:
>
> export SDK=/Developer/SDKs/MacOSX10.4u.sdk
Well, first things first. You asked if you *really* need to use the SDK.
You need to use an SDK if you're cross-compiling, such as:
a. Making a Universal Binary build of Perl, either to distribute or
to use for building and distributing UB modules.
b. Building Perl to run on a OS version other than the one you're
building with.
> There is a possibility I erased part of the SDK
SDKs are separate sub-packages in the Xcode package, so you can re-
install them pretty easily, without installing the whole thing.
sherm--
Web Hosting by West Virginians, for West Virginians: http://wv-www.net
Cocoa programming in Perl: http://camelbones.sourceforge.net
Joel Rees - 28 Oct 2006 17:15 GMT
Hi, Sherm,
>> PPC Mac Mini, Mac OS X 10.4.8, I'm following along in
>> README.macosx and I've done this:
[quoted text clipped - 10 lines]
> b. Building Perl to run on a OS version other than the one you're
> building with.
Then since this copy of perl is for apache 2, I don't need it.
Thanks.
>> There is a possibility I erased part of the SDK
>
> SDKs are separate sub-packages in the Xcode package, so you can re-
> install them pretty easily, without installing the whole thing.
Yeah, I figured re-installing XCode should be sufficient, since the
only thing that I moved (and then tried to delete because I thought
it was an alias) was XCode.
Building perl without the SDK options worked.
But I'm still wondering whether I wanted the shared libraries and
threads. In fact, looking at perl -V on the system perl and comparing
it to the parallel perl, I'm thinking maybe I wanted that
multiplicity thing and I probably did want the large files option and
what is PERL_IMPLICIT_CONTEXT, and, oh, it looks like there are some
advisories I need to check.
Especially I'm thinking the shared libraries and threads are going to
be useful with mod_perl.
thanks more.
> sherm--
>
> Web Hosting by West Virginians, for West Virginians: http://wv-www.net
> Cocoa programming in Perl: http://camelbones.sourceforge.net
Kurtz Le Pirate - 28 Oct 2006 14:26 GMT
> PPC Mac Mini, Mac OS X 10.4.8, I'm following along in README.macosx
> and I've done this:
[quoted text clipped - 23 lines]
> I cannot continue any further, aborting.
> --------------------------
hello,
trying to compile perl 5.8.8 for panther, i get the same error !!

Signature
klp
Tommy Nordgren - 28 Oct 2006 15:08 GMT
> PPC Mac Mini, Mac OS X 10.4.8, I'm following along in README.macosx
> and I've done this:
[quoted text clipped - 14 lines]
> powerpc-apple-darwin8-gcc-4.0.1: '-b' must come at the start of the
> command line
This message is clearly indicative. You should try putting the -b
option first in -Accflags
-Accflags="-b$SDK/user/include/gcc -nostdinc -B$SDK/usr/lib/gcc -
isystem$SDK/usr/include -F$SDK/System/Library/Frameworks"
> Uh-oh, the C compiler 'cc' doesn't seem to be working.
> powerpc-apple-darwin8-gcc-4.0.1: '-b' must come at the start of the
[quoted text clipped - 26 lines]
> libraries and threads are now functional. Anyone on the list here
> using them with (parallel installs of) apache 2 and mod_perl?
-------------------------------------
This sig is dedicated to the advancement of Nuclear Power
Tommy Nordgren
tommy.nordgren@chello.se
Joel Rees - 28 Oct 2006 17:19 GMT
>> PPC Mac Mini, Mac OS X 10.4.8, I'm following along in
>> README.macosx and I've done this:
[quoted text clipped - 19 lines]
> -Accflags="-b$SDK/user/include/gcc -nostdinc -B$SDK/usr/lib/gcc -
> isystem$SDK/usr/include -F$SDK/System/Library/Frameworks"
I though about trying that, but cc --help says the -b option is for
the architecture. And I realized that maybe I didn't want to be doing
something I'd have to specify the architecture for.
Thanks.
>> Uh-oh, the C compiler 'cc' doesn't seem to be working.
>> powerpc-apple-darwin8-gcc-4.0.1: '-b' must come at the start of
[quoted text clipped - 6 lines]
>> I cannot continue any further, aborting.
>> --------------------------