| Summary: | app-emulation/wine-vanilla-2.0.3 not building due to missing language pl, no workaround by specifying USE="linguas_pl" | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Nico Baggus <mlspamcb> |
| Component: | Current packages | Assignee: | Wine Maintainers <wine> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | ulm |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
I understand the linguas need to go, but i do expect that the package would build then.... not fail to build. Not I do have a languages variable set to just "en en_US".. te prevent a lot of unneeded files on a constrainted system. Enabling another language is not exactly an option. This works:
L10N="en_US en_GB nl pl" emerge -1 wine-vanilla
Now the problem is How to specify this in a package.use, as obviously L10N use flags don't exist.?
[I] app-emulation/wine-vanilla
Available versions:
(2.0) 2.0-r1^t
(2.0.1) 2.0.1-r1^t
(2.0.2) 2.0.2-r1^t
(2.0.3) 2.0.3^t
(2.18) ~2.18-r2^t
(2.19) ~2.19-r1^t
(2.20) ~2.20^t
(9999) **9999^t
{+X +alsa capi cups custom-cflags dos +fontconfig +gecko gphoto2 gsm gstreamer +jpeg kerberos +lcms ldap +mono mp3 ncurses netapi nls odbc openal opencl +opengl osmesa oss pcap +perl +png prelink pulseaudio +realtime +run-exes samba scanner selinux +ssl test +threads +truetype udev +udisks v4l +xcomposite xinerama +xml ABI_MIPS="n32 n64 o32" ABI_PPC="32 64" ABI_S390="32 64" ABI_X86="(+)32 (+)64 x32" ELIBC="glibc" KERNEL="FreeBSD"}
Installed versions: 2.0.3(2.0.3)^t(20:48:39 14-01-18)(X alsa cups fontconfig gecko gphoto2 gsm gstreamer jpeg lcms ldap mono mp3 ncurses netapi nls odbc openal opengl osmesa pcap perl png pulseaudio realtime run-exes samba scanner ssl threads truetype udev udisks v4l xcomposite xinerama xml -capi -custom-cflags -dos -opencl -oss -prelink -selinux -test ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="32 64 -x32" ELIBC="glibc" KERNEL="-FreeBSD")
Homepage: https://www.winehq.org/
Description: Free implementation of Windows(tm) on Unix, without external patchsets
Oh i have no use-case for a pl language addition to the global L10N variable. and to need a random language for any package to install seems somewhat weird. (and could end up installing all languages anyway). Please attach the output of emerge --info. This looks like yet another dupe of 617864 (if not using a 64-bit only build of Wine, feel free to re-open). *** This bug has been marked as a duplicate of bug 617864 *** Oh, wow, my eyes really /are/ sleepy. From the initial comment: ABI_X86="64 -32 -x32" From comment 2: ABI_X86="32 64 -x32" That's probably why it started working. :] Ok thanks, i'll follow the other issue. Ok thanks, i'll follow the other issue. |
rebuild was done due to change of build flags of wine-vanilla: Error: /var/tmp/portage/app-emulation/wine-vanilla-2.0.3/temp/environment: line 3646: no match: /var/tmp/portage/app-emulation/wine-vanilla-2.0.3/image/usr/share/wine-vanilla-2.0.3/man/pl* As can be seen the previous build was done after adding the linguas_pl flag to the use file. Installed versions: 2.0.3(2.0.3)^t(17:27:38 08-12-17)(X alsa cups fontconfig gecko gphoto2 gsm gstreamer jpeg lcms ldap linguas_en linguas_en_US linguas_nl linguas_pl mono mp3 ncurses nls odbc openal opengl perl png pulseaudio realtime run-exes scanner ssl threads truetype udev udisks v4l xcomposite xinerama xml -capi -custom-cflags -dos -linguas_ar -linguas_bg -linguas_ca -linguas_cs -linguas_da -linguas_de -linguas_el -linguas_eo -linguas_es -linguas_fa -linguas_fi -linguas_fr -linguas_he -linguas_hi -linguas_hr -linguas_hu -linguas_it -linguas_ja -linguas_ko -linguas_lt -linguas_ml -linguas_nb_NO -linguas_or -linguas_pa -linguas_pt_BR -linguas_pt_PT -linguas_rm -linguas_ro -linguas_ru -linguas_sk -linguas_sl -linguas_sr_RS@cyrillic -linguas_sr_RS@latin -linguas_sv -linguas_te -linguas_th -linguas_tr -linguas_uk -linguas_wa -linguas_zh_CN -linguas_zh_TW -netapi -opencl -osmesa -oss -pcap -prelink -samba -selinux -test ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" ABI_X86="64 -32 -x32" ELIBC="glibc" KERNEL="-FreeBSD") Homepage: https://www.winehq.org/ Description: Free implementation of Windows(tm) on Unix, without external patchsets Tail from build log: make[1]: Leaving directory '/var/tmp/portage/app-emulation/wine-vanilla-2.0.3/work/wine-2.0.3-abi_x86_64.amd64/tools/wrc' /var/tmp/portage/app-emulation/wine-vanilla-2.0.3/work/wine-2.0.3/tools/install-sh -m 644 /var/tmp/portage/app-emulation/wine-vanilla-2.0.3/work/wine-2.0.3/loader/l_intl.nls /var/tmp/portage/app-emulation/wine-vanilla-2.0.3/image//usr/share/wine-vanilla-2.0.3/wine/l_intl.nls /var/tmp/portage/app-emulation/wine-vanilla-2.0.3/work/wine-2.0.3/tools/install-sh -m 644 /var/tmp/portage/app-emulation/wine-vanilla-2.0.3/work/wine-2.0.3/loader/wine.desktop /var/tmp/portage/app-emulation/wine-vanilla-2.0.3/image//usr/share/wine-vanilla-2.0.3/applications/wine.desktop * PT_PAX marking -psmr /var/tmp/portage/app-emulation/wine-vanilla-2.0.3/image/usr/lib/wine-vanilla-2.0.3/bin/wine64 with paxctl * PT_PAX marking -psmr /var/tmp/portage/app-emulation/wine-vanilla-2.0.3/image/usr/lib/wine-vanilla-2.0.3/bin/wine64 with scanelf * PT_PAX marking -psmr /var/tmp/portage/app-emulation/wine-vanilla-2.0.3/image/usr/lib/wine-vanilla-2.0.3/bin/wine64-preloader with paxctl * PT_PAX marking -psmr /var/tmp/portage/app-emulation/wine-vanilla-2.0.3/image/usr/lib/wine-vanilla-2.0.3/bin/wine64-preloader with scanelf * XATTR_PAX marking -psmre /var/tmp/portage/app-emulation/wine-vanilla-2.0.3/image/usr/lib/wine-vanilla-2.0.3/bin/wine64 with setfattr * XATTR_PAX marking -psmre /var/tmp/portage/app-emulation/wine-vanilla-2.0.3/image/usr/lib/wine-vanilla-2.0.3/bin/wine64-preloader with setfattr /var/tmp/portage/app-emulation/wine-vanilla-2.0.3/temp/environment: line 3646: no match: /var/tmp/portage/app-emulation/wine-vanilla-2.0.3/image/usr/share/wine-vanilla-2.0.3/man/pl* * The ebuild phase 'install' has exited unexpectedly. This type of * behavior is known to be triggered by things such as failed variable * assignments (bug #190128) or bad substitution errors (bug #200313). * Normally, before exiting, bash should have displayed an error message * above. If bash did not produce an error message above, it's possible * that the ebuild has called `exit` when it should have called `die` * instead. This behavior may also be triggered by a corrupt bash binary or * a hardware problem such as memory or cpu malfunction. If the problem is * not reproducible or it appears to occur randomly, then it is likely to * be triggered by a hardware problem. If you suspect a hardware problem * then you should try some basic hardware diagnostics such as memtest. * Please do not report this as a bug unless it is consistently * reproducible and you are sure that your bash binary and hardware are * functioning properly.