public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: pfeifer@dbai.tuwien.ac dot@(Gerald Pfeifer)
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/2363: objdir with colon causes bootstrap failure
Date: Fri, 23 Mar 2001 09:36:00 -0000	[thread overview]
Message-ID: <200103231732.f2NHWJj74178@taygeta.dbai.tuwien.ac.at> (raw)

>Number:         2363
>Category:       libstdc++
>Synopsis:       objdir with colon causes bootstrap failure
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Mar 23 09:36:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        3.1 20010323 (experimental)
>Organization:
>Environment:
System: FreeBSD taygeta.dbai.tuwien.ac.at 4.2-RELEASE FreeBSD 4.2-RELEASE #2: Thu Dec 28 19:02:47 CET 2000 root@taygeta.dbai.tuwien.ac.at:/usr/src/sys/compile/GERALDKERNEL i386


	
host: i386-unknown-freebsd4.2
build: i386-unknown-freebsd4.2
target: i386-unknown-freebsd4.2
configured with: /sw/test/gcc/cvs/configure --prefix=/sw/test/gcc/FreeBSD --enable-languages=c,c++,objc,java : (reconfigured) 
>Description:
	If the name of objdir contains a colon, bootstrap nearly succeeds but
	at the end, during compilation of libstdc++, the following kind of
	boostrap failure is encountered:

	creating libstdc++.la
	(cd .libs && rm -f libstdc++.la && ln -s ../libstdc++.la libstdc++.la)
	gmake \
	top_builddir=`CDPATH=:. && cd .. && pwd` \
	top_srcdir=`CDPATH=:. && cd /sw/test/gcc/cvs-3.0/libstdc++-v3 && pwd` \
	tmp-libstdc++.INC
	gmake[5]: Entering directory `/files/pfeifer/O17:07/i386-unknown-freebsd4.2/libstdc++-v3/src'
	Makefile:283: *** multiple target patterns.  Stop.
	gmake[5]: Leaving directory `/files/pfeifer/O17:07/i386-unknown-freebsd4.2/libstdc++-v3/src'
	gmake[4]: *** [libstdc++.INC] Error 2
	gmake[4]: Leaving directory `/files/pfeifer/O17:07/i386-unknown-freebsd4.2/libstdc++-v3/src'

>How-To-Repeat:
	
>Fix:
	Do not use an objdir whose name contains a colon.
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2001-03-23  9:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200103231732.f2NHWJj74178@taygeta.dbai.tuwien.ac.at \
    --to=pfeifer@dbai.tuwien.ac \
    --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).