Patch for libg++-2.3 makefiles

Thread View: gnu.g++.lib.bug

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Jason Merrill Sat, 12 Dec 1992 02:56

#372

Author: Jason Merrill
Date: Sat, 12 Dec 1992 02:56

93 lines
3392 bytes

The first two patches make the C and C++ compilers for the target default
to the same as those for the host, rather than to $(CC) and gcc.

The next patch allows libg++ to be built in parallel (with the -j option to
GNU make); previously the dependencies were not indicated, so it would try
to compile stuff in src while it was creating _G_config.h, which didn't
work.

The final patch makes the C++ compiler used for test-install the same as
the one used for the build.

*** Makefile.in.orig	Thu Dec  3 21:56:05 1992
--- Makefile.in	Fri Dec 11 21:50:35 1992
***************
*** 89,95 ****
      echo $${rootme}/gcc/gcc -B$${rootme}/gcc/; \
    else \
      if [ "$(host_canonical)" = "$(target_canonical)" ] ; then \
!       echo $(CC); \
      else \
        t='$(program_transform_name)'; echo gcc | sed -e '' $$t; \
      fi; \
--- 89,95 ----
      echo $${rootme}/gcc/gcc -B$${rootme}/gcc/; \
    else \
      if [ "$(host_canonical)" = "$(target_canonical)" ] ; then \
!       echo $(CC_FOR_BUILD); \
      else \
        t='$(program_transform_name)'; echo gcc | sed -e '' $$t; \
      fi; \
***************
*** 100,106 ****
      echo $${rootme}/gcc/gcc -B$${rootme}/gcc/; \
    else \
      if [ "$(host_cpu)-$(host_vendor)-$(host_os)" = "$(target_cpu)-$(target_vendor)-$(target_os)" ] ; then \
!       echo gcc; \
      else \
        t='$(program_transform_name)'; echo gcc | sed -e '' $$t; \
      fi; \
--- 100,106 ----
      echo $${rootme}/gcc/gcc -B$${rootme}/gcc/; \
    else \
      if [ "$(host_cpu)-$(host_vendor)-$(host_os)" = "$(target_cpu)-$(target_vendor)-$(target_os)" ] ; then \
!       echo $(CXX_FOR_BUILD); \
      else \
        t='$(program_transform_name)'; echo gcc | sed -e '' $$t; \
      fi; \
*** libg++/Makefile.in.orig	Wed Dec  9 17:38:32 1992
--- libg++/Makefile.in	Fri Dec 11 21:50:36 1992
***************
*** 192,202 ****
  	$(RANLIB) $(TARGETLIB)
  	@touch stamp-$(TARGETLIB)
  
! in-src:
  	@rootme=`pwd`/ ; export rootme ; cd src ; \
  		$(MAKE) $(FLAGS_TO_PASS)
  
! in-io:
  	@rootme=`pwd`/ ; export rootme ; cd $(IO_DIR) ; \
  		$(MAKE) $(FLAGS_TO_PASS) stamp
  
--- 192,204 ----
  	$(RANLIB) $(TARGETLIB)
  	@touch stamp-$(TARGETLIB)
  
! src/stamp: in-src ;
! in-src: _G_config.h
  	@rootme=`pwd`/ ; export rootme ; cd src ; \
  		$(MAKE) $(FLAGS_TO_PASS)
  
! $(IO_DIR)/stamp: in-io ;
! in-io: _G_config.h
  	@rootme=`pwd`/ ; export rootme ; cd $(IO_DIR) ; \
  		$(MAKE) $(FLAGS_TO_PASS) stamp
  
***************
*** 319,325 ****
  		fi ; \
  	done
  	cd test-install; $(MAKE) $(TEST_INSTALL) \
! 	    CXX=$(bindir)/gcc COMPILE_FLAGS="" LIBS=-lg++
  
  ###**######################################################################
  #
--- 321,327 ----
  		fi ; \
  	done
  	cd test-install; $(MAKE) $(TEST_INSTALL) \
! 	    "CXX=$(CXX)" COMPILE_FLAGS="" LIBS=-lg++
  
  ###**######################################################################
  #

Re: Patch for libg++-2.3 makefiles

#378

Author: bothner
Date: Sun, 13 Dec 1992 16:45

21 lines
1236 bytes

Thanks for your suggestions.

> The first two patches make the C and C++ compilers for the target default
> to the same as those for the host, rather than to $(CC) and gcc.

Seems reasonable; I'll put it in if some other people agree.

> The next patch allows libg++ to be built in parallel

I put it in; it seems to work.  (Specifically, without causing libg++.a
to be re-built when everything is up-to-date.)

> The final patch makes the C++ compiler used for test-install the same as
> the one used for the build.

This one I disagree with.  The whole point is to test that the *installed*
compiler can find the librray we have just installed - i.e. that the
installed compiler and library are consistent and can work with each other.

	--Per Bothner
Cygnus Support     bothner@cygnus.com

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads