zlib and bipz2 not linking?

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

zlib and bipz2 not linking?

Boost - Build mailing list

Hi Experts,

When cross compiling for VxWorks on Linux  …

In previous versions of Boost the presence of libz.a and libbz2.a were detected and linked into iostreams tests.

But with v1.68 the libraries are not being added to the link line.

Please see below for an example error.

 

The config-cache and the build console indicate that libz and bzip are being found, it’s just not being used when required.

 

I’m having trouble deciphering ac.jam, so I was hopping someone could help me understand  how a dependency on /zlib//zlib is supposed to add –lz to the link line?

And why it might not work in my case?

 

Many thanks,

 

Brian Kuhl

Wind River

 

 

. ./vxworks_env.sh &&  cd status   &&  \

                    BOOST_TELNET_ADDR="localhost 20023"  \

                    LAYER_SRC_PATH="yow-build62-lx:VSB/3pp/BOOST/boost_1_68_0" \

                    PKG_SRC_BUILD_DIR="/yow-build62-lx2/bkuhl/work/VSB/3pp/BOOST/boost_1_68_0"  \

                    VSB_LD_LIBRARY_PATH="yow-build62-lx:VSB/usr/root/llvm/bin;yow-build62-lx:VSB/usr/lib/common" \

../b2 -j1 --prefix=/yow-build62-lx2/bkuhl/work/VSB/usr/root --libdir=/yow-build62-lx2/bkuhl/work/VSB/usr/lib/common --includedir=/yow-build62-lx2/bkuhl/work/VSB/usr/h/public    toolset=clang-vxworks cross-compile=vxworks --reconfigure target-os=vxworks "variant=debug" address-model=64  static-only=on  "testing.launcher=./vxworks_boost_test_run.exp" "--limit-tests=iostreams|system" "--exclude-tests=coroutine2|function_types|functional|logic|rational" -d2

Performing configuration checks

    - default address-model    : 64-bit

    - default architecture     : x86

    - default address-model    : 64-bit

    - default architecture     : x86

    - symlinks supported       : yes

    - BOOST_COMP_GNUC >= 4.3.0 : no

    - zlib                     : yes

    - bzip2                    : yes

    - lzma                     : no

    - has_icu builds           : no

...patience...

...patience..

 

 

module config-cache {

  set "default address-model-32-bit-64-bit-<target-os>vxworks-<toolset-clang:version>4.2.1-<toolset>clang" : "2" ;

  set "default architecture-arm-mips1-power-sparc-x86-combined-<target-os>vxworks-<toolset-clang:version>4.2.1-<toolset>clang" : "5" ;

  set "default address-model-32-bit-64-bit-power-sparc-x86-combined-<target-os>linux-<toolset-clang:version>4.2.1-<toolset>clang" : "2" ;

  set "default architecture-arm-mips1-power-sparc-x86-combined-<target-os>linux-<toolset-clang:version>4.2.1-<toolset>clang" : "5" ;

  set "symlinks supported" : "true" ;

  set "BOOST_COMP_GNUC >= 4.3.0-<address-model>64-<architecture>x86-<target-os>vxworks-<toolset-clang:platform>vxworks-<toolset-clang:version>4.2.1-<toolset>clang" : "false" ;

  set "ac-library-zlib-<address-model>64-<architecture>x86-<link>static-<target-os>vxworks-<toolset-clang:platform>vxworks-<toolset-clang:version>4.2.1-<toolset>clang" : "%default" "z" "<link>static" ;

  set "ac-library-bzip2-<address-model>64-<architecture>x86-<link>static-<target-os>vxworks-<toolset-clang:platform>vxworks-<toolset-clang:version>4.2.1-<toolset>clang" : "%default" "bz2" "<link>static" ;

  set "ac-library-lzma-<address-model>64-<architecture>x86-<link>static-<target-os>vxworks-<toolset-clang:platform>vxworks-<toolset-clang:version>4.2.1-<toolset>clang" : "missing" ;

  set "has_icu builds-<address-model>64-<architecture>x86-<target-os>vxworks-<toolset-clang:platform>vxworks-<toolset-clang:version>4.2.1-<toolset>clang" : "false" ;

}

 

 

 

 

