> -----Original Message----- > From: Mike Frysinger [mailto:vapier@xxxxxxxxxx] > Sent: Monday, June 08, 2009 7:24 AM > To: Chuck Lever > Cc: Jeff Layton; Muntz, Daniel; linux-nfs@xxxxxxxxxxxxxxx > Subject: Re: should we make --enable-tirpc the default in > current nfs-utils? > > On Monday 08 June 2009 10:16:07 Chuck Lever wrote: > > Frankly, I think dropping back automatically is not a good > idea. The > > torrent of messages that configure normally spits out means that > > messages about a missing libtirpc are going to be missed in most > > cases, and folks will think that because they specified > --enable-tirpc > > on the configure command line, that's the build they got. > > the automatic fallback is when no tirpc option is specified. > if --enable- tirpc is specified, then it should fail (and > that is what the proposed patch does). > -mike > When libnfsidmap, libgssglue, etc. are not present the build fails. The builder didn't specify any particular --enable-X flag, and the build doesn't just do something like fall back and build v3-only. Why would I want the build to nondeterministically (to the extent that one might not be aware of what libraries are installed) generate different code? -Dan -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
