public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: gawrilow@math.tu-berlin.de
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/3457: enable-version-specific-runtime-libs vs. gxx-include-dir
Date: Thu, 28 Jun 2001 04:06:00 -0000 [thread overview]
Message-ID: <20010628110044.10622.qmail@sourceware.cygnus.com> (raw)
>Number: 3457
>Category: libstdc++
>Synopsis: enable-version-specific-runtime-libs vs. gxx-include-dir
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Jun 28 04:06:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Ewgenij Gawrilow
>Release: 3.0
>Organization:
>Environment:
UltraSPARC, Solaris 2.8
>Description:
configure --enable-version-specific-runtime-libs --gxx-include-dir=PATH
generates a Makefile where the value of --gxx-include-dir
is simply ignored. This causes make install
to put all C++ include files to the libsubdir/include, while
the prepocessor looks for them at the specified PATH.
This contradicts the INSTALL docs and the behavior of former
releases (such as 2.95.x)
>How-To-Repeat:
configure and install gcc with both options mentioned above
>Fix:
See attached patch.
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="p"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="p"
LS0tIGxpYnN0ZGMrKy12My9hY2luY2x1ZGUubTR+CVRodSBKdW4gMTQgMTA6NDc6MzUgMjAwMQor
KysgbGlic3RkYysrLXYzL2FjaW5jbHVkZS5tNAlUaHUgSnVuIDI4IDEyOjM5OjAyIDIwMDEKQEAg
LTE2MTUsNyArMTYxNSw5IEBACiBnY2NfdmVyc2lvbl90cmlnZ2VyPSR7c3JjZGlyfS8uLi9nY2Mv
dmVyc2lvbi5jCiBnY2NfdmVyc2lvbl9mdWxsPWBncmVwIHZlcnNpb25fc3RyaW5nICR7Z2NjX3Zl
cnNpb25fdHJpZ2dlcn0gfCBzZWQgLWUgJ3MvLipcIlwoW15cIl0qXClcIi4qL1wxLydgCiBnY2Nf
dmVyc2lvbj1gZWNobyAke2djY192ZXJzaW9uX2Z1bGx9IHwgc2VkIC1lICdzL1woW14gXSpcKSAu
Ki9cMS8nYAotZ3h4X2luY2x1ZGVfZGlyPSckKGxpYmRpcikvZ2NjLWxpYi8kKHRhcmdldF9hbGlh
cykvJyR7Z2NjX3ZlcnNpb259L2luY2x1ZGUvZysrCitpZiB0ZXN0IHgiJGd4eF9pbmNsdWRlX2Rp
ciIgPSB4Im5vIjsgdGhlbgorICBneHhfaW5jbHVkZV9kaXI9JyQobGliZGlyKS9nY2MtbGliLyQo
dGFyZ2V0X2FsaWFzKS8nJHtnY2NfdmVyc2lvbn0vaW5jbHVkZS9nKysKK2ZpCiBnbGliY3BwX3Rv
b2xleGVjZGlyPSckKGxpYmRpcikvZ2NjLWxpYi8kKHRhcmdldF9hbGlhcyknCiBnbGliY3BwX3Rv
b2xleGVjbGliZGlyPSckKHRvb2xleGVjZGlyKS8nJHtnY2NfdmVyc2lvbn0KIGNoYW5nZXF1b3Rl
KFssXSlkbmwK
next reply other threads:[~2001-06-28 4:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-28 4:06 gawrilow [this message]
2001-08-24 12:17 bkoz
2002-04-04 11:52 bkoz
2002-04-04 12:01 bkoz
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=20010628110044.10622.qmail@sourceware.cygnus.com \
--to=gawrilow@math.tu-berlin.de \
--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).