public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/12179] [3.4/3.5 Regression] --enable-version-specific-runtime-libs put files in the wrong place
Date: Sun, 08 Feb 2004 01:37:00 -0000 [thread overview]
Message-ID: <20040208013756.7309.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030905080629.12179.peturr02@ru.is>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-02-08 01:37 -------
Subject: Bug 12179
CVSROOT: /cvs/gcc
Module name: gcc
Branch: gcc-3_4-branch
Changes by: geoffk@gcc.gnu.org 2004-02-08 01:37:46
Modified files:
. : ChangeLog ltmain.sh
gcc/testsuite : ChangeLog
gcc/testsuite/objc.dg: call-super-2.m
libf2c : ChangeLog Makefile.in aclocal.m4 configure
libstdc++-v3 : ChangeLog acinclude.m4 aclocal.m4 configure
Added files:
libstdc++-v3 : .cvsignore
Log message:
Merge various patches from mainline:
Index: ChangeLog
2004-02-04 Geoffrey Keating <geoffk@apple.com>
Partial merge from upstream:
* ltmain.in: When setting IFS to '~', be careful about user
arguments that contain '~'.
Index: gcc/testsuite/ChangeLog
2004-02-07 Geoffrey Keating <geoffk@geoffk.org>
Andrew Pinski <pinskia@physics.uc.edu>
* objc.dg/call-super-2.m: Include stddef.h for size_t.
Update line numbers for the including of stddef.h.
Index: libf2c/ChangeLog
Thu Feb 5 15:08:08 2004 Geoffrey Keating <geoffk@apple.com>
PR 12179
* aclocal.m4 (GLIBCPP_EXPORT_INSTALL_INFO): Use 'gcc', not 'gcc-lib'.
Add comment about poorly-named variables.
* Makefile.in (libsubdir): Use 'gcc', not 'gcc-lib'.
* configure: Regenerate.
Index: libstdc++-v3/ChangeLog
2004-02-05 Geoffrey Keating <geoffk@apple.com>
PR 12179
* .cvsignore: New.
* acinclude.m4 (GLIBCXX_EXPORT_INSTALL_INFO): Use 'gcc', not
'gcc-lib'. Add comment about poorly-named variables.
* aclocal.m4: Regenerate.
* configure: Regenerate.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.856.2.3&r2=1.856.2.4
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/ltmain.sh.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.22&r2=1.22.4.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.3389.2.59&r2=1.3389.2.60
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/objc.dg/call-super-2.m.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.2.18.1&r2=1.2.18.2
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libf2c/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.202.2.1&r2=1.202.2.2
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libf2c/Makefile.in.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.57&r2=1.57.14.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libf2c/aclocal.m4.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.7&r2=1.7.16.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libf2c/configure.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.42&r2=1.42.10.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libstdc++-v3/.cvsignore.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=NONE&r2=1.1.2.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libstdc++-v3/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.2224.2.25&r2=1.2224.2.26
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libstdc++-v3/acinclude.m4.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.280&r2=1.280.4.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libstdc++-v3/aclocal.m4.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.296&r2=1.296.4.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libstdc++-v3/configure.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.373.4.2&r2=1.373.4.3
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12179
prev parent reply other threads:[~2004-02-08 1:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 8:06 [Bug libstdc++/12179] New: Static link failure: cannot find -lstdc++ peturr02 at ru dot is
2003-09-05 8:09 ` [Bug libstdc++/12179] " peturr02 at ru dot is
2003-09-05 8:11 ` peturr02 at ru dot is
2003-09-05 14:50 ` [Bug libstdc++/12179] [3.4 Regression] Static link failure: cannot find -lstdc++ when --enable-version-specific-runtime-libs pinskia at gcc dot gnu dot org
2003-09-27 20:26 ` [Bug bootstrap/12179] [3.4 Regression] --enable-version-specific-runtime-libs put files in the wrong place pinskia at gcc dot gnu dot org
2003-10-18 7:25 ` pinskia at gcc dot gnu dot org
2003-11-10 8:03 ` pinskia at gcc dot gnu dot org
2003-11-10 13:36 ` v dot haisman at sh dot cvut dot cz
2003-11-10 16:42 ` pinskia at gcc dot gnu dot org
2004-01-10 23:20 ` neroden at gcc dot gnu dot org
2004-01-13 12:23 ` v dot haisman at sh dot cvut dot cz
2004-01-15 18:42 ` mrdizzy38 at hotmail dot com
2004-01-15 18:56 ` giovannibajo at libero dot it
2004-01-15 19:00 ` giovannibajo at libero dot it
2004-01-15 20:52 ` geoffk at gcc dot gnu dot org
2004-01-17 8:46 ` [Bug bootstrap/12179] [3.4/3.5 " dhazeghi at yahoo dot com
2004-01-17 10:30 ` v dot haisman at sh dot cvut dot cz
2004-01-17 11:53 ` v dot haisman at sh dot cvut dot cz
2004-01-21 18:08 ` dhazeghi at yahoo dot com
2004-01-21 18:12 ` pinskia at gcc dot gnu dot org
2004-02-04 22:33 ` pinskia at gcc dot gnu dot org
2004-02-05 23:20 ` cvs-commit at gcc dot gnu dot org
2004-02-05 23:20 ` geoffk at gcc dot gnu dot org
2004-02-08 1:37 ` cvs-commit at gcc dot gnu dot org [this message]
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=20040208013756.7309.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).