Boost-Build :

Date view	Thread view	Subject view	Author view

From: Michael Ellenberger (mellenbe_at_[hidden])
Date: 2004-06-16 16:29:21

Next message: David Abrahams: "Re: Some fundamental misunderstandings (v2)"
Previous message: Mark Elston: "RE: [jamboost] Re: Some fundamental misunderstandings (v2)"
Maybe in reply to: Michael Ellenberger: "RE: [jamboost] Configuring 64 bit builds on solaris"

I am building using the version 1 syntax. I occasionally get bjam cores.
Some of this is seems to be based on my BUILD values and other times I can
run bjam again without changing anything and it will work.

I've set environmental variables for everything I want pass to the BUILD.

BOOST_BUILD_PATH=/home/jupiter3/mellenbe/boost-stl/local/src/boost-build

STLPORT_4.6.1_PATH=/home/jupiter3/mellenbe/boost-stl/local

STLPORT_VERSION=4.6.1

STLPORT_LIB_DIRECTORY=lib

STLPORT_INCLUDE_DIRECTORY=include/stlport

GCC_ROOT_DIRECTORY=/usr/local/gcc/3.3.3

GCC_STDLIB_DIRECTORY=/usr/local/gcc/3.3.3/lib/sparcv9

TOOLS=gcc-stlport

BUILD=<library-path>/usr/local/gcc/3.3.3/lib/sparcv9 <cxxflags>-m64
<linkflags>-m64 <stlport-iostream>on <runtime-link>static release debug

This works ok and keeps the command line down to a minimum.

I am getting errors whenever I specify <runtime-link>static. I turned
verbose on in the linker and this is what I see. The linker does not like
the combination of parameters it's getting. This is one of many variations
I have tried to get by this problem.

Any suggestions, anyone?

Thanks,

Mike

Configured with: ../configure --prefix=/usr/local/gcc/3.3.3
--enable-languages=c

,c++

Thread model: posix

gcc version 3.3.3

/usr/local/gcc/3.3.3/lib/gcc-lib/sparc-sun-solaris2.7/3.3.3/collect2 -V -dn
-Bs

tatic -G -dy -z text -Y P,/usr/lib/sparcv9 -Qy -o
bin/boost/libs/test/build/libb

oost_prg_exec_monitor.so/gcc-stlport/debug/runtime-link-static/shared-linkab
le-t

rue/libboost_prg_exec_monitor-gcc-sgdp-1_31.so
/usr/local/gcc/3.3.3/lib/gcc-lib/

sparc-sun-solaris2.7/3.3.3/sparcv9/crti.o /usr/ccs/lib/sparcv9/values-Xa.o
/usr/

local/gcc/3.3.3/lib/gcc-lib/sparc-sun-solaris2.7/3.3.3/sparcv9/crtbegin.o
-L/usr

/local/gcc/3.3.3/lib/sparcv9 -L/usr/local/gcc/3.3.3/lib
-L/home/jupiter3/mellenb

e/boost-stl/local/lib
-L/usr/local/gcc/3.3.3/lib/gcc-lib/sparc-sun-solaris2.7/3.

3.3/sparcv9 -L/usr/local/gcc/3.3.3/lib/gcc-lib/sparc-sun-solaris2.7/3.3.3
-L/usr

/ccs/bin/sparcv9 -L/usr/ccs/bin -L/usr/ccs/lib/sparcv9 -L/usr/ccs/lib
-L/usr/loc

al/gcc/3.3.3/lib/gcc-lib/sparc-sun-solaris2.7/3.3.3/../../../sparcv9
-L/usr/loca

l/gcc/3.3.3/lib/gcc-lib/sparc-sun-solaris2.7/3.3.3/../../.. -L/lib/sparcv9
-L/us

r/lib/sparcv9 -Bstatic -lstdc++ -Bdynamic
bin/boost/libs/test/build/libboost_prg

_exec_monitor.so/gcc-stlport/debug/runtime-link-static/shared-linkable-true/
exec

ution_monitor.o
bin/boost/libs/test/build/libboost_prg_exec_monitor.so/gcc-stlpo

rt/debug/runtime-link-static/shared-linkable-true/cpp_main.o
-lstlport_gcc_stlde

bug -lrt -lstdc++ -lm -lgcc -lgcc_eh -lgcc -lgcc_eh
/usr/local/gcc/3.3.3/lib/gcc

-lib/sparc-sun-solaris2.7/3.3.3/sparcv9/crtend.o
/usr/local/gcc/3.3.3/lib/gcc-li

b/sparc-sun-solaris2.7/3.3.3/sparcv9/crtn.o

ld: Software Generation Utilities - Solaris Link Editors: 5.7-1.280

ld: warning: option -d appears more than once, first setting taken

