All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Dignan <pdignan@nvidia.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: Cross-compiling nfs-utils 1.1.4 for ARM
Date: Tue, 25 Jan 2011 11:56:24 -0800	[thread overview]
Message-ID: <4D3F2AE8.3010303@nvidia.com> (raw)
In-Reply-To: <4D3EC8DC.602@RedHat.com>

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
>>
>> -----------------------------------------------------------------------------------
>> This email message is for the sole use of the intended recipient(s) and may contain
>> confidential information.  Any unauthorized review, use, disclosure or distribution
>> is prohibited.  If you are not the intended recipient, please contact the sender by
>> reply email and destroy all copies of the original message.
>> -----------------------------------------------------------------------------------
>> -- 
>> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
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


  reply	other threads:[~2011-01-25 19:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 22:15 Cross-compiling nfs-utils 1.1.4 for ARM Patrick Dignan
2011-01-25 12:58 ` Steve Dickson
2011-01-25 19:56   ` Patrick Dignan [this message]
2011-01-25 20:32     ` Kevin Coffman
2011-01-25 22:26       ` Patrick Dignan
2011-01-25 22:44         ` Chuck Lever
2011-01-26  1:49           ` Steve Dickson
2011-01-26 15:34             ` Chuck Lever

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D3F2AE8.3010303@nvidia.com \
    --to=pdignan@nvidia.com \
    --cc=SteveD@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.