This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Regenerating INSTALL
- From: ricaljasan <ricaljasan at pacific dot net>
- To: libc-help at sourceware dot org
- Date: Mon, 2 May 2016 23:54:27 -0700
- Subject: Regenerating INSTALL
- Authentication-results: sourceware.org; auth=none
Getting to the final stages of preparing my patches, and I know INSTALL
needs to be regenerated and its patch included alongside install.texi,
but I am getting some unexpected diffs. From
https://sourceware.org/glibc/wiki/Regeneration I see that `make INSTALL'
is supposed to take place. However, I get a ton of hunks in the diff,
not just the few I expected. An example of a relevant hunk is:
-'--disable-mathvec'
- By default for x86_64, the GNU C Library is built with vector math
- library. Use this option to disable vector math library.
+`--disable-mathvec'
+ By default for x86_64, the GNU C Library is built with the vector
+ math library. Use this option to disable the vector math library.
It appears that many of the hunks are related to the '-vs-` generation,
but there are many more, related to things such as an apparent
difference in line-width. For example:
-setting up a chroot environment or preparing a binary distribution. The
-directory should be specified with an absolute file name. Installing
-with the 'prefix' and 'exec_prefix' GNU standard make variables set is
+setting up a chroot environment or preparing a binary distribution.
+The directory should be specified with an absolute file name. Installing
+with the `prefix' and `exec_prefix' GNU standard make variables set is
not supported.
How should I deal with this? Do I need to hand-pick the edits (`git add
-p'), or is it expected that I generate INSTALL before working on my
branch (maybe it is expected that I always `configure' first?) so I can
`make INSTALL' again afterwards to get only the relevant edits in the patch?
Thanks,
Rical