ld: fatal: option -dn and -z[text|textwarn|textoff] are incompatible

ld: fatal: option -dn and -G are incompatible

ld: fatal: Flags processing errors

collect2: ld returned 1 exit status

LD_LIBRARY_PATH=/usr/local/gcc/3.3.3/lib/sparcv9:bin/boost/libs/test/build/l

ibboost_prg_exec_monitor.so/gcc-stlport/debug/runtime-link-static/shared-lin
kabl

e-true:$LD_LIBRARY_PATH

export LD_LIBRARY_PATH

/usr/local/gcc/3.3.3/bin//g++ -static -g --verbose -m64
-static-libgcc -W

l,-Bstatic -lstdc++ -Wl,-Bdynamic -fPIC -shared -pthreads -o
"bin/boost/libs/te

st/build/libboost_prg_exec_monitor.so/gcc-stlport/debug/runtime-link-static/
shar

ed-linkable-true/libboost_prg_exec_monitor-gcc-sgdp-1_31.so"
-L"/usr/local/gcc/

3.3.3/lib/sparcv9" -L"/usr/local/gcc/3.3.3/lib"
-L"/home/jupiter3/mellenbe/boos

t-stl/local/lib"
"bin/boost/libs/test/build/libboost_prg_exec_monitor.so/gcc-st

lport/debug/runtime-link-static/shared-linkable-true/execution_monitor.o"
"bin/b

oost/libs/test/build/libboost_prg_exec_monitor.so/gcc-stlport/debug/runtime-
link

-static/shared-linkable-true/cpp_main.o" -lstlport_gcc_stldebug -lrt

> -----Original Message-----

> From: Vladimir Prus [mailto:ghost_at_[hidden]] On Behalf Of Vladimir

> Prus

> Sent: Tuesday, June 15, 2004 10:48 PM

> To: jamboost_at_[hidden]

> Subject: Re: [jamboost] Configuring 64 bit builds on solaris

> Hi Michael,

> > In the boost-build directory file user-config.jam was updated

> >

> > using gcc;

> >

> > using gcc : 3.3.3 g++ /usr/local/gcc/3.3.3/bin;

> >

> > This seems to get me the compiler I want to use for the build. Can I

> > assume this is a V2 file? When I build boost will this file be used?

> It will be used if you pass --v2 flag to bjam, when invoking it in the

> top-level directory of boost. The V1 version is still the default for

> Boost,

> so you need to explicitly use V2.

> > bjam cflags="-m64" linkflags="-m64"

> >

> > This builds me an ELF64 executable.

> Good.

> > Now if I want to build boost and would like to set up a configuration

> file.

> > I'm not sure what its name would be or what directory it would be placed

> > in.

> >

> > Some of what we need to set is as follows,

> >

> > bjam --prefix="~/boost-stl/local/boost_1_31_0" -sTOOLS="gcc-stlport"

> > -sBUILD="<t

> >

> > hreading>multi <stlport-iostream>on <runtime-link>dynamic release debug"

> > -sSTLPO

> >

> > RT_4.6.1_PATH=~/boost-stl/local -sSTLPORT_VERSION=4.6.1

> > STLPORT_LIB_DIRECTORY=li

> >

> > b -sSTLPORT_INCLUDE_DIRECTORY=include/stlport install

> >

> > I don't know if this is V1 or V2 syntax! I'd like to have this

> information

> > in a configuration file and not the command line.

> This is V1 syntax. What's worse, the "install" rule is one of few things

> that

> are not implemented in V2 yet.

> So, if you want to "just" build Boost, you can use the above syntax. If

> you

> have some other requirements, you might need to wait for V2 to implement

> "install". And when it happens, you'll be able to edit top-level Jamfile

> to

> use the properties you want (gcc with stlport, dynamic linking, etc).

> - Volodya

> Yahoo! Groups Links

> http://groups.yahoo.com/group/jamboost/

> jamboost-unsubscribe_at_[hidden]

> http://docs.yahoo.com/info/terms/

------_=_NextPart_001_01C453E6.689D487C Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>

</head>

I am building using the version 1 syntax.=A0 I occasionally get bja=
m
cores.=A0 Some of this is seems to be based on my BUILD values and other ti=
mes I
can run bjam again without changing anything and it will work.</font=
>

I've set environmental variables for everything I want pass to the
BUILD.

BOOST_BUILD_PATH=3D/home/jupiter3/mellenbe/boost-stl/local/src/boos=
t-build

STLPORT_4.6.1_PATH=3D/home/jupiter3/mellenbe/boost-stl/local=

STLPORT_VERSION=3D4.6.1

STLPORT_LIB_DIRECTORY=3Dlib

STLPORT_INCLUDE_DIRECTORY=3Dinclude/stlport

GCC_ROOT_DIRECTORY=3D/usr/local/gcc/3.3.3

GCC_STDLIB_DIRECTORY=3D/usr/local/gcc/3.3.3/lib/sparcv9</fon=
t>

TOOLS=3Dgcc-stlport

BUILD=3D<library-path>/usr/local/gcc/3.3.3/lib/sparcv9
<cxxflags>-m64 <linkflags>-m64 <stlport-iostream>on
<runtime-link>static release debug

This works ok and keeps the command line down to a minimum.<=
/font>

I am getting errors whenever I specify <runtime-link>static.=
=A0 I
turned verbose on in the linker and this is what I see. =A0The linker does =
not
like the combination of parameters it's getting.=A0 This is one of many
variations I have tried to get by this problem.

Any suggestions, anyone?

Thanks,

Mike

Configured with: ../configure --prefix=3D/usr/local/gcc/3.3.3
--enable-languages=3Dc

,c++

Thread model: posix

gcc version 3.3.3

=A0/usr/local/gcc/3.3.3/lib/gcc-lib/sparc-sun-solaris2.7/3.3.3/coll=
ect2
-V -dn -Bs

tatic -G -dy -z text -Y P,/usr/lib/sparcv9 -Qy -o
bin/boost/libs/test/build/libb

oost_prg_exec_monitor.so/gcc-stlport/debug/runtime-link-static/shar=
ed-linkable-t

rue/libboost_prg_exec_monitor-gcc-sgdp-1_31.so
/usr/local/gcc/3.3.3/lib/gcc-lib/

sparc-sun-solaris2.7/3.3.3/sparcv9/crti.o
/usr/ccs/lib/sparcv9/values-Xa.o /usr/

local/gcc/3.3.3/lib/gcc-lib/sparc-sun-solaris2.7/3.3.3/sparcv9/crtb=
egin.o
-L/usr

/local/gcc/3.3.3/lib/sparcv9 -L/usr/local/gcc/3.3.3/lib
-L/home/jupiter3/mellenb

e/boost-stl/local/lib
-L/usr/local/gcc/3.3.3/lib/gcc-lib/sparc-sun-solaris2.7/3.</p=
>

3.3/sparcv9 -L/usr/local/gcc/3.3.3/lib/gcc-lib/sparc-sun-solaris2.7=
/3.3.3
-L/usr

/ccs/bin/sparcv9 -L/usr/ccs/bin -L/usr/ccs/lib/sparcv9 -L/usr/ccs/l=
ib
-L/usr/loc

al/gcc/3.3.3/lib/gcc-lib/sparc-sun-solaris2.7/3.3.3/../../../sparcv=
9
-L/usr/loca

l/gcc/3.3.3/lib/gcc-lib/sparc-sun-solaris2.7/3.3.3/../../..
-L/lib/sparcv9 -L/us

r/lib/sparcv9 -Bstatic -lstdc++ -Bdynamic
bin/boost/libs/test/build/libboost_prg

_exec_monitor.so/gcc-stlport/debug/runtime-link-static/shared-linka=
ble-true/exec

ution_monitor.o bin/boost/libs/test/build/libboost_prg_exec_monitor=
.so/gcc-stlpo

rt/debug/runtime-link-static/shared-linkable-true/cpp_main.o
-lstlport_gcc_stlde

bug -lrt -lstdc++ -lm -lgcc -lgcc_eh -lgcc -lgcc_eh
/usr/local/gcc/3.3.3/lib/gcc

-lib/sparc-sun-solaris2.7/3.3.3/sparcv9/crtend.o /usr/local/gcc/3.3=
.3/lib/gcc-li

b/sparc-sun-solaris2.7/3.3.3/sparcv9/crtn.o

ld: Software Generation Utilities - Solaris Link Editors: 5.7-1.280=

ld: warning: option -d appears more than once, first setting taken<=
/span>

ld: fatal: option -dn and -z[text|textwarn|textoff] are incompatibl=
e

ld: fatal: option -dn and -G are incompatible

ld: fatal: Flags processing errors

collect2: ld returned 1 exit status

=A0=A0=A0
LD_LIBRARY_PATH=3D/usr/local/gcc/3.3.3/lib/sparcv9:bin/boost/libs/test/buil=
d/l

ibboost_prg_exec_monitor.so/gcc-stlport/debug/runtime-link-static/s=
hared-linkabl

e-true:$LD_LIBRARY_PATH

=A0=A0=A0 export LD_LIBRARY_PATH

=A0=A0=A0 /usr/local/gcc/3.3.3/bin//g++=A0=A0=A0 -static -g --verbo=
se -m64
-static-libgcc -W

l,-Bstatic -lstdc++ -Wl,-Bdynamic -fPIC -shared -pthreads=A0 -o
"bin/boost/libs/te

