public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rkl@connect.org.uk
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/4096: libstdc++-v3/include/Makefile.in has several errors in it
Date: Thu, 23 Aug 2001 07:46:00 -0000	[thread overview]
Message-ID: <20010823144048.15496.qmail@sourceware.cygnus.com> (raw)

>Number:         4096
>Category:       libstdc++
>Synopsis:       libstdc++-v3/include/Makefile.in has several errors in it
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Aug 23 07:46:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     rkl@connect.org.uk
>Release:        3.0.1
>Organization:
>Environment:
HP-UX 11.00, but probably applies to most platforms
>Description:
The new Makefile.in added with 3.0.1, namely
libstdc++-v3/include/Makefile.in has several problems:

* The lengths of lines are excessive - HP-UX 11.00's vi
  can't edit them.

* The path for the rules involving gthr.h, gthr-single.h
  and gthr-default.h seem to be one level too low, causing
  the build to bomb out.

* Use of "-d" with the $(INSTALL) command isn't
  cross-platform (many install scripts don't support it) -
  see the install-data-local rule.

* "make install" installs the Makefile.in, Makefile and
  Makefile.am files into the install tree of gcc !!!!!
>How-To-Repeat:
You won't be able to build with "make" or "make install"
on HP-UX 11.00.
>Fix:
* Use "vim" to edit the Makefile.in instead of "vi" on
  HP-UX 11.00. Would be nice if no Makefile* files in
  gcc exceeded, say, 200 chars on any one line.

* Add a "../" to the middle of the path for the
  gthr*.h: rules - for example, the gthr.h rule now reads:

${thread_builddir}/gthr.h:
        sed -e '/^#/s/\(${uppercase}${uppercase}*\)/_GLIBCPP_\1/g' \
            -e 's,^#include "\(.*\)",#include <bits/\1>,g' \
            < ${glibcpp_srcdir}/../../gcc/gthr.h > $@

* In the install-data-local: rule, change:
            $(INSTALL) -d $${installFile} ;\
  to:
          mkdir -p $${installFile} ;\

* Add an ! -name directive to the find command in the
  install-data-local rule:

  for file in `find . ! -name stamp-\* ! -name Makefile\* -print`; do \
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-08-23  7:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-23  7:46 rkl [this message]
2001-08-23 14:56 Phil Edwards
2001-12-28 15:18 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=20010823144048.15496.qmail@sourceware.cygnus.com \
    --to=rkl@connect.org.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).