public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Phil Richards <pgr@derived-software.demon.co.uk>
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/4071: "make install" installs .../include/g++-v3/Makefile
Date: Tue, 21 Aug 2001 10:16:00 -0000	[thread overview]
Message-ID: <200108211100.f7LB0sX04775@derisoft.derived-software.demon.co.uk> (raw)

>Number:         4071
>Category:       libstdc++
>Synopsis:       "make install" installs .../include/g++-v3/Makefile
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Aug 21 10:16:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Phil Richards
>Release:        3.0.1
>Organization:
Derived Software Limited
>Environment:
System: Linux derisoft.derived-software.demon.co.uk 2.4.5-5mdk #1 Sat Jun 16 08:08:07 EDT 2001 i686 unknown
Architecture: i686

host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-3.0.1/configure --prefix=/usr/local --enable-threads
>Description:

[I couldn't work out which category/class problems like this should go
under ... there doesn't appear to be an "install" class.]

Did "make bootstrap" as "normal user", and "make install" as root.
I keep a list of all files installed (for later clean-up), and when
cross-checking what needed keeping between gcc 3.0 and gcc 3.0.1
noticed that
    /usr/local/include/g++-v3/Makefile
existed in 3.0.1 and not 3.0.

A quick check showed that this was a copy of
    <builddir>/i686-pc-linux-gnu/libstdc++-v3/include/Makefile

The install-data-local: rule from that Makefile installs all
files in the directory (except stamp-*) into .../include/g++-v3;
this, of course, includes "Makefile".

>How-To-Repeat:

make bootstrap
make install

(not double checked, but that's what I did to cause it!)

>Fix:
gcc-3.0.1/libstdc++-v3/include/Makefile.am:420 needs to exclude Makefile.

Quick (tested on GNU find) hack:

diff -Nc3pad gcc-3.0.1/libstdc++-v3/include/Makefile.am gcc-3.0.1-pgr/libstdc++-v3/include/Makefile.am
*** gcc-3.0.1/libstdc++-v3/include/Makefile.am	Fri Aug 17 22:03:40 2001
--- gcc-3.0.1-pgr/libstdc++-v3/include/Makefile.am	Tue Aug 21 11:50:41 2001*************** ${thread_builddir}/gthr-default.h:
*** 417,423 ****
  gxx_include_dir = @gxx_include_dir@
  
  install-data-local:
! 	for file in `find . ! -name stamp-\* -print`; do \
  	installFile=${gxx_include_dir}/$${file} ;\
  	if [ -d $${file} ]; then \
  	  $(INSTALL) -d $${installFile} ;\
--- 417,423 ----
  gxx_include_dir = @gxx_include_dir@
  
  install-data-local:
! 	for file in `find . ! -name stamp-\* ! -name Makefile -print`; do \
  	installFile=${gxx_include_dir}/$${file} ;\
  	if [ -d $${file} ]; then \
  	  $(INSTALL) -d $${installFile} ;\
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-08-21 10:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-21 10:16 Phil Richards [this message]
2001-08-21 18:06 Phil Edwards
2001-08-22 15:56 Phil Edwards
2001-08-24 17:15 bkoz
2001-10-10 13:40 pme

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=200108211100.f7LB0sX04775@derisoft.derived-software.demon.co.uk \
    --to=pgr@derived-software.demon.co.uk \
    --cc=gcc-gnats@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).