[gentoo-user] Big Fat Yellow Warning when emerging/unmerging wine-vanilla.
Does someone know why I get these when emerging or unmerging wine-vanilla (as part of a @world upgrade followed by a depclean): >>> Unmerging (1 of 1) app-emulation/wine-vanilla-4.1... !!! Warning: Skipping wine-staging. No registered targets found. !!! Warning: Skipping wine-d3d9. No registered targets found. !!! Warning: Skipping wine-any. No registered targets found. Something that starts with "!!!" and is printed in bright, yellow letters seems very, very severe. Is something broken?
Re: [gentoo-user] Re: Flashing hardware via WINE ?
On 03/19 11:20, Kai Krakow wrote: > Am Sun, 19 Mar 2017 09:57:22 +0100 > schrieb tu...@posteo.de: > > > On 03/19 09:37, Kai Krakow wrote: > > > Am Sun, 19 Mar 2017 09:09:51 +0100 > > > schrieb tu...@posteo.de: > > > > > > > Hi, > > > > > > > > I have a smart NiMH-charger with serial port (normally used to > > > > dump chargeing curves to the PC). > > > > The chargers firmware can bei flashed with a flashtool provided > > > > by the vendor. The communication is via serial port. I have > > > > a PCI=>serial.ports-card installed in my PC. > > > > > > > > The command > > > > > > > > file > > > > > > > > results in this information > > > > > > > > PE32 executable (GUI) Intel 80386, for MS Windows > > > > > > > > . As Linux user by heart I have no Windows. > > > > > > > > May the attempt to install wine and use it for this purpose > > > > a thinkable way or are the precoditions that way, that it > > > > is due to those a NO-NO...? > > > > > > Flashing via serial port should be no problem from within Wine. It > > > requires no special driver implementation. > > > > > > However, if the hardware implements its own driver behind the serial > > > port, it won't work anyways because on the Wine side there will be > > > no such driver. > > > > > > So I think, it should either work or fail early without doing > > > damage. > > > > > > > > > > Does anyone have experience with such an attempt? > > > > > > I'm usually doing such things from VirtualBox by passing through the > > > hardware (usually USB, that's easily done from within the GUI). > > > > > > VirtualBox can also pass COM ports to the VM. You may want to try > > > that as a second chance. > > > > > > > > > -- > > > Regards, > > > Kai > > > > > > Replies to list-only preferred. > > > > Hi Kai (that's a rhyme! :) > > Yeah, I know that one... If you are from Germany, you'll also get why > my former nick (some years ago) was "Shark" :-) > > > I have installed Virtualbox already and use the Linux Image I > > installed there for banking purposes only. Feels more secure. > > So something like application virtualization... You could maybe run in > an isolated container, only exposing the xserver or run inside a nested > xserver. It would probably greatly reduce startup times and not waste a > complete image. > > > I would prefer the WIndows-in-a-(virtual)box-solution) as you > > do -- if I would own a Windows installation disc. But do not. > > Well, you can easily get an image from MS using a Linux browser. Just > go to the Windows 10 download page. It will show a selection form to > choose the ISO instead of the nasty downloader they present to Windows > browsers. Then install this inside the VM. Even if not activated, it > runs for 1-2 hours before shutting down which should be enough for most > purposes you'll need it for. > > If you already activated a Windows installation with your MS account, > with some luck your Win10 VM may even become digitally activated (this > happened to me). No cracks involved. Should be legal enough. ;-) > > > But it is good to know, that the wine-workaround would either > > work or fail too early to damage anything. > > I tried some, and all failed because they didn't even find the device. > The ones that worked where either network based (flashing via IP > protocol) or using other simple interfaces (COM or LPT). > > > Is there anything important to know before doing an emerge > > of wine (need I more than app-emulation/wine?) -- I have > > literally no experience with this emulator - the flashing > > tool is a 32bit gui application...) ??? > > Wine = wine is no emulater ;-) > > Actually, it's the Windows API implemented as .so files plus an EXE > loader to enable the kernel to run PE binaries (instead of ELF). So > nothing is emulated, it's running native. There's also a thin layer of > drivers implemented to transform API calls to native kernel interfaces, > like HID (for input devices). So everything connecting to simple > HID-USB should also work (some custom USB hardware just implement a HID > interface, it's simple and cheap). > > If your applications work depends on if the required parts of the API > had been implemented (including the bugs that exist
[gentoo-user] wine cpu usage
hello everyone. To run a windows application I installed the wine package. But cpu usage of wine it a little high. using virtualbox is a lot smoother(9% = 3% cpu usage) . Is it normal? my wine config: [I] app-emulation/wine Available versions: 1.6.2^t (~)1.7.0^t (~)1.7.3^t (~)1.7.4^t (~)1.7.8^t (~)1.7.9^t (~)1.7.10^t (~)1.7.11^t (~)1.7.12^t (~)1.7.13^t (~)1.7.14^t (~)1.7.15^t (~)1.7.16^t (~)1.7.17^t (~)1.7.18^t (~)1.7.19-r1^t (~)1.7.20^t (~)1.7.21^t (~)1.7.22^t (~)1.7.28^t (~)1.7.29^t (~)1.7.33^t (~)1.7.38^t (~)1.7.39^t (~)1.7.40^t (~)1.7.41^t (~)1.7.42^t (~)1.7.43^t **^t {+X +alsa capi cups custom-cflags dos +fontconfig +gecko gphoto2 gsm gstreamer +jpeg (+)lcms ldap +mono mp3 ncurses netapi nls odbc openal opencl +opengl osmesa oss pcap +perl pipelight +png +prelink pulseaudio +realtime +run-exes s3tc samba scanner selinux +ssl staging test +threads +truetype +udisks v4l vaapi (+)xcomposite xinerama +xml ABI_MIPS=n32 n64 o32 ABI_PPC=32 64 ABI_S390=32 64 ABI_X86=(+)32 (+)64 x32 ELIBC=glibc LINGUAS=ar bg ca cs da de el en en_US eo es fa fi fr he hi hr hu it ja ko lt ml nb_NO nl or pa pl pt_BR pt_PT rm ro ru sk sl sr_RS@cyrillic sr_RS@latin sv te th tr uk wa zh_CN zh_TW} Installed versions: 1.7.43^t(12:50:01 AM 05/28/2015)(X alsa fontconfig gecko jpeg lcms ldap mono mp3 ncurses nls opengl perl png prelink realtime run-exes ssl threads truetype udisks xcomposite xml -capi -cups -custom-cflags -dos -gphoto2 -gsm -gstreamer -netapi -odbc -openal -opencl -osmesa -oss -pcap -pipelight -pulseaudio -s3tc -samba -scanner -selinux -staging -test -v4l -vaapi -xinerama ABI_MIPS=-n32 -n64 -o32 ABI_PPC=-32 -64 ABI_S390=-32 -64 ABI_X86=32 64 -x32 ELIBC=glibc LINGUAS=-ar -bg -ca -cs -da -de -el -en -en_US -eo -es -fa -fi -fr -he -hi -hr -hu -it -ja -ko -lt -ml -nb_NO -nl -or -pa -pl -pt_BR -pt_PT -rm -ro -ru -sk -sl -sr_RS@cyrillic -sr_RS@latin -sv -te -th -tr -uk -wa -zh_CN -zh_TW) thanks
[gentoo-user] Re: Flashing hardware via WINE ?
Am Sun, 19 Mar 2017 09:57:22 +0100 schrieb tu...@posteo.de: > On 03/19 09:37, Kai Krakow wrote: > > Am Sun, 19 Mar 2017 09:09:51 +0100 > > schrieb tu...@posteo.de: > > > > > Hi, > > > > > > I have a smart NiMH-charger with serial port (normally used to > > > dump chargeing curves to the PC). > > > The chargers firmware can bei flashed with a flashtool provided > > > by the vendor. The communication is via serial port. I have > > > a PCI=>serial.ports-card installed in my PC. > > > > > > The command > > > > > > file > > > > > > results in this information > > > > > > PE32 executable (GUI) Intel 80386, for MS Windows > > > > > > . As Linux user by heart I have no Windows. > > > > > > May the attempt to install wine and use it for this purpose > > > a thinkable way or are the precoditions that way, that it > > > is due to those a NO-NO...? > > > > Flashing via serial port should be no problem from within Wine. It > > requires no special driver implementation. > > > > However, if the hardware implements its own driver behind the serial > > port, it won't work anyways because on the Wine side there will be > > no such driver. > > > > So I think, it should either work or fail early without doing > > damage. > > > > > > > Does anyone have experience with such an attempt? > > > > I'm usually doing such things from VirtualBox by passing through the > > hardware (usually USB, that's easily done from within the GUI). > > > > VirtualBox can also pass COM ports to the VM. You may want to try > > that as a second chance. > > > > > > -- > > Regards, > > Kai > > > > Replies to list-only preferred. > > Hi Kai (that's a rhyme! :) Yeah, I know that one... If you are from Germany, you'll also get why my former nick (some years ago) was "Shark" :-) > I have installed Virtualbox already and use the Linux Image I > installed there for banking purposes only. Feels more secure. So something like application virtualization... You could maybe run in an isolated container, only exposing the xserver or run inside a nested xserver. It would probably greatly reduce startup times and not waste a complete image. > I would prefer the WIndows-in-a-(virtual)box-solution) as you > do -- if I would own a Windows installation disc. But do not. Well, you can easily get an image from MS using a Linux browser. Just go to the Windows 10 download page. It will show a selection form to choose the ISO instead of the nasty downloader they present to Windows browsers. Then install this inside the VM. Even if not activated, it runs for 1-2 hours before shutting down which should be enough for most purposes you'll need it for. If you already activated a Windows installation with your MS account, with some luck your Win10 VM may even become digitally activated (this happened to me). No cracks involved. Should be legal enough. ;-) > But it is good to know, that the wine-workaround would either > work or fail too early to damage anything. I tried some, and all failed because they didn't even find the device. The ones that worked where either network based (flashing via IP protocol) or using other simple interfaces (COM or LPT). > Is there anything important to know before doing an emerge > of wine (need I more than app-emulation/wine?) -- I have > literally no experience with this emulator - the flashing > tool is a 32bit gui application...) ??? Wine = wine is no emulater ;-) Actually, it's the Windows API implemented as .so files plus an EXE loader to enable the kernel to run PE binaries (instead of ELF). So nothing is emulated, it's running native. There's also a thin layer of drivers implemented to transform API calls to native kernel interfaces, like HID (for input devices). So everything connecting to simple HID-USB should also work (some custom USB hardware just implement a HID interface, it's simple and cheap). If your applications work depends on if the required parts of the API had been implemented (including the bugs that exists between different versions of Windows). So, with this knowledge, you simply emerge wine with the useflags that look useful to you. If you don't need graphics (DirectX) or don't want to apply your linux GUI theme to Windows apps, you can ignore the staging useflag. Wine can be compiled with both 64bit and 32bit support. After installation, get familiar with the winecfg utility. It allows mapping unix path to Windows drive letters. And it allows to set Windows version per EXE you run (to expose different API bugs and behavior to your application). Also,
[gentoo-user] Re: Flashing hardware via WINE ?
Am Sun, 19 Mar 2017 11:35:44 +0100 schrieb tu...@posteo.de: > On 03/19 11:20, Kai Krakow wrote: > > Am Sun, 19 Mar 2017 09:57:22 +0100 > > schrieb tu...@posteo.de: > > > > > On 03/19 09:37, Kai Krakow wrote: > [...] > [...] > [...] > [...] > [...] > > > > > > Hi Kai (that's a rhyme! :) > > > > Yeah, I know that one... If you are from Germany, you'll also get > > why my former nick (some years ago) was "Shark" :-) > > > > > I have installed Virtualbox already and use the Linux Image I > > > installed there for banking purposes only. Feels more secure. > > > > So something like application virtualization... You could maybe run > > in an isolated container, only exposing the xserver or run inside a > > nested xserver. It would probably greatly reduce startup times and > > not waste a complete image. > > > > > I would prefer the WIndows-in-a-(virtual)box-solution) as you > > > do -- if I would own a Windows installation disc. But do not. > > > > Well, you can easily get an image from MS using a Linux browser. > > Just go to the Windows 10 download page. It will show a selection > > form to choose the ISO instead of the nasty downloader they present > > to Windows browsers. Then install this inside the VM. Even if not > > activated, it runs for 1-2 hours before shutting down which should > > be enough for most purposes you'll need it for. > > > > If you already activated a Windows installation with your MS > > account, with some luck your Win10 VM may even become digitally > > activated (this happened to me). No cracks involved. Should be > > legal enough. ;-) > > > But it is good to know, that the wine-workaround would either > > > work or fail too early to damage anything. > > > > I tried some, and all failed because they didn't even find the > > device. The ones that worked where either network based (flashing > > via IP protocol) or using other simple interfaces (COM or LPT). > > > > > Is there anything important to know before doing an emerge > > > of wine (need I more than app-emulation/wine?) -- I have > > > literally no experience with this emulator - the flashing > > > tool is a 32bit gui application...) ??? > > > > Wine = wine is no emulater ;-) > > > > Actually, it's the Windows API implemented as .so files plus an EXE > > loader to enable the kernel to run PE binaries (instead of ELF). So > > nothing is emulated, it's running native. There's also a thin layer > > of drivers implemented to transform API calls to native kernel > > interfaces, like HID (for input devices). So everything connecting > > to simple HID-USB should also work (some custom USB hardware just > > implement a HID interface, it's simple and cheap). > > > > If your applications work depends on if the required parts of the > > API had been implemented (including the bugs that exists between > > different versions of Windows). > > > > So, with this knowledge, you simply emerge wine with the useflags > > that look useful to you. If you don't need graphics (DirectX) or > > don't want to apply your linux GUI theme to Windows apps, you can > > ignore the staging useflag. Wine can be compiled with both 64bit > > and 32bit support. > > > > After installation, get familiar with the winecfg utility. It allows > > mapping unix path to Windows drive letters. And it allows to set > > Windows version per EXE you run (to expose different API bugs and > > behavior to your application). Also, you can set DDL overrides > > (which is what Windows itself uses when you run applications in > > compatibility mode, or when you put DLL overrides manually in the > > registry). Tho, here you can decide between native (native DLL on > > filesystem) or builtin (*.dll.so file from Wine), and the order in > > which they are tried. > > > > You may also run with different WINEDEBUG settings if you want to > > work out problems. There are fixme lines which usually show stub > > implementations of API calls (functions that do nothing, and are > > there just to return success or fail). You can use it like this: > > > > # WINEDEBUG=-all wine your-exe-file.exe > > > > If you'd like to easily manage different Wine prefixes, I'd > > recommend using PlayOnLinux - it's not only useful to games. It > > also has a long list of scripted installers for installing popular > > Windows extensions that you may need (fonts, VB runtimes, C > > runtimes) in
Re: [gentoo-user] Re: Konsole
quot; LINGUAS="(-de%) (-ja%) (-ko%) (-zh_CN%) (-zh_TW%)" 0 KiB [ebuild NS] dev-qt/designer-5.5.1-r1:5::gentoo [4.8.6-r1:4::gentoo] USE="declarative -debug {-test} -webkit" 0 KiB [ebuild N#] kde-frameworks/kxmlgui-5.21.0:5/5.21::gentoo USE="-attica -debug {-test}" 848 KiB [ebuild N#] kde-frameworks/kbookmarks-5.21.0:5/5.21::gentoo USE="nls -debug {-test}" 113 KiB [ebuild R] kde-misc/kde-gtk-config-2.2.1:4::gentoo USE="(-aqua) -debug" L10N="-bs% -ca% -ca-valencia% -cs% -da% -de% -el% -es% -et% -eu% -fi% -fr% -ga% -gl% -hu% -id% -it% -ja% -kk% -km% -lt% -mr% -nb% -nds% -nl% -pl% -pt% -pt-BR% -ro% -ru% -sk% -sl% -sv% -uk% -zh-CN% -zh-TW%" LINGUAS="(-bs%) (-ca%) (-ca@valencia%) (-cs%) (-da%) (-de%) (-el%) (-es%) (-et%) (-eu%) (-fi%) (-fr%) (-ga%) (-gl%) (-hu%) (-id%) (-it%) (-ja%) (-kk%) (-km%) (-lt%) (-mr%) (-nb%) (-nds%) (-nl%) (-pl%) (-pt%) (-pt_BR%) (-ro%) (-ru%) (-sk%) (-sl%) (-sv%) (-uk%) (-zh_CN%) (-zh_TW%)" 0 KiB [ebuild R] media-libs/phonon-4.7.2::gentoo USE="designer gstreamer pulseaudio qt4 qt5* (-aqua) -debug -vlc (-zeitgeist)" 0 KiB [ebuild R] media-libs/phonon-gstreamer-4.7.2::gentoo USE="alsa network qt4 qt5* -debug" 0 KiB [ebuild N#] kde-frameworks/knotifications-5.21.0:5/5.21::gentoo USE="X dbus nls -debug (-speech)" 94 KiB [ebuild N#] kde-plasma/polkit-kde-agent-5.5.5:5::gentoo USE="-debug" 0 KiB [ebuild R] sys-auth/polkit-kde-agent-0.99.1-r1:4::gentoo USE="(-aqua) -debug -minimal" L10N="-ar% -bs% -ca% -ca-valencia% -cs% -da% -de% -el% -en-GB% -eo% -es% -et% -fi% -fr% -ga% -gl% -hr% -hu% -is% -it% -ja% -kk% -km% -lt% -mai% -mr% -ms% -nb% -nds% -nl% -pa% -pl% -pt% -pt-BR% -ro% -ru% -sk% -sl% -sr% -sr-Latn% -sr-Latn-ijekavsk% -sr-ijekavsk% -sv% -th% -tr% -ug% -uk% -vi% -zh-CN% -zh-TW%" LINGUAS="(-ar%) (-bs%) (-ca%) (-ca@valencia%) (-cs%) (-da%) (-de%) (-el%) (-en_GB%) (-eo%) (-es%) (-et%) (-fi%) (-fr%) (-ga%) (-gl%) (-hr%) (-hu%) (-is%) (-it%) (-ja%) (-kk%) (-km%) (-lt%) (-mai%) (-mr%) (-ms%) (-nb%) (-nds%) (-nl%) (-pa%) (-pl%) (-pt%) (-pt_BR%) (-ro%) (-ru%) (-sk%) (-sl%) (-sr%) (-sr@ijekavian%) (-sr@ijekavianlatin%) (-sr@latin%) (-sv%) (-th%) (-tr%) (-ug%) (-uk%) (-vi%) (-zh_CN%) (-zh_TW%)" 0 KiB [ebuild N#] kde-frameworks/kwallet-5.21.0:5/5.21::gentoo USE="man -debug -gpg {-test}" 282 KiB [ebuild U ] app-emulation/wine-1.8.2::gentoo [1.6.2::gentoo] USE="X alsa cups fontconfig gecko gphoto2 jpeg lcms mono mp3 ncurses nls opengl perl png pulseaudio realtime run-exes scanner ssl staging%* threads truetype udisks vaapi%* xcomposite xinerama xml -capi -custom-cflags -dos -gsm -gstreamer -ldap -netapi% -odbc -openal -opencl -osmesa -oss -pcap% -pipelight% -prelink* -s3tc% -samba (-selinux) {-test} -v4l" ABI_X86="32 64 (-x32)" LINGUAS="en -ar -bg -ca -cs -da -de -el -en_US -eo -es -fa -fi -fr -he -hi -hr -hu -it -ja -ko -lt -ml -nb_NO -nl -or -pa -pl -pt_BR -pt_PT -rm -ro -ru -sk -sl -sr_RS@cyrillic -sr_RS@latin -sv -te -th -tr -uk -wa -zh_CN -zh_TW" 147,531 KiB [ebuild R] media-gfx/digikam-4.4.0-r1:4::gentoo USE="gphoto2 handbook thumbnails -addressbook (-aqua) -debug -doc -mysql -semantic-desktop -themedesigner -video" L10N="-ar% -be% -bg% -bs% -ca% -cs% -da% -de% -el% -en-GB% -eo% -es% -et% -eu% -fa% -fi% -fr% -ga% -gl% -he% -hi% -hr% -hu% -is% -it% -ja% -km% -ko% -lt% -lv% -ms% -nb% -nds% -ne% -nl% -nn% -pa% -pl% -pt% -pt-BR% -ro% -ru% -se% -sk% -sl% -sq% -sv% -th% -tr% -uk% -vi% -zh-CN% -zh-TW%" LINGUAS="(-ar%) (-be%) (-bg%) (-bs%) (-ca%) (-cs%) (-da%) (-de%) (-el%) (-en_GB%) (-eo%) (-es%) (-et%) (-eu%) (-fa%) (-fi%) (-fr%) (-ga%) (-gl%) (-he%) (-hi%) (-hr%) (-hu%) (-is%) (-it%) (-ja%) (-km%) (-ko%) (-lt%) (-lv%) (-ms%) (-nb%) (-nds%) (-ne%) (-nl%) (-nn%) (-pa%) (-pl%) (-pt%) (-pt_BR%) (-ro%) (-ru%) (-se%) (-sk%) (-sl%) (-sq%) (-sv%) (-th%) (-tr%) (-uk%) (-vi%) (-zh_CN%) (-zh_TW%)" 0 KiB [ebuild R] app-text/acroread-9.5.5-r3::gentoo USE="nsplugin -html -ldap" L10N="-ja% -ko% -zh-CN% -zh-TW%" LINGUAS="(-ja%) (-ko%) (-zh_CN%) (-zh_TW%)" 0 KiB [ebuild U ] media-gfx/gimp-2.8.14-r2:2::gentoo [2.8.14-r1:2::gentoo] USE="alsa bzip2 dbus exif jpeg lcms mng pdf png svg tiff udev -aalib (-altivec) (-aqua) -curl -debug -doc -gnome -jpeg2k -postscript -python -smp {-test} -webkit -wmf -xpm" CPU_FLAGS_X86="mmx sse" LINGUAS="en_CA -am -ar -ast -az -be -bg -br -ca -ca@valencia -cs -csb -da -de -dz -el -en_GB -eo -es -et -eu -fa -fi -fr -ga -gl -gu -he -hi -hr -hu -id -is -it -ja -ka -kk -km -kn -ko -lt -lv -mk -ml -ms -my -nb -nds -ne -nl -nn -oc -pa -pl -pt -pt_BR -ro -ru -rw -si -sk -sl -sr -sr@latin -sv -ta -te -th -tr -tt -uk -vi -xh -yi -zh_CN -zh_HK -zh_TW" PYTHON_TARGETS="python2_7" 0 KiB [ebui