From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux-NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: mount.nfs in latest nfs-utils doesn't build
Date: Tue, 27 Oct 2009 15:41:37 -0400 [thread overview]
Message-ID: <4AE74CF1.8080003@RedHat.com> (raw)
In-Reply-To: <45A199A9-CC1A-4A9B-BA2B-382BA06FCD18@oracle.com>
On 10/26/2009 04:56 PM, Chuck Lever wrote:
> Commit 1d1f7016 added --enable-mountconfig, which defaults off, but
> building nfs-utils without it fails.
Sorry about that..... that patch is upcoming....
steved.
>
> Making all in mount
> libtool: link: gcc -Wall -Wstrict-prototypes -pipe -g -Wextra -fpie
> -D_FILE_OFFSET_BITS=64 -D _FORTIFY_SOURCE=2 -pie -o mount.nfs mount.o
> error.o network.o fstab.o token.o parse_opt.o parse_dev.o nfsmount.o
> nfs4mount.o stropts.o nfsumount.o ../../support/nfs/libnfs.a
> ../../support/export/libexport.a
> network.o: In function `nfs_probe_nfsport':
> /home/cel/src/nfs-utils/main/utils/mount/network.c:620: undefined
> reference to `config_default_proto'
> /home/cel/src/nfs-utils/main/utils/mount/network.c:620: undefined
> reference to `config_default_proto'
> stropts.o: In function `nfs_validate_options':
> /home/cel/src/nfs-utils/main/utils/mount/stropts.c:291: undefined
> reference to `config_default_vers'
> /home/cel/src/nfs-utils/main/utils/mount/stropts.c:292: undefined
> reference to `config_default_vers'
> /home/cel/src/nfs-utils/main/utils/mount/stropts.c:293: undefined
> reference to `config_default_vers'
> collect2: ld returned 1 exit status
> make[2]: *** [mount.nfs] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all-recursive] Error 1
> [cel@matisse nfs-utils]$
>
> --
> Chuck Lever
> chuck[dot]lever[at]oracle[dot]com
>
>
>
prev parent reply other threads:[~2009-10-27 19:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 20:56 mount.nfs in latest nfs-utils doesn't build Chuck Lever
2009-10-27 19:41 ` Steve Dickson [this message]
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=4AE74CF1.8080003@RedHat.com \
--to=steved@redhat.com \
--cc=chuck.lever@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox