On Wed, Dec 09, 2009 at 04:19:08PM -0600, Bruce Dubbs wrote: > Robert Millan wrote: >> On Mon, Dec 07, 2009 at 07:21:28PM +0000, Colin Watson wrote: >>> On Mon, Dec 07, 2009 at 11:38:06AM -0600, Bruce Dubbs wrote: >>>> configure.ac:176: required file `./config.rpath' not found >>>> >>>> The can be fixed by `touch config.rpath` >>> configure does actually run this, so I'd recommend copying the file from >>> gettext or gnulib instead. >> >> config.{guess,sub} are automatically updated. Can't config.rpath be >> handled the same way? >> >> In any case, this warning is harmless AFAICT. > > Yes, it is harmless, but removing it is just more professional. I don't > have a problem with suppressing specific warnings if they have been > considered and found inappropriate. > > I'm pretty sure config.rpath only exists for ld. There is is only used > when linking an ELF executable with shared objects. Since GRUB doesn't > create any libraries, then it is not appropriate. An empty config.rpath > is not unreasonable in this case.
I wouldn't spend a lot of time with this. If you think it's better to remove the config.rpath warning, I don't mind. If you find an easy way to have autogen.sh update it, all the better. I'd just like to avoid the burden of perpetually updating this file by hand. -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel