[Bug build/18272] New: Build terminates with cannot remove /usr/include/limits.h

["david_denny at verizon dot net" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=18272

            Bug ID: 18272
           Summary: Build terminates with cannot remove
                    /usr/include/limits.h
           Product: glibc
           Version: 2.21
            Status: NEW
          Severity: normal
          Priority: P2
         Component: build
          Assignee: unassigned at sourceware dot org
          Reporter: david_denny at verizon dot net
                CC: carlos at redhat dot com

Created attachment 8250
  --> https://sourceware.org/bugzilla/attachment.cgi?id=8250&action=edit
Output during "make --debug=a -j1 2>&1 | tee log.file"

Beginning from clean source and following direction from "Linux From Scratch"
build terminates with:

/usr/bin/install -c -m 644 ../include/limits.h /usr/include/limits.h
/usr/bin/install: cannot remove '/usr/include/limits.h': Permission denied

The problem is highly reproducible.
1.) No specific distribution, but generally following / compatible with Linux
>From Scratch.
2.) Source is clean. 
3.) Platform is Dell PE 2900 with 8 3GHz Xeon procesors and lots of RAM
4.) GCC 2.9.1
5.) Make 4.1
6.) Kernel 3.19.0
7.) binutils-2.25
8.) gmp-6.0.0.a, mpfr-3.1.2, mpc-1.0.3
9.) All else pretty much up to date and known dependencies rebuilt and pass
their own tests.

These are the things I've tried:
1.) Running as non-root user.
2.) use -J1 on make
3.) Unset all relevant environment variables.
4.) Try to "touch" /usr/include/limits.h
5.) Turn on "make --debug=a" to generate tons of make file debugging - why does
it want to replace /usr/include/limits.h during non-root build?

The problem has persisted for me through several versions of GLIBC, at least
2.18 and 2.19 to the point where I developed a patch (hack) to continue.

I'm sure it is something, I acknowledge that, but how can I figure it out? 
Looks like some other people have had the same problem but "fix" it by fooling
around with the distro configurations till the problem goes away.

FWIW, glibc-2.21 builds perfectly on other machines of similar configuration
(i686 for example.)

I can upload anything you'd like, and I have uploaded a rather mammoth log
file.

-- 
You are receiving this mail because:
You are on the CC list for the bug.