Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 692218 - dev-libs/boost should depend on xz-utils
Summary: dev-libs/boost should depend on xz-utils
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: David Seifert
URL:
Whiteboard:
Keywords:
Depends on: boost-1.71-stable
Blocks:
  Show dependency tree
 
Reported: 2019-08-15 13:00 UTC by tt_1
Modified: 2019-11-01 11:20 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tt_1 2019-08-15 13:00:31 UTC
I found this as I'm actually testing if another package depends on xz-utils, so I removed the xz-utils package. 

preserved libs function from portage catches the breakage: 

!!! existing preserved libs:
>>> package: app-arch/xz-utils-5.2.4-r2
 *  - /lib64/liblzma.so.5
 *  - /lib64/liblzma.so.5.2.4
 *      used by /usr/lib64/libarchive.so.13.3.3 (app-arch/libarchive-3.3.3)
 *      used by /usr/lib64/libboost_iostreams.so.1.65.0 (dev-libs/boost-1.65.0)
 *      used by /usr/lib64/python3.6/lib-dynload/_lzma.cpython-36m-x86_64-linux-gnu.so (dev-lang/python-3.6.5)

But it is possible to emerge boost itself without xz-utils getting pulled in, and also without boost throwing out an error during it's own configure. 


here is the output from boost with xz-utils available: 

ldd /usr/lib64/libboost_iostreams.so.1.65.0 
	linux-vdso.so.1 (0x00007ffd77d3e000)
	libz.so.1 => /lib64/libz.so.1 (0x00007f0eaeb14000)
	libbz2.so.1 => /lib64/libbz2.so.1 (0x00007f0eaeaff000)
	liblzma.so.5 => /lib64/liblzma.so.5 (0x00007f0eaead6000)
	librt.so.1 => /lib64/librt.so.1 (0x00007f0eaeacc000)
	libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/libstdc++.so.6 (0x00007f0eae84f000)
	libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/libgcc_s.so.1 (0x00007f0eae835000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f0eae810000)
	libc.so.6 => /lib64/libc.so.6 (0x00007f0eae63b000)
	libm.so.6 => /lib64/libm.so.6 (0x00007f0eae4fa000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f0eaeb67000)


and here's without it: 

ldd /var/tmp/portage/dev-libs/boost-1.65.0/image/usr/lib64/libboost_iostreams.so.1.65.0 
	linux-vdso.so.1 (0x00007fff9b964000)
	libz.so.1 => /lib64/libz.so.1 (0x00007fdc99437000)
	libbz2.so.1 => /lib64/libbz2.so.1 (0x00007fdc99422000)
	librt.so.1 => /lib64/librt.so.1 (0x00007fdc99418000)
	libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/libstdc++.so.6 (0x00007fdc9919b000)
	libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/libgcc_s.so.1 (0x00007fdc99181000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fdc9915e000)
	libc.so.6 => /lib64/libc.so.6 (0x00007fdc98f87000)
	libm.so.6 => /lib64/libm.so.6 (0x00007fdc98e46000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fdc99486000)

I know that one must not ever remove xz-utils, but I felt silly today :-) 

In any case, dev-libs/boost should depend on xz-utils, mostly to prevent accidents in the future.
Comment 1 David Seifert gentoo-dev 2019-08-20 08:56:08 UTC
This is fixed in 1.70 and won't be backported to 1.65
Comment 2 tt_1 2019-08-20 09:56:56 UTC
that's correct, making it depend on boost-1.70.0 stabilization then
Comment 3 tt_1 2019-11-01 11:20:33 UTC
fixed by stable boost-1.71.0