View previous topic :: View next topic |
Author |
Message |
MikeFly n00b
Joined: 01 Aug 2017 Posts: 5
|
Posted: Tue Aug 01, 2017 2:49 pm Post subject: [SOLVED] Cannot emerge wine |
|
|
Hello, I used wine-9999 for long time and now I cannot emerge it, cannot emerge wine-staging, pure wine, even not 9999 version.
Error in configure phase: Code: | checking for i686-pc-linux-gnu-strip... no
checking for strip... strip
checking for i686-pc-linux-gnu-ranlib... ranlib
checking whether ln -s works... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ldconfig... /bin/true
checking for msgfmt... msgfmt
/var/tmp/portage/app-emulation/wine-staging-2.12/work/wine-2.12/configure: line 7049: syntax error near unexpected token `newline'
/var/tmp/portage/app-emulation/wine-staging-2.12/work/wine-2.12/configure: line 7049: ` '''
!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/app-emulation/wine-staging-2.12/work/wine-2.12-abi_x86_32.x86/config.log
* ERROR: app-emulation/wine-staging-2.12::gentoo failed (configure phase):
* econf failed
*
* Call stack:
* ebuild.sh, line 115: Called src_configure
* environment, line 4512: Called multilib-minimal_src_configure
* environment, line 3502: Called multilib_foreach_abi 'multilib-minimal_abi_src_configure'
* environment, line 3716: Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
* environment, line 3432: Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
* environment, line 3430: Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_configure'
* environment, line 877: Called multilib-minimal_abi_src_configure
* environment, line 3496: Called multilib_src_configure
* environment, line 3939: Called econf '--prefix=/usr/lib/wine-staging-2.12' '--datarootdir=/usr/share/wine-staging-2.12' '--datadir=/usr/share/wine-staging-2.12' '--docdir=/usr/share/doc/wine-staging-2.12' '--includedir=/usr/include/wine-staging-2.12' '--libdir=/usr/lib32/wine-staging-2.12' '--libexecdir=/usr/libexec/wine-staging-2.12' '--localstatedir=/var/wine-staging-2.12' '--mandir=/usr/share/wine-staging-2.12/man' '--sysconfdir=/etc/wine' '--with-alsa' '--without-capi' '--with-cms' '--with-cups' '--with-curses' '--with-dbus' '--with-fontconfig' '--with-gnutls' '--enable-mshtml' '--without-gphoto' '--without-gsm' '--without-gstreamer' '--without-hal' '--with-jpeg' '--with-ldap' '--enable-mscoree' '--with-mpg123' '--without-netapi' '--with-gettext' '--with-openal' '--without-opencl' '--with-opengl' '--without-osmesa' '--without-oss' '--without-pcap' '--with-png' '--with-pulse' '--with-pthread' '--without-sane' '--disable-tests' '--with-freetype' '--with-udev' '--with-v4l' '--with-x' '--with-xcomposite' '--with-xinerama' '--with-xml' '--with-xslt' '--with-xattr' '--without-gtk3' '--with-va' '--disable-win64'
* phase-helpers.sh, line 665: Called __helpers_die 'econf failed'
* isolated-functions.sh, line 117: Called die
* The specific snippet of code:
* die "$@"
*
* If you need support, post the output of `emerge --info '=app-emulation/wine-staging-2.12::gentoo'`,
* the complete build log and the output of `emerge -pqv '=app-emulation/wine-staging-2.12::gentoo'`.
* The complete build log is located at '/var/tmp/portage/app-emulation/wine-staging-2.12/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/app-emulation/wine-staging-2.12/temp/environment'.
* Working directory: '/var/tmp/portage/app-emulation/wine-staging-2.12/work/wine-2.12-abi_x86_32.x86'
* S: '/var/tmp/portage/app-emulation/wine-staging-2.12/work/wine-2.12' | Thank you for suggestions.
[code] tags added for readability. — JRG
Last edited by MikeFly on Tue Aug 01, 2017 6:37 pm; edited 1 time in total |
|
Back to top |
|
|
John R. Graham Administrator
Joined: 08 Mar 2005 Posts: 10590 Location: Somewhere over Atlanta, Georgia
|
Posted: Tue Aug 01, 2017 3:41 pm Post subject: |
|
|
wine-9999 gets past the configure phase on my stable amd64 system. Emerge Output wrote: | !!! Please attach the following file when seeking support:
!!! /var/tmp/portage/app-emulation/wine-staging-2.12/work/wine-2.12-abi_x86_32.x86/config.log | Could you pastebin that log, please?
- John _________________ I can confirm that I have received between 0 and 499 National Security Letters. |
|
Back to top |
|
|
MikeFly n00b
Joined: 01 Aug 2017 Posts: 5
|
|
Back to top |
|
|
John R. Graham Administrator
Joined: 08 Mar 2005 Posts: 10590 Location: Somewhere over Atlanta, Georgia
|
Posted: Tue Aug 01, 2017 4:11 pm Post subject: |
|
|
configure is failing on a C++ test program. Could you post the output ofplease?
- John _________________ I can confirm that I have received between 0 and 499 National Security Letters. |
|
Back to top |
|
|
MikeFly n00b
Joined: 01 Aug 2017 Posts: 5
|
Posted: Tue Aug 01, 2017 4:30 pm Post subject: |
|
|
OK...
Code: |
[ebuild NS ~] sys-devel/gcc-6.3.0:6.3.0::gentoo [5.4.0-r3:5.4.0::gentoo] USE="cxx fortran (multilib) nls nptl openmp pch sanitize ssp vtv (-altivec) (-awt) -cilk -debug -doc (-fixed-point) (-gcj) -go -graphite (-hardened) (-jit) (-libssp) -mpx -objc -objc++ -objc-gc (-pie) -regression-test -vanilla" 0 KiB
|
but original gcc is gcc-5.4.0-r3, trying emerge 6.3.0 now... Thank you for support, I will send result, when compile of new gcc will be done. |
|
Back to top |
|
|
MikeFly n00b
Joined: 01 Aug 2017 Posts: 5
|
Posted: Tue Aug 01, 2017 5:22 pm Post subject: |
|
|
Hmmm... same error
Code: |
checking for ldconfig... /bin/true
checking for msgfmt... msgfmt
/var/tmp/portage/app-emulation/wine-staging-2.8/work/wine-2.8/configure: line 7022: syntax error near unexpected token `newline'
/var/tmp/portage/app-emulation/wine-staging-2.8/work/wine-2.8/configure: line 7022: ` '''
|
but different log, now it looks like test compilation is OK...
https://pastebin.com/xFe9BPz7
Any idea, please? |
|
Back to top |
|
|
MikeFly n00b
Joined: 01 Aug 2017 Posts: 5
|
Posted: Tue Aug 01, 2017 6:35 pm Post subject: |
|
|
OK, I found it!
Beauty of live ebuilds It was caused by autoconf-9999. Dont ask me how... it was try&fail.
Anyway, thank you for support and have a nice day. |
|
Back to top |
|
|
|