Cross Compile libpthread-stubs for Tiny210

Its been upwards of 13 years since Ive had to cross compile (and that was
in DOS).  I am using a SUSE linux system as my work system and need to
compile for arm-linux so I did:

'./configure --target=arm-linux'

which then runs through its setup and then I type:

'make' 

but all I get is:

make  all-am
make[1]: Entering directory `/home/db2inst1/tiny210/libpthread-stubs-0.3'
make[1]: Leaving directory `/home/db2inst1/tiny210/libpthread-stubs-0.3'

and no output libpthread-stubs.so 

Does someone have a link to a cross-compiling primer, an idiots guide or
similar on what I am missing?

Thanks!

Generally it's going to be a wee bit more than just --target=, I can't say
which because they're all different but it can end up being a mixture of
target/host/arch, include dirs, header dependencies, may even need a
CROSS_COMPILE export and the PATH env var having the path to your
cross-compiler too.

Do the following at the command prompt and it might give you extra clues as
to what's going on.
./configure --help

Ive got the CROSS_COMPILE setup to the compiler supplied by friendlyarm for
building the kernel so it knows which gcc to use (verified by watching the
output).  I think the problem is that the generated Makefile for libpthread
isnt setup to actually compile stubs.c for some reason.

you could always pastebin the output of the ./configure stage (or
config.log if there is one) might help, along with the output from
./configure --help :-)

http://www.linuxfromscratch.org/blfs/view/svn/x/libpthread-stubs.html

This suggests that your ./configure stage could be missing the --prefix
option.

config.log is posted at http://pastebin.com/E4Qc9VUT and I thought that the
--prefix was used for an installation location (same result with --prefix
set).

Problem averted..I finally found a build of this.

Of course now Im stuck with the realization that I somehow have to get the
X11 Server compiled and running.  Ubuntu is definitely looking better.

There are a couple of references to arm1176jzf-s (--with-cpu=arm1176jzf-s
--with-tune=arm1176jzf-s) which whilst it should stop it compiling, the 210
is actually a cortex-a8.

I'm not familiar with the libprthread/stubs code but essentially, I can't
see any references in there to finding any necessary headers that it might
need, it seems that everything would look in standard dirs, unless you're
using sys-root?

As for prefix, yes it can be used for installation but it can also be used
by the configure stage to use as a basis for arch-dependent files (headers,
shared libs). It's difficult to say exactly how true that statement is for
your situation, each package will use configure or whichever automated
system the maintainer of the package in their own way.