Re: zlib and bipz2 not linking?

"Kuhl, Brian via Boost-build" <[email protected]>
Newsgroups gmane.comp.lib.boost.build
Message-ID <6C486AB80682E24095E3E77A408D68F201499127F1@ALA-MBD.corp.ad.wrs.com>
Hi Steven,
Does this mean that the usage requirement are not being met, and therefore zlib is not being included?
The reason I ask is this line in the debug output ..

     Building target '/zlib'
         Build request: object(property-set)@2707 ...
         Command line free features: <testing.launcher>../../../status/vxworks_boost_test_run.exp
         Target requirements:

         Common properties:  ...
         Usage requirements for zlib:
         Build properties:  ...

    - zlib                     : yes (cached)
         Usage requirements from zlib:  <relevant>cross-compile <relevant>link <relevant>static-only

I find it odd that the "usage requirements from zlib:" include the two custom parameters I define in project-config.jam ?
What does 'from' indicate in this context?  A requirement that is new in some way? A requirement that is not matched?

Brian

> -----Original Message-----
> From: Steven Watanabe [mailto:[email protected]]
> Sent: Friday, September 07, 2018 5:20 PM
> To: Kuhl, Brian; Boost.Build developer's and user's list
> Cc: Krejsa, Dan
> Subject: Re: [Boost-build] zlib and bipz2 not linking?
>
> AMDG
>
> On 09/07/2018 02:55 PM, Kuhl, Brian wrote:
> > So I have several '<library>object(file-target)@' but I don't think they are for
> /zlib and /bzip2?  There are 6  '<library>object' and 6 dependent Boost libraries
> on the link line.
> >
> > If zlib and bzip2 were being passed I think I should see 8, do you agree?
> >
>
>   No.  Boost.Test and Boost.IOStreams are direct dependencies
> and are not included in the usage-requirements.  You'll see
> them listed somewhere nearby as sources.  zlib and bzip2
> appear to be present as the two searched-lib targets.
> The problem is happening somewhere later on, but I'm
> not quite sure where.
>   Oh.  Are you using a modified version of Boost.Build?
> In particular, if gcc.jam names the rule gcc.vxworks.link like you
> tried in the thread "Is it possible to override CONFIG_COMMAND"
> instead of gcc.link.vxworks, as I suggested, it will definitely
> cause this problem among others.
>
> > Brian
> >
> >
> > ../../../run_a_test.sh gzip_test  --debug-building  -n -d0  > out.txt
> > cat out.txt
> >
> > Building target './gzip_test'
> >      Build request: object(property-set)@2701 <address-model>64 <cross-
> compile>vxworks    ...
> >
> > ... lots more stuff ...
> >
> >      Usage requirements for gzip_test:  <include>../../.. <include>../../..
> <library>object(searched-lib-target)@2717 <library>object(searched-lib-
> target)@2932 <relevant>context-impl   ...   <library>object(file-target)@3078
> <library>object(file-target)@3102 <library>object(file-target)@3138
> <relevant>context-impl  ...
> >      Build properties:   ...
> >      Usage requirements from gzip_test:
> <define>BOOST_CHRONO_STATIC_LINK=1  ...  <include>../../..
> <library>object(file-target)@3078 <library>object(file-target)@3102
> <library>object(file-target)@3138 <library>object(searched-lib-target)@2717 ...
> <use>object(file-target)@3138
> >
> >
> >     /yow-build62-lx2/bkuhl/vx7/compilers/llvm-
> 6.0.0.2/LINUX386/bin/ldpentium -m elf_x86_64  -L"/yow-build62-
> lx2/bkuhl/work/VSB/usr/lib/common" -o
> "../../../bin.v2/libs/iostreams/test/gzip_test.test/clang-vxworks-
> 4.2.1/debug/cross-compile-vxworks/static-only-on/gzip_test.vxe" /yow-
> build62-lx2/bkuhl/work/VSB/usr/lib/common//crt0.o
> "../../../bin.v2/libs/iostreams/test/gzip_test.test/clang-vxworks-
> 4.2.1/debug/cross-compile-vxworks/static-only-on/gzip_test.o"
> "../../../bin.v2/libs/iostreams/build/clang-vxworks-4.2.1/debug/cross-compile-
> vxworks/static-only-on/libboost_iostreams.a"
> "../../../bin.v2/libs/test/build/clang-vxworks-4.2.1/debug/cross-compile-
> vxworks/static-only-on/libboost_unit_test_framework.a"
> "../../../bin.v2/libs/filesystem/build/clang-vxworks-4.2.1/debug/cross-compile-
> vxworks/static-only-on/libboost_filesystem.a"
> "../../../bin.v2/libs/timer/build/clang-vxworks-4.2.1/debug/cross-compile-
> vxworks/static-only-on/libboost_timer.a"
> "../../../bin.v2/libs/chrono/build/clang-vxworks-4.2.1/debug/cross-compile-
> vxworks/static-only-on/libboost_chrono.a"
> "../../../bin.v2/libs/system/build/clang-vxworks-4.2.1/debug/cross-compile-
> vxworks/static-only-on/libboost_system.a" --start-group -lunix -lnet  -lc  -
> lc_internal  -lllvm  -lcplusplus  -lllvmcplus  -ldl  -lsyscall      --end-group  --defsym
> __wrs_rtp_base=0x200000000 -u __tls__  -u __wr_need_frame_add -T/yow-
> build62-lx2/bkuhl/vx7/helix/guests/vxworks-
> 7/build/tool/llvm_2016_04/usr/ldscript.vxe.x86-64   -L/yow-build62-
> lx2/bkuhl/work/VSB/usr/lib/common -z common-page-size=8192  -static
> > <snip>
> In Christ,
> Steven Watanabe

_______________________________________________
Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.