clang-vxworks.link ../bin.v2/libs/iostreams/test/bzip2_test.test/clang-vxworks-4.2.1/debug/cross-compile-vxworks/static-only-on/bzip2_test.vxe

    /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/bzip2_test.test/clang-vxworks-4.2.1/debug/cross-compile-vxworks/static-only-on/bzip2_test.vxe" /yow-build62-lx2/bkuhl/work/VSB/usr/lib/common//crt0.o "../bin.v2/libs/iostreams/test/bzip2_test.test/clang-vxworks-4.2.1/debug/cross-compile-vxworks/static-only-on/bzip2_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

../bin.v2/libs/iostreams/build/clang-vxworks-4.2.1/debug/cross-compile-vxworks/static-only-on/libboost_iostreams.a(bzip2.o): In function `boost::iostreams::detail::bzip2_base::end(bool)':

/yow-build62-lx2/bkuhl/work/VSB/3pp/BOOST/boost_1_68_0/status/../libs/iostreams/src/bzip2.cpp:121: undefined reference to `BZ2_bzCompressEnd'

/yow-build62-lx2/bkuhl/work/VSB/3pp/BOOST/boost_1_68_0/status/../libs/iostreams/src/bzip2.cpp:122: undefined reference to `BZ2_bzDecompressEnd'

../bin.v2/libs/iostreams/build/clang-vxworks-4.2.1/debug/cross-compile-vxworks/static-only-on/libboost_iostreams.a(bzip2.o): In function `boost::iostreams::detail::bzip2_base::compress(int)':

/yow-build62-lx2/bkuhl/work/VSB/3pp/BOOST/boost_1_68_0/status/../libs/iostreams/src/bzip2.cpp:128: undefined reference to `BZ2_bzCompress'

../bin.v2/libs/iostreams/build/clang-vxworks-4.2.1/debug/cross-compile-vxworks/static-only-on/libboost_iostreams.a(bzip2.o): In function `boost::iostreams::detail::bzip2_base::decompress()':

/yow-build62-lx2/bkuhl/work/VSB/3pp/BOOST/boost_1_68_0/status/../libs/iostreams/src/bzip2.cpp:133: undefined reference to `BZ2_bzDecompress'

../bin.v2/libs/iostreams/build/clang-vxworks-4.2.1/debug/cross-compile-vxworks/static-only-on/libboost_iostreams.a(bzip2.o): In function `boost::iostreams::detail::bzip2_base::do_init(bool, void* (*)(void*, int, int), void (*)(void*, void*), void*)':

/yow-build62-lx2/bkuhl/work/VSB/3pp/BOOST/boost_1_68_0/status/../libs/iostreams/src/bzip2.cpp:153: undefined reference to `BZ2_bzCompressInit'

/yow-build62-lx2/bkuhl/work/VSB/3pp/BOOST/boost_1_68_0/status/../libs/iostreams/src/bzip2.cpp:157: undefined reference to `BZ2_bzDecompressInit'

...failed clang-vxworks.link ../bin.v2/libs/iostreams/test/bzip2_test.test/clang-vxworks-4.2.1/debug/cross-compile-vxworks/static-only-on/bzip2_test.vxe...

 

 


_______________________________________________
Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build
Reply | Threaded
Open this post in threaded view
|

Re: zlib and bipz2 not linking?

Boost - Build mailing list
AMDG

On 09/06/2018 09:43 PM, Kuhl, Brian via Boost-build wrote:

> Hi Experts,
> When cross compiling for VxWorks on Linux  ...
> In previous versions of Boost the presence of libz.a and libbz2.a were detected and linked into iostreams tests.
> But with v1.68 the libraries are not being added to the link line.
> Please see below for an example error.
>
> The config-cache and the build console indicate that libz and bzip are being found, it's just not being used when required.
>
> I'm having trouble deciphering ac.jam, so I was hopping someone could help me understand  how a dependency on /zlib//zlib is supposed to add -lz to the link line?
> And why it might not work in my case?
>

  What's supposed to happen is that ac-library.construct
returns a target representing -lz.  When boost_iostreams
is built as a static library, it propagates this target
to its dependencies as a <library> usage requirement.
I would recommend --debug-building and/or --debug-generators,
but that just shows the dependency as <library>object(file-target)@NNN
which is not really useful.

  Okay, try building just one test target with
`--debug-building --debug-generators -n -d0`.
There are two things that you should be looking
for in the output.  First of all, there should
be two lines like this:

         Usage requirements for boost_iostreams:  ...
         Build properties:  ... <install-dependencies>off
<library>object(file-target)@4855 ...

If the <library> is missing, then that means that zlib is
not being passed to the boost_iostreams target.

The second line to look for is:
         Usage requirements from boost_iostreams:  <include>.
<library>object(file-target)@4855 <relevant>address-model ...

If there is no library here, then that means the problem
is in the propagation of static libraries.

> Many thanks,
>
> Brian Kuhl
> Wind River
>
>
> . ./vxworks_env.sh &&  cd status   &&  \
>                     BOOST_TELNET_ADDR="localhost 20023"  \
>                     LAYER_SRC_PATH="yow-build62-lx:VSB/3pp/BOOST/boost_1_68_0" \
>                     PKG_SRC_BUILD_DIR="/yow-build62-lx2/bkuhl/work/VSB/3pp/BOOST/boost_1_68_0"  \
>                     VSB_LD_LIBRARY_PATH="yow-build62-lx:VSB/usr/root/llvm/bin;yow-build62-lx:VSB/usr/lib/common" \
> ../b2 -j1 --prefix=/yow-build62-lx2/bkuhl/work/VSB/usr/root --libdir=/yow-build62-lx2/bkuhl/work/VSB/usr/lib/common --includedir=/yow-build62-lx2/bkuhl/work/VSB/usr/h/public    toolset=clang-vxworks cross-compile=vxworks --reconfigure target-os=vxworks "variant=debug" address-model=64  static-only=on  "testing.launcher=./vxworks_boost_test_run.exp" "--limit-tests=iostreams|system" "--exclude-tests=coroutine2|function_types|functional|logic|rational" -d2
> Performing configuration checks
>     - default address-model    : 64-bit
>     - default architecture     : x86
>     - default address-model    : 64-bit
>     - default architecture     : x86
>     - symlinks supported       : yes
>     - BOOST_COMP_GNUC >= 4.3.0 : no
>     - zlib                     : yes
>     - bzip2                    : yes
>     - lzma                     : no
> <snip>
>
>
> clang-vxworks.link ../bin.v2/libs/iostreams/test/bzip2_test.test/clang-vxworks-4.2.1/debug/cross-compile-vxworks/static-only-on/bzip2_test.vxe
>     /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/bzip2_test.test/clang-vxworks-4.2.1/debug/cross-compile-vxworks/static-only-on/bzip2_test.vxe" /yow-build62-lx2/bkuhl/work/VSB/usr/lib/common//crt0.o "../bin.v2/libs/iostreams/test/bzip2_test.test/clang-vxworks-4.2.1/debug/cross-compile-vxworks/static-only-on/bzip2_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-v
 xworks/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
> ../bin.v2/libs/iostreams/build/clang-vxworks-4.2.1/debug/cross-compile-vxworks/static-only-on/libboost_iostreams.a(bzip2.o): In function `boost::iostreams::detail::bzip2_base::end(bool)':
> /yow-build62-lx2/bkuhl/work/VSB/3pp/BOOST/boost_1_68_0/status/../libs/iostreams/src/bzip2.cpp:121: undefined reference to `BZ2_bzCompressEnd'
> <snip>

_______________________________________________
Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build
Reply | Threaded
Open this post in threaded view
|

Re: zlib and bipz2 not linking?

Boost - Build mailing list
Hi Steven,
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?
 
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
 
 
> -----Original Message-----
> From: Steven Watanabe [[hidden email]]
> Sent: Friday, September 07, 2018 10:50 AM
> To: Boost.Build developer's and user's list
> Cc: Kuhl, Brian; Krejsa, Dan
> Subject: Re: [Boost-build] zlib and bipz2 not linking?
>
> AMDG
>
> On 09/06/2018 09:43 PM, Kuhl, Brian via Boost-build wrote:
> > Hi Experts,
> > When cross compiling for VxWorks on Linux  ...
> > In previous versions of Boost the presence of libz.a and libbz2.a were detected
> and linked into iostreams tests.
> > But with v1.68 the libraries are not being added to the link line.
> > Please see below for an example error.
> >
> > The config-cache and the build console indicate that libz and bzip are being
> found, it's just not being used when required.
> >
> > I'm having trouble deciphering ac.jam, so I was hopping someone could help
> me understand  how a dependency on /zlib//zlib is supposed to add -lz to the link
> line?
> > And why it might not work in my case?
> >
>
>   What's supposed to happen is that ac-library.construct returns a target
> representing -lz.  When boost_iostreams is built as a static library, it propagates
> this target to its dependencies as a <library> usage requirement.
> I would recommend --debug-building and/or --debug-generators, but that just
> shows the dependency as <library>object(file-target)@NNN which is not really
> useful.
>
>   Okay, try building just one test target with `--debug-building --debug-
> generators -n -d0`.
> There are two things that you should be looking for in the output.  First of all,
> there should be two lines like this:
>
>          Usage requirements for boost_iostreams:  ...
>          Build properties:  ... <install-dependencies>off
> <library>object(file-target)@4855 ...
>
> If the <library> is missing, then that means that zlib is not being passed to the
> boost_iostreams target.
>
> The second line to look for is:
>          Usage requirements from boost_iostreams:  <include>.
> <library>object(file-target)@4855 <relevant>address-model ...
>
> If there is no library here, then that means the problem is in the propagation of
> static libraries.
>
> > Many thanks,
> >
> > Brian Kuhl
> > Wind River
> >
> >
> > . ./vxworks_env.sh &&  cd status   &&  \
> >                     BOOST_TELNET_ADDR="localhost 20023"  \
> >                     LAYER_SRC_PATH="yow-build62-
> lx:VSB/3pp/BOOST/boost_1_68_0" \
> >                     PKG_SRC_BUILD_DIR="/yow-build62-
> lx2/bkuhl/work/VSB/3pp/BOOST/boost_1_68_0"  \
> >                     VSB_LD_LIBRARY_PATH="yow-build62-
> lx:VSB/usr/root/llvm/bin;yow-build62-lx:VSB/usr/lib/common" \
> > ../b2 -j1 --prefix=/yow-build62-lx2/bkuhl/work/VSB/usr/root --libdir=/yow-
> build62-lx2/bkuhl/work/VSB/usr/lib/common --includedir=/yow-build62-
> lx2/bkuhl/work/VSB/usr/h/public    toolset=clang-vxworks cross-
> compile=vxworks --reconfigure target-os=vxworks "variant=debug" address-
> model=64  static-only=on  "testing.launcher=./vxworks_boost_test_run.exp" "--
> limit-tests=iostreams|system" "--exclude-
> tests=coroutine2|function_types|functional|logic|rational" -d2
> > Performing configuration checks
> >     - default address-model    : 64-bit
> >     - default architecture     : x86
> >     - default address-model    : 64-bit
> >     - default architecture     : x86
> >     - symlinks supported       : yes
> >     - BOOST_COMP_GNUC >= 4.3.0 : no
> >     - zlib                     : yes
> >     - bzip2                    : yes
> >     - lzma                     : no
> > <snip>
> >
> >
> > clang-vxworks.link ../bin.v2/libs/iostreams/test/bzip2_test.test/clang-
> vxworks-4.2.1/debug/cross-compile-vxworks/static-only-on/bzip2_test.vxe
> >     /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/bzip2_test.test/clang-vxworks-4.2.1/debug/cross-
> compile-vxworks/static-only-on/bzip2_test.vxe" /yow-build62-
> lx2/bkuhl/work/VSB/usr/lib/common//crt0.o
> "../bin.v2/libs/iostreams/test/bzip2_test.test/clang-vxworks-4.2.1/debug/cross-
> compile-vxworks/static-only-on/bzip2_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
> > ../bin.v2/libs/iostreams/build/clang-vxworks-4.2.1/debug/cross-compile-
> vxworks/static-only-on/libboost_iostreams.a(bzip2.o): In function
> `boost::iostreams::detail::bzip2_base::end(bool)':
> > /yow-build62-
> lx2/bkuhl/work/VSB/3pp/BOOST/boost_1_68_0/status/../libs/iostreams/src/bzi
> p2.cpp:121: undefined reference to `BZ2_bzCompressEnd'
> > <snip>
 
 

_______________________________________________
Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build
Reply | Threaded
Open this post in threaded view
|

Re: zlib and bipz2 not linking?

Boost - Build mailing list
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/cla
 ng-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
Reply | Threaded
Open this post in threaded view
|

Re: zlib and bipz2 not linking?

Boost - Build mailing list
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 [[hidden email]]
> 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
Reply | Threaded
Open this post in threaded view
|

Re: zlib and bipz2 not linking?

Boost - Build mailing list
AMDG

On 09/10/2018 11:47 AM, Kuhl, Brian wrote:
> Does this mean that the usage requirement are not being met, and therefore zlib is not being included?

I don't understand what you mean by "usage requirements are
not being met."

> 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?
>

  These properties are returned after processing
the zlib target and are applied to all targets
that depend on zlib.  <relevant> indicates that the
properties that you defined should be included
in the target paths.

> Brian
>
>> -----Original Message-----
>> From: Steven Watanabe [mailto:[hidden email]]
>> 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.
>>
>>> <snip>
>>>
>>> <snip>
>
>

_______________________________________________
Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build
Reply | Threaded
Open this post in threaded view
|

Re: zlib and bipz2 not linking?

Boost - Build mailing list
Hi Steven,
I backed out the link-with-ld generators and the libraries being added to the link line now.  However if I add
 project : requirements   <static-only>on:<link>static  
or
b2 link=static ...

The libraries are mangled
                    <l/link-static>z <l/link-static>bz2

Any ideas how I can correct this?

Thanks

Brian


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

> AMDG
>
> On 09/10/2018 11:47 AM, Kuhl, Brian wrote:
> > Does this mean that the usage requirement are not being met, and therefore
> zlib is not being included?
>
> I don't understand what you mean by "usage requirements are
> not being met."
>
> > 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?
> >
>
>   These properties are returned after processing
> the zlib target and are applied to all targets
> that depend on zlib.  <relevant> indicates that the
> properties that you defined should be included
> in the target paths.
>
> > Brian
> >
> >> -----Original Message-----
> >>
> >> 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.
> >>
> >>> <snip>
> >>>
> >>> <snip>
> >
> >

_______________________________________________
Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build
Reply | Threaded
Open this post in threaded view
|

Re: zlib and bipz2 not linking?

Boost - Build mailing list
AMDG

On 09/12/2018 03:07 PM, Kuhl, Brian wrote:

> Hi Steven,
> I backed out the link-with-ld generators and the libraries being added to the link line now.  However if I add
>  project : requirements   <static-only>on:<link>static  
> or
> b2 link=static ...
>
> The libraries are mangled
>                     <l/link-static>z <l/link-static>bz2
>
> Any ideas how I can correct this?
>

That looks like the internal Jam name.  It's
supposed to be fixed up by `bind LIBRARIES`

In Christ,
Steven Watanabe
_______________________________________________
Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build
Reply | Threaded
Open this post in threaded view
|

Re: zlib and bipz2 not linking?

Boost - Build mailing list
In reply to this post by Boost - Build mailing list
AMDG

On 09/12/2018 03:07 PM, Kuhl, Brian wrote:

> Hi Steven,
> I backed out the link-with-ld generators and the libraries being added to the link line now.  However if I add
>  project : requirements   <static-only>on:<link>static  
> or
> b2 link=static ...
>
> The libraries are mangled
>                     <l/link-static>z <l/link-static>bz2
>
> Any ideas how I can correct this?
>

After a bit of poking around, I think the most
likely cause is that the generator for the link rule either
a) is not derived from linking-generator, or
b) overrides linking-generator.generated-targets incorrectly.

In Christ,
Steven Watanabe
_______________________________________________
Unsubscribe & other changes: https://lists.boost.org/mailman/listinfo.cgi/boost-build