cclient fails to build on Mac OS X 10.3.9 (Server)

[ovidiu@…]

I'm trying to build php5 with apache2, mysql5, imap, pear on MacOS X 10.3.9 Server. cclient provides IMAP functionality that I need for PHP5, but it fails to compile on 10.3.9.

root# port -v install cclient ---> Fetching cclient ---> Verifying checksum(s) for cclient ---> Checksumming imap-2006g.tar.Z ---> Extracting cclient ---> Extracting imap-2006g.tar.Z ---> Configuring cclient ---> Building cclient with target osx EXTRACFLAGS=-fno-common You are building for OLD versions of Mac OS X. This build is NOT suitable for modern versions of Mac OS X, such as Tiger, which use PAM-based authentication. If you want to build for modern Mac OS X, you should use make oxp instead. Do you want to continue this build? Type y or n please: make[1]: * [osxwarn] Error 1 make: * [osxok] Error 2 Error: Target com.apple.build returned: shell command " cd "/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_mail_cclient/work/imap-2006g" && make osx EXTRACFLAGS=-fno-common " returned error 2 Command output: You are building for OLD versions of Mac OS X. This build is NOT suitable for modern versions of Mac OS X, such as Tiger, which use PAM-based authentication. If you want to build for modern Mac OS X, you should use make oxp instead. Do you want to continue this build? Type y or n please: make[1]: * [osxwarn] Error 1 make: * [osxok] Error 2

Warning: the following items did not execute (for cclient): com.apple.activate com.apple.build com.apple.destroot com.apple.install Error: Status 1 encountered during processing.

Is there fix for this issue ? A new port for cclient based on imap2004 for OS X 10.3.9 if latest version cannot be built on OS X < 10.4 ?

[ryandesign (Ryan Carsten Schmidt)]

I don't think we need an imap2004 port. imap 2006 should build just fine on Panther.

The portfile makes "osx" on Panther, and "oxp" on Tiger, because Tiger includes PAM. Does Panther Server include PAM too? (Does /usr/include/pam/pam_appl.h exist?) If so, then the portfile should use "oxp" on Panther Server too.

Maybe the portfile should be changed so that it does not assume "osx" or "oxp" based on OS version, but rather on the capabilities of the OS. Take the logic from the Makefile itself, which just checks for the presence of that pam_appl.h header file to see which build is best. If pam_appl.h is present, use "oxp". If not, use "osx".

Or do we have a "platform" selector for Server versions of the OS vs. client versions that we could use?

[ovidiu@…]

Thank you! I thought OS X 10.3.9 has no PAM, but it had. I have changed to "oxp" for variant7 and it worked.

[pguyot (Paul Guyot)]

I am confused, and I do not have access to a 10.3.9 box. What should be done? Replace osx with oxp on line 42?

[ovidiu@…]

Yes, on line 42 I changed to "oxp"

platform darwin 7 {

build.target oxp EXTRACFLAGS=-fno-common

}

[ryandesign (Ryan Carsten Schmidt)]

Are we confident that this fix is correct for both Mac OS X 10.3 Server and Mac OS X 10.3 client? Or have you only tested this on Server?

[ovidiu@…]

Only 10.3.9 Server. I didn't had the chance to test on client.

[pguyot (Paul Guyot)]

Actually, the 10.3.9 SDK has pam headers, so we'll assume it's present on server and client versions of the OS. I've just committed the change.

[(none)]

Milestone Port Bugs deleted