st/build/libboost_prg_exec_monitor.so/gcc-stlport/debug/runtime-lin=
k-static/shar

ed-linkable-true/libboost_prg_exec_monitor-gcc-sgdp-1_31.so"=
=A0 -L"/usr/local/gcc/

3.3.3/lib/sparcv9"=A0 -L"/usr/local/gcc/3.3.3/lib"
-L"/home/jupiter3/mellenbe/boos

t-stl/local/lib"=A0
"bin/boost/libs/test/build/libboost_prg_exec_monitor.so/gcc-st<=
/font>

lport/debug/runtime-link-static/shared-linkable-true/execution_moni=
tor.o"
"bin/b

oost/libs/test/build/libboost_prg_exec_monitor.so/gcc-stlport/debug=
/runtime-link

-static/shared-linkable-true/cpp_main.o"=A0=A0=A0=A0
-lstlport_gcc_stldebug -lrt

> -----Original Message-----

> From: Vladimir Prus [mailto:ghost_at_[hidden]] On Behalf Of =
Vladimir

> Prus

> Sent: Tuesday, June 15, 2004 10:48 PM

> To: jamboost_at_[hidden]

> Subject: Re: [jamboost] Configuring 64 bit builds on solaris</=
span>

>

> Hi Michael,

>

> > In the boost-build directory file user-config.jam was upd=
ated

> >

> >=A0=A0 using gcc;

> >

> >=A0=A0 using gcc : 3.3.3 g++ /usr/local/gcc/3.3.3/bin;</sp=
an>

> >

> > This seems to get me the compiler I want to use for the
build.=A0 Can I

> > assume this is a V2 file?=A0 When I build boost will this=
file
be used?

>

> It will be used if you pass --v2 flag to bjam, when invoking i=
t in
the

> top-level directory of boost. The V1 version is still the defa=
ult
for

> Boost,

> so you need to explicitly use V2.

>

> > bjam cflags=3D"-m64" linkflags=3D"-m64&quo=
t;

> >

> > This builds me an ELF64 executable.

>

> Good.

>

> > Now if I want to build boost and would like to set up a
configuration

> file.

> > I'm not sure what its name would be or what directory it
would be placed

> > in.

> >

> > Some of what we need to set is as follows,<=
/p>

> >

> > bjam --prefix=3D"~/boost-stl/local/boost_1_31_0&quot=
;
-sTOOLS=3D"gcc-stlport"

> > -sBUILD=3D"<t

> >

> > hreading>multi <stlport-iostream>on
<runtime-link>dynamic release debug"

> > -sSTLPO

> >

> > RT_4.6.1_PATH=3D~/boost-stl/local -sSTLPORT_VERSION=3D4.6=
.1

> > STLPORT_LIB_DIRECTORY=3Dli

> >

> > b -sSTLPORT_INCLUDE_DIRECTORY=3Dinclude/stlport install</=
span>

> >

> > I don't know if this is V1 or V2 syntax!=A0 I'd like to h=
ave
this

> information

> > in a configuration file and not the command line.<=
/font>

>

> This is V1 syntax. What's worse, the "install" rule =
is
one of few things

> that

> are not implemented in V2=A0 yet.

>

> So, if you want to "just" build Boost, you can use t=
he
above syntax. If

> you

> have some other requirements, you might need to wait for V2 to
implement

> "install". And when it happens, you'll be able to ed=
it
top-level Jamfile

> to

> use the properties you want (gcc with stlport, dynamic linking=
,
etc).

>

> - Volodya

>

> ------------------------ Yahoo! Groups Sponsor
--------------------~-->

> Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.</s=
pan>

> Now with Pop-Up Blocker. Get it for free!

> http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/z3wwlB/TM=
>

> --------------------------------------------------------------=
------~->

>

> Yahoo! Groups Links

>

> <*> To visit your group on the web, go to:=

> =A0=A0=A0=A0=A0 http://groups.yahoo.com/group/jamboost/><=
/font>

>

> <*> To unsubscribe from this group, send an email to:</s=
pan>

> =A0=A0=A0=A0=A0jamboost-unsubscribe_at_[hidden]</fo=
nt>

>

> <*> Your use of Yahoo! Groups is subject to:</fon=
t>

> =A0=A0=A0=A0=A0 http://docs.yahoo.com/info/terms/>=

>

</div>

</body>

</html>
------_=_NextPart_001_01C453E6.689D487C--

Next message: David Abrahams: "Re: Some fundamental misunderstandings (v2)"
Previous message: Mark Elston: "RE: [jamboost] Re: Some fundamental misunderstandings (v2)"
Maybe in reply to: Michael Ellenberger: "RE: [jamboost] Configuring 64 bit builds on solaris"

Date view	Thread view	Subject view	Author view

Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk