[kintaro]

Any one know what host type should be specified?

- - - - - - - - - - - proble output ... - - - - - - - - - - -

[localhost:temp/samba-2.0.7/source] kintaro% ./configure --target=TARGET
loading cache ./config.cache
checking for gcc... no
checking for cc... cc
checking whether the C compiler (cc -O ) works... yes
checking whether the C compiler (cc -O ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether cc accepts -g... yes
checking for a BSD compatible install... /usr/bin/install -c
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether cc understands -c and -o together... yes
checking that the C compiler understands volatile... yes
checking host system type... configure: error: can not guess host type; you must specify one
[localhost:temp/samba-2.0.7/source] kintaro%

- - - - - - - - - - - - - end of info - - - - - - - - - - - - - - -

[parallax]

Try copying /usr/libexec/config.* into the installation folder.

[fitter]

You can also specify the host type during ocnfiguration by adding this flag:

--host=chiptype-vendor-operatingsystem

In the case of OS X 10.0, the host info is as follows:

--host=powerpc-apple-darwin1.3

Unfortunately, this system type is not recognized by all packages. Others I've found to work properly are:

powerpc-apple-darwin
powerpc-apple-machten (most succesful if powerpc-apple-darwin1.3 fails)
powerpc-apple-rhapsody10.0

So, to compile the software, you would enter the following:

./configure --target=TARGET --host=powerpc-apple-darwin1.3

I notice, too, that you don't have a symbolic link directing calls to gcc to apple's cc. Enter this at the command line: ln -s /usr/bin/cc /usr/bin/gcc. (No period.) This will make any package searching for gcc (gnu c compiler) use cc; it'll save you a lot of headaches if you get into installing any considerable amount of unix software.

One other tip for compiling unix software.... Apple's cc has a bug in it that causes some problems during compile time. The workaround is to enter this at the command prompt before configuring and installing the software: setenv CFLAGS -traditional-cpp <hit enter> setenv CPPFLAGS -traditional-cpp <enter> Begin configuration.

This will prevent a number of compiling errors from occuring.