Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 643388 - net-wireless/bluez-5.47-r1 fails to build with profile 17.1
Summary: net-wireless/bluez-5.47-r1 fails to build with profile 17.1
Status: RESOLVED DUPLICATE of bug 599244
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal with 1 vote (vote)
Assignee: Pacho Ramos
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-04 10:54 UTC by Ingo Brunberg
Modified: 2018-01-08 19:20 UTC (History)
3 users (show)

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


Attachments
build.log (wrong file format) (build.log,151.39 KB, text/x-log)
2018-01-06 17:06 UTC, Till Schäfer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ingo Brunberg 2018-01-04 10:54:57 UTC
The build expects to find libicu in /usr/lib instead of /usr/lib64.

libtool: link: x86_64-pc-linux-gnu-gcc -fPIC -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -DOBEX_PLUGIN_BUILTIN -DPLUGINDIR=\"/usr/lib64/obex/plugins\" -fPIC -D_FILE_OFFSET_BITS=64 -march=native -O2 -pipe -fno-stack-protector -Wl,--export-dynamic -Wl,-O1 -o obexd/src/obexd btio/obexd-btio.o gobex/obexd-gobex.o gobex/obexd-gobex-defs.o gobex/obexd-gobex-packet.o gobex/obexd-gobex-header.o gobex/obexd-gobex-transfer.o gobex/obexd-gobex-apparam.o obexd/plugins/obexd-filesystem.o obexd/plugins/obexd-bluetooth.o obexd/plugins/obexd-opp.o obexd/plugins/obexd-ftp.o obexd/plugins/obexd-irmc.o obexd/plugins/obexd-pbap.o obexd/plugins/obexd-vcard.o obexd/plugins/obexd-phonebook-dummy.o obexd/plugins/obexd-mas.o obexd/plugins/obexd-messages-dummy.o obexd/client/obexd-mns.o obexd/src/obexd-main.o obexd/src/obexd-plugin.o obexd/src/obexd-log.o obexd/src/obexd-manager.o obexd/src/obexd-obex.o obexd/src/obexd-mimetype.o obexd/src/obexd-service.o obexd/src/obexd-transport.o obexd/src/obexd-server.o obexd/client/obexd-manager.o obexd/client/obexd-session.o obexd/client/obexd-bluetooth.o obexd/client/obexd-sync.o obexd/client/obexd-pbap.o obexd/client/obexd-ftp.o obexd/client/obexd-opp.o obexd/client/obexd-map.o obexd/client/obexd-map-event.o obexd/client/obexd-transfer.o obexd/client/obexd-transport.o obexd/client/obexd-dbus.o obexd/client/obexd-driver.o /usr/lib/libicuuc.so /usr/lib/libicui18n.so -pthread  -Wl,--as-needed lib/.libs/libbluetooth-internal.a gdbus/.libs/libgdbus-internal.a -lical -licalss -licalvcal -lpthread -ldbus-1 -lgthread-2.0 -lglib-2.0 -ldl -pthread
x86_64-pc-linux-gnu-gcc: error: /usr/lib/libicuuc.so: No such file or directory
x86_64-pc-linux-gnu-gcc: error: /usr/lib/libicui18n.so: No such file or directory
make[1]: *** [Makefile:4267: obexd/src/obexd] Fehler 1
Comment 1 Alexander Tsoy 2018-01-05 07:40:09 UTC
Possible duplicate of bug 599244
Plese make sure that libical is updated.
Comment 2 Anton Kuleshov 2018-01-05 09:02:24 UTC
Yes, it is, thanks. Upgrade libical to -r3 solved this issue.
Comment 3 Ingo Brunberg 2018-01-05 09:54:42 UTC
Confirmed! After upgrading libical bluez builds successfully.
Comment 4 Till Schäfer 2018-01-06 17:05:42 UTC
I had similar issue (wrong format instead of missing / see below). For me a simple rebuild of libical helped (no need for -r3). 

libical did not popped up during update or during the profile 17.1 migration with "emerge /lib32 /usr/lib32". So somehow this package also needs a rebuild but is not recognized by the migration behaviour. 

 

libtool: link: x86_64-pc-linux-gnu-gcc -fPIC -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -DOBEX_PLUGIN_BUILTIN -DPLUGINDIR=\"/usr/lib64/obex/plugins\" -fPIC -D_FILE_OFFSET_BITS=64 -march=native -O2 -pipe -ggdb -Wl,--export-dynamic -Wl,-O1 -o obexd/src/obexd btio/obexd-btio.o gobex/obexd-gobex.o gobex/obexd-gobex-defs.o gobex/obexd-gobex-packet.o gobex/obexd-gobex-header.o gobex/obexd-gobex-transfer.o gobex/obexd-gobex-apparam.o obexd/plugins/obexd-filesystem.o obexd/plugins/obexd-bluetooth.o obexd/plugins/obexd-opp.o obexd/plugins/obexd-ftp.o obexd/plugins/obexd-irmc.o obexd/plugins/obexd-pbap.o obexd/plugins/obexd-vcard.o obexd/plugins/obexd-phonebook-dummy.o obexd/plugins/obexd-mas.o obexd/plugins/obexd-messages-dummy.o obexd/client/obexd-mns.o obexd/src/obexd-main.o obexd/src/obexd-plugin.o obexd/src/obexd-log.o obexd/src/obexd-manager.o obexd/src/obexd-obex.o obexd/src/obexd-mimetype.o obexd/src/obexd-service.o obexd/src/obexd-transport.o obexd/src/obexd-server.o obexd/client/obexd-manager.o obexd/client/obexd-session.o obexd/client/obexd-bluetooth.o obexd/client/obexd-sync.o obexd/client/obexd-pbap.o obexd/client/obexd-ftp.o obexd/client/obexd-opp.o obexd/client/obexd-map.o obexd/client/obexd-map-event.o obexd/client/obexd-transfer.o obexd/client/obexd-transport.o obexd/client/obexd-dbus.o obexd/client/obexd-driver.o /usr/lib/libicuuc.so /usr/lib/libicui18n.so -pthread  -Wl,--as-needed lib/.libs/libbluetooth-internal.a gdbus/.libs/libgdbus-internal.a -lical -licalss -licalvcal -lpthread -ldbus-1 -lgthread-2.0 -lglib-2.0 -ldl -pthread
/usr/lib/libicuuc.so: error adding symbols: File in wrong forma
Comment 5 Till Schäfer 2018-01-06 17:06:25 UTC
Created attachment 513534 [details]
build.log (wrong file format)
Comment 6 Bob Johnson 2018-01-07 18:22:33 UTC
Same here on stable amd64. Simply rebuilding stable dev-libs/libical-2.0.0-r2 allows net-wireless/bluez-5.47-r1 to rebuild successfully.
Comment 7 Jonas Stein gentoo-dev 2018-01-08 14:45:11 UTC
is there anything left we can do in the ebuild, or should we close here?
Comment 8 Alexander Tsoy 2018-01-08 15:18:49 UTC
(In reply to Jonas Stein from comment #7)
> is there anything left we can do in the ebuild, or should we close here?

We can stabilize dev-libs/libical-2.0.0-r3 to ensure that stable users don't need to rebuild libical after switching to 17.1 profile. On the other hand 17.1 profiles are experimental and not meant for stable users. :)
Comment 9 Pacho Ramos gentoo-dev 2018-01-08 19:17:37 UTC
Yeah, I would open a bug for stabilizing new libical before profiles 17.1 are widely used

*** This bug has been marked as a duplicate of bug 599244 ***
Comment 10 Pacho Ramos gentoo-dev 2018-01-08 19:20:06 UTC
I have opened bug 643940 for libical stabilization