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]

PATH for libstdc++ Makefile



I just got bitten by an odd situation.  The line to build libstdc++.so
is something like:

  xgcc -g -O2 -fvtable-thunks -D_GNU_SOURCE -fno-implicit-templates
  -Wl,-soname,libstdc++-libc6.0-1.so.2 -shared -o
  libstdc++-2-libc6.0-1-2.9.0.so `cat piclist` -lm

But, this passes `-lgcc' to the linker and the directories searched do
not include the directory containing the recently built libgcc.a.
Therefore, you get whatever libgcc.a is lying around in
/usr/local/lib, etc.

Jeff, OK?

-- 
Mark Mitchell 			mark@markmitchell.com
Mark Mitchell Consulting	http://www.markmitchell.com

1998-09-21  Mark Mitchell  <mark@markmitchell.com>

	* Makefile.in ($(SHLIB)): Avoid getting bad libgcc.a's.

Index: Makefile.in
===================================================================
RCS file: /egcs/carton/cvsfiles/egcs/libstdc++/Makefile.in,v
retrieving revision 1.22
diff -c -p -r1.22 Makefile.in
*** Makefile.in	1998/09/17 00:30:53	1.22
--- Makefile.in	1998/09/22 03:10:12
*************** marlink:
*** 96,102 ****
  	@$(MAKE) $(MARLINK) "ARLINK=$(MARLINK)"
  
  $(SHLIB): piclist
! 	$(CC) $(LIBCXXFLAGS) $(SHFLAGS) -shared -o $(SHLIB) `cat piclist` $(SHDEPS)
  
  $(SHARLIB): $(SHLIB)
  	-rm -f t$(SHARLIB)
--- 96,102 ----
  	@$(MAKE) $(MARLINK) "ARLINK=$(MARLINK)"
  
  $(SHLIB): piclist
! 	$(CC) -L ../../gcc $(LIBCXXFLAGS) $(SHFLAGS) -shared -o $(SHLIB) `cat piclist` $(SHDEPS)
  
  $(SHARLIB): $(SHLIB)
  	-rm -f t$(SHARLIB)


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