Re: boost-libs

[Jason Bacon <bacon4000%gmail.com@localhost>]

On 12/24/17 09:15, Jason Bacon wrote:
> FYI:
>
> boost-libs is failing on CentOS 6 & 7 with the following error:
>
> => Automatic manual page handling
> => Generating post-install file lists
> pkg_create: can't stat 
> `/usr/pkgsrc/devel/boost-libs/work/.destdir/usr/pkg/lib/libboost_stacktrace_backtrace.a'
> pkg_create: can't stat 
> `/usr/pkgsrc/devel/boost-libs/work/.destdir/usr/pkg/lib/libboost_stacktrace_backtrace.so'
> pkg_create: can't stat 
> `/usr/pkgsrc/devel/boost-libs/work/.destdir/usr/pkg/lib/libboost_stacktrace_backtrace.so.1.65.1'
> => Checking file-check results for boost-libs-1.65.1nb3
> ERROR: ************************************************************
> ERROR: The following files are in the PLIST but not in 
> /usr/pkgsrc/devel/boost-libs/work/.destdir/usr/pkg:
> ERROR: 
> /usr/pkgsrc/devel/boost-libs/work/.destdir/usr/pkg/lib/libboost_stacktrace_backtrace.a
> ERROR: 
> /usr/pkgsrc/devel/boost-libs/work/.destdir/usr/pkg/lib/libboost_stacktrace_backtrace.so
> ERROR: 
> /usr/pkgsrc/devel/boost-libs/work/.destdir/usr/pkg/lib/libboost_stacktrace_backtrace.so.1.65.1
> *** Error code 1
>
> Stop.
> bmake.bin[3]: stopped in /usr/pkgsrc/devel/boost-libs
> *** Error code 1
>
> I'll look into it after the holiday if a patch doesn't magically 
> appear before then.
I think the problem is that neither CentOS 6 nor 7 have libbacktrace.  
The boost-libs configure output shows this:

    - gcc visibility           : yes
    - long double support      : yes
warning: skipping optional Message Passing Interface (MPI) library.
note: to enable MPI support, add "using mpi ;" to user-config.jam.
note: to suppress this message, pass "--without-mpi" to bjam.
note: otherwise, you can safely ignore this message.
    - libbacktrace builds      : no
    - addr2line builds         : yes
    - WinDbg builds            : no

Perhaps we should just mask off these entries in PLIST.Linux on systems 
that don't have libbacktrace?

--
Earth is a beta site.