This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Failure in a complete build of current gcc snapshot


Adding gcc-patches and libstdc++; this is
<http://gcc.gnu.org/ml/gcc/2009-07/msg00464.html>.

* Ralf Wildenhues wrote on Sun, Jul 26, 2009 at 09:46:34AM CEST:
> 
> The other bug (the one about libstdc++*) also seems within that rule,
> but I don't see it yet.

Never mind.  The rest is just followup failure.

OK to install this trivial patch if it passes the build I'm running
right now, as well as a normal and a DESTDIR install I'll be doing
afterwards?

AFAICS the python directory is new in trunk, so no stable releases
affected.

Thanks,
Ralf

libstdc++-v3/ChangeLog:
2009-07-26  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>

	* python/Makefile.am (install-data-local): Use DESTDIR
	correctly.

diff --git a/libstdc++-v3/python/Makefile.am b/libstdc++-v3/python/Makefile.am
index 50cc6d9..457e45b 100644
--- a/libstdc++-v3/python/Makefile.am
+++ b/libstdc++-v3/python/Makefile.am
@@ -44,7 +44,7 @@ install-data-local: gdb.py
 ## .la file, and any previous -gdb.py file.  This is inherently
 ## fragile, but there does not seem to be a better option, because
 ## libtool hides the real names from us.
-	@here=`pwd`; cd $(toolexeclibdir); \
+	@here=`pwd`; cd $(DESTDIR)$(toolexeclibdir); \
 	  for file in libstdc++*; do \
 	    case $$file in \
 	      *-gdb.py) ;; \


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]