Re: [Boost-Users] Boost Building

From: Vadim Egorov (egorovv_at_[hidden])
Date: 2002-03-08 02:58:23

"karl_m_au" <karlm_at_[hidden]> writes:

> Hiya
>
> I'm trying to build boost 1.27.0 on a Debian linux system.
>
> I've built the boost version of jam. 
>
> Both g++ 2.95.3 and g++ 3.0.3 are installed. I'm pretty 
> sure I've made the appropriate changes to get g++ 3.0 to 
> be used in the build process.
>
> I've used various versions of the command line recommended 
> in the documentation.
>
> Very few of the builds work, becuse of this:
>
>    g++-3.0  -c -Wall -ftemplate-depth-100     -I"libs/regex/build"  
> -o
> "libs/regex/build/bin/libboost_regex.a/gcc-3/debug/c_regex_traits.o" 
> "libs/regex/build/../src/c_regex_traits.cpp" 
>
> Somehow the <include> directive isn't working.
>
> Any clues?
>
I guess you have the g++ 3.0 binary installed as g++3.0. I have a similar 
situation with FreeBSD where it is called g++30. To be able to switch compilers
I've made the changes below - and now I can add -sCXX=g++30 ($(CC) is not really used)
to use g++30 as a compiler - works for me.

-- 
Vadim
---
When man calls an animal "vicious", he usually means that it will attempt
to defend itself when he tries to kill it.
Index: gcc-tools.jam
===================================================================
RCS file: /cvsroot/boost/boost/tools/build/gcc-tools.jam,v
retrieving revision 1.26
diff -c -3 -c -r1.26 gcc-tools.jam
*** gcc-tools.jam	2 Mar 2002 23:06:58 -0000	1.26
--- gcc-tools.jam	8 Mar 2002 07:46:50 -0000
***************
*** 10,15 ****
--- 10,17 ----
  GCC_BIN_DIRECTORY ?= "" ; # Don't clobber tool names if GCC_ROOT_DIRECTORY not set
  GCC_INCLUDE_DIRECTORY ?= $(GCC_ROOT_DIRECTORY)$(SLASH)include ;
  GCC_STDLIB_DIRECTORY ?= $(GCC_ROOT_DIRECTORY)$(SLASH)lib ;
+ CXX ?= g++ ;
+ CC ?= gcc ;
  
  flags gcc LINKFLAGS <runtime-link>static : -static ;
  flags gcc CFLAGS <debug-symbols>on : -g ;
***************
*** 108,114 ****
  # for gcc, we repeat all libraries so that dependencies are always resolved
  actions gcc-Link-action bind NEEDLIBS
  {
!     $(GCC_BIN_DIRECTORY)g++ $(IMPLIB_COMMAND)$(<[2]) $(LINKFLAGS) -o "$(<[1])" -L$(LIBPATH:T) -L$(STDLIBPATH:T) "$(>)" "$(NEEDLIBS)" "$(NEEDLIBS)" -l$(FINDLIBS) -Wl,-rpath-link,. -Wl,-soname,$(<[1]:D=).$(DLLVERSION)
  }
  
  actions gcc-dllwrap bind NEEDLIBS
--- 110,116 ----
  # for gcc, we repeat all libraries so that dependencies are always resolved
  actions gcc-Link-action bind NEEDLIBS
  {
!     $(GCC_BIN_DIRECTORY)$(CXX) $(IMPLIB_COMMAND)$(<[2]) $(LINKFLAGS) -o "$(<[1])" -L$(LIBPATH:T) -L$(STDLIBPATH:T) "$(>)" "$(NEEDLIBS)" "$(NEEDLIBS)" -l$(FINDLIBS) -Wl,-rpath-link,. -Wl,-soname,$(<[1]:D=).$(DLLVERSION)
  }
  
  actions gcc-dllwrap bind NEEDLIBS
***************
*** 125,131 ****
  
  actions gcc-Cc-action
  {
!     $(GCC_BIN_DIRECTORY)gcc -c -Wall -U$(UNDEFS) -D$(DEFINES) $(CFLAGS) -I"$(HDRS)" -isystem$(SPACE)"$(STDHDRS)" -o "$(<)" "$(>)"
  }
  
  #### C++ ####
--- 127,133 ----
  
  actions gcc-Cc-action
  {
!     $(GCC_BIN_DIRECTORY)$(CC) -c -Wall -U$(UNDEFS) -D$(DEFINES) $(CFLAGS) -I"$(HDRS)" -isystem$(SPACE)"$(STDHDRS)" -o "$(<)" "$(>)"
  }
  
  #### C++ ####
***************
*** 136,142 ****
  
  actions gcc-C++-action
  {
!     $(GCC_BIN_DIRECTORY)g++ -c -Wall -ftemplate-depth-100 -U$(UNDEFS) -D$(DEFINES) $(CFLAGS) $(C++FLAGS) -I"$(HDRS)" -isystem$(SPACE)"$(STDHDRS)" -o "$(<)" "$(>)"
  }
  
  #### Archive ####
--- 138,144 ----
  
  actions gcc-C++-action
  {
!     $(GCC_BIN_DIRECTORY)$(CXX) -c -Wall -ftemplate-depth-100 -U$(UNDEFS) -D$(DEFINES) $(CFLAGS) $(C++FLAGS) -I"$(HDRS)" -isystem$(SPACE)"$(STDHDRS)" -o "$(<)" "$(>)"
  }
  
  #### Archive ####

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com