In-Reply-To: <4D3F2AE8.3010303@nvidia.com>
References: <4D3DF9FD.1050800@nvidia.com>
	<4D3EC8DC.602@RedHat.com>
	<4D3F2AE8.3010303@nvidia.com>
Date: Tue, 25 Jan 2011 15:32:46 -0500
Message-ID: <AANLkTi=tnLVwgYgPBgc=BrD5jAbqH7JfMhxOecc7K8cm@mail.gmail.com>
Subject: Re: Cross-compiling nfs-utils 1.1.4 for ARM
From: Kevin Coffman <kwc@citi.umich.edu>
To: Patrick Dignan <pdignan@nvidia.com>
Cc: Steve Dickson <SteveD@redhat.com>,
        "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Content-Type: text/plain; charset=ISO-8859-1
Sender: linux-nfs-owner@vger.kernel.org
MIME-Version: 1.0

On Tue, Jan 25, 2011 at 2:56 PM, Patrick Dignan <pdignan@nvidia.com> wrote:
> On 01/25/2011 04:58 AM, Steve Dickson wrote:
>>
>> On 01/24/2011 05:15 PM, Patrick Dignan wrote:
>>>
>>> Hi,
>>>
>>> I'm attempting to cross-compile nfs-utils 1.1.4 for ARM on an x86_64
>>> build machine. ?I can cross-compile other software, but nfs-utils fails. ?I
>>> get the following error:
>>>
>>> gcc -DHAVE_CONFIG_H -I. -I../../support/include ?-D_GNU_SOURCE
>>> -D_GNU_SOURCE ?-O2 -pipe -I/build/tegra2_seaboard/usr/include/
>>> -I/build/tegra2_seaboard/include/ -ggdb -march=armv7-a -mtune=cortex-a8
>>> -mfpu=vfpv3-d16 -mfloat-abi=softfp -MT testlk-testlk.o -MD -MP -MF
>>> .deps/testlk-testlk.Tpo -c -o testlk-testlk.o `test -f 'testlk.c' || echo
>>> './'`testlk.c
>>> cc1: error: unrecognized command line option "-mfpu=vfpv3-d16"
>>> cc1: error: unrecognized command line option "-mfloat-abi=softfp"
>>> testlk.c:1: error: bad value (armv7-a) for -march= switch
>>> testlk.c:1: error: bad value (cortex-a8) for -mtune= switch
>>>
>>> I'm guessing there's some sort of problem in Makefile.am that's causing
>>> it to fail, but I am not sure what changes I need to make. ?Does anyone know
>>> the solution to this problem or where I might start looking to fix this?
>>
>> My guess would be your cross-compiler is added those to the CFLAGS because
>> those flags are not set on a "normal" compilation...
>>
>> steved.
>>
>>> Best,
>>>
>>> Patrick Dignan
>
> I believe you are correct, however I think it should be using the ARM
> specific compiler when trying to cross-compile. ?I don't know enough about
> automake and cross-compiling to be sure, but I think that it doesn't set the
> CC variable correctly. ?It does seem to configure correctly though, since it
> shows the proper compiler being found: "checking for
> armv7a-cros-linux-gnueabi-gcc... (cached) armv7a-cros-linux-gnueabi-gcc",
> but then it uses the normal gcc.
>
> Thanks for the help!
>
> Best,
>
> Patrick Dignan

This is just a guess, but I'm suspicious of these lines in
tools/locktest/Makefile.am:

CC=$(CC_FOR_BUILD)
LIBTOOL = @LIBTOOL@ --tag=CC

This might have been an oversite when the original conversion to
automake was done.  What happens if you comment those lines out (and
then re-run autogen.sh)?  Note that Makefile.am for rpcgen and
rpcdebug also have these lines, but they may not need to be built when
cross-compiling?

K.C.