| View previous topic :: View next topic |
| Author |
Message |
nw_biohazard
Tux's lil' helper
Joined: 05 Aug 2008
Posts: 122
|
 Posted: Tue Jan 23, 2018 3:19 am Post subject: SOLVED kde-apps/rocs-17.08.3::gentoo failed (compile phase) |
 |
|
I upgraded to a new 17.0 profile ( [19] default/linux/amd64/17.0/desktop/plasma (stable) *) and successfully completed the following:
| Code: | ~ # gcc-config -c
x86_64-pc-linux-gnu-6.4.0
~# . /etc/profile
~# emerge -1 sys-devel/libtool
~# emerge -1 sys-devel/gcc:6.4.0
~# emerge -1 sys-devel/binutils
~# emerge -1 sys-libs/glibc
~# emerge -e @world |
I then did an @world update and got the following error: | Code: |
~# emerge --update --newuse --deep --backtrack=100 world
[ 97%] Built target gmlfileformat
make[1]: Leaving directory '/var/tmp/portage/kde-apps/rocs-17.08.3/work/rocs-17.08.3_build'
make: *** [Makefile:130: all] Error 2
* ERROR: kde-apps/rocs-17.08.3::gentoo failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=kde-apps/rocs-17.08.3::gentoo'`,
* the complete build log and the output of `emerge -pqv '=kde-apps/rocs-17.08.3::gentoo'`.
* The complete build log is located at '/var/tmp/portage/kde-apps/rocs-17.08.3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/kde-apps/rocs-17.08.3/temp/environment'.
* Working directory: '/var/tmp/portage/kde-apps/rocs-17.08.3/work/rocs-17.08.3_build'
* S: '/var/tmp/portage/kde-apps/rocs-17.08.3/work/rocs-17.08.3'
>>> Failed to emerge kde-apps/rocs-17.08.3, Log file:
>>> '/var/tmp/portage/kde-apps/rocs-17.08.3/temp/build.log' |
Output of | Code: | | emerge --info '=kde-apps/rocs-17.08.3::gentoo |
https://paste.pound-python.org/show/5BomII827MXd6TWAD5eQ/
Output of | Code: | emerge -pqv '=kde-apps/rocs-17.08.3::gentoo
[ebuild U ] kde-apps/rocs-17.08.3 [17.04.3] USE="handbook -debug {-test}" |
Build log: https://paste.pound-python.org/show/Ots9yL3NAjr4iiiTigus/
ebuild environment: https://paste.pound-python.org/show/QmZBtUrp5KvLtzMuKyvO/
Any clues as to how to get past this? Thanks in advance![/url]
Last edited by nw_biohazard on Wed Jan 24, 2018 3:34 am; edited 1 time in total |
|
| Back to top |
|
 |
krinn
Watchman
Joined: 02 May 2003
Posts: 7470
|
| Posted: Tue Jan 23, 2018 9:34 pm Post subject: |
|
|
| Code: | | /usr/lib64/libQt5WebKit.so.5.7.1: undefined reference to `leveldb::DestroyDB(std::string const&, leveldb::Options const&)' |
sorry, it mean rebuild it 
| Code: | | emerge -1 /usr/lib64/libQt5WebKit.so.5.7.1 |
|
|
| Back to top |
|
|
asturm
Developer
Joined: 05 Apr 2007
Posts: 8935
|
| Posted: Tue Jan 23, 2018 10:17 pm Post subject: |
|
|
| Probably a missing leveldb rebuild after switch go >= GCC-5. |
|
| Back to top |
|
|
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21621
|
| Posted: Wed Jan 24, 2018 3:10 am Post subject: |
|
|
I read this as a successful leveldb rebuild and a missed Qt rebuild. Here, a leveldb that was rebuilt post-gcc-5 has leveldb::DestroyDB(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, leveldb::Options const&). Note the ::__cxx11 in the parameter name.
As a test: | Code: | $ cat -n s.cpp
1 #include <string>
2
3 void f(const std::string &);
4 void g()
5 {
6 f("");
7 }
$ g++-4.9.4 -O2 -o /dev/null s.cpp
ccCdQaWR.o: In function `g()':
s.cpp:(.text+0x41): undefined reference to `f(std::string const&)'
$ g++-5.4.0 -O2 -o /dev/null s.cpp
ccd8orcd.o: In function `g()':
s.cpp:(.text+0x43): undefined reference to `f(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' |
This shows that code built with gcc-5 will ask for the more mangled name. Since qt5webkit asks for the less mangled name, it likely was never rebuilt with gcc-5. |
|
| Back to top |
|
|
nw_biohazard
Tux's lil' helper
Joined: 05 Aug 2008
Posts: 122
|
| Posted: Wed Jan 24, 2018 3:35 am Post subject: |
|
|
Doing
| Code: | | emerge -1 /usr/lib64/libQt5WebKit.so.5.7.1 |
Solved it.
Thanks! Much appreciated. |
|
| Back to top |
|
|
|
Portage & Programming
