Re: [Boost-users] problem building boost's bjam for boost-1.32.0 on solaris with gcc

From: William Deegan (bdbaddog_at_[hidden])
Date: 2006-07-13 22:24:08

On 7/13/06, Rene Rivera <grafikrobot_at_[hidden]> wrote:
> William Deegan wrote:
> > On 7/13/06, William Deegan <bdbaddog_at_[hidden]> wrote:
> >> On 7/13/06, Rene Rivera <grafikrobot_at_[hidden]> wrote:
> >>> William Deegan wrote:
> >>>> Greetings,
> >>>>
> >>>> Here's whats happening:
> >>>> bash ./build.sh
> >>>> ###
> >>>> ### Using 'gcc' toolset.
> >>>> ###
> >>>> rm -rf bootstrap.gcc
> >>>> mkdir bootstrap.gcc
> >>>> gcc -o bootstrap.gcc/jam0 command.c compile.c execnt.c execunix.c
> >>>> execvms.c expand.c filent.c fileos2.c fileunix.c filevms.c glob.c
> >>>> hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c
> >>>> make1.c newstr.c option.c parse.c pathunix.c pathvms.c regexp.c
> >>>> rules.c scan.c search.c subst.c timestamp.c variable.c modules.c
> >>>> strings.c filesys.c builtins.c pwd.c
> >>>> ./bootstrap.gcc/jam0 -f build.jam --toolset=gcc --toolset-root=
> >>>> build.jam:66: in module scope
> >>>> *** argument error
> >>>> * rule toolset ( name command : opt.out + : opt.define + :
> >>>> release-flags * : debug-flags * : linklibs * )
> >>>> * called with: ( cc /eng/tools/cm/solaris/bin/gcc  -m64  : -o  : -D :
> >>>> -s -O : -g :  )
> >>>> * extra argument
> >>>> build.jam:39:see definition of rule 'toolset' being called
> >>>>
> >>>> This is run via script.
> >>>> If I run it interactively it builds fine.
> >>>> I'm trying to script up building boost+ many other third party
> >>>> packages for many platforms.
> >>>> Any idea why it fails when run via a script?
> >>> Yes. It's having problems with the value of "CC" env variable
> >>> "/eng/tools/cm/solaris/bin/gcc  -m64". Try clearing that value out
> >>> before running the build.sh script.
> >>>
> >>> I'll fix the real problem in the version of bjam :-)
> >> WoW..  Fast answer. Thanks. That did the trick.
> >
> > I guess, how do I get bjam to build with the gcc I want and with -m64
> > (or 64 bits)?
>
> Set CC to only the compiler "/eng/tools/cm/solaris/bin/gcc", and set
> CFLAGS to "-m64", then invoke "./build.sh cc". But it's not like you
> need to. The default compiler should work just fine even if it's not 64
> bit. Or is there some particular reason why you need to compile it in 64
> bit mode?
>
>
> NOTE: AFAIK bjam has never been tested in 64 bit addressing operation.

I guess I meant to build the boost libraries with my specific gcc 64
bit on solaris.

Thanks,
Bill