Re: [SOLVED] Re: wine-unstable 64 bit

2014-06-20 Thread Henrique de Moraes Holschuh
On Fri, 20 Jun 2014, berenger.mo...@neutralite.org wrote: > So I was wrong. Not really surprising honestly, but I think I have > seen such assertion somewhere else from someone more knowledgeable > than me. Now you have the URL to the spec ;-) http://pubs.opengroup.org/onlinepubs/009695399/utilit

Re: [SOLVED] Re: wine-unstable 64 bit

2014-06-20 Thread berenger . morel
Le 19.06.2014 16:22, Henrique de Moraes Holschuh a écrit : On Thu, 19 Jun 2014, berenger.mo...@neutralite.org wrote: This syntax "$(command)" is not portable. It is a POSIX shell construct. Anything that doesn't implement it should not be linked to /bin/sh in the first place. So I was w

Re: [SOLVED] Re: wine-unstable 64 bit

2014-06-19 Thread Floris
Op Thu, 19 Jun 2014 15:18:34 +0200 schreef : Le 11.06.2014 14:42, Floris a écrit : If someone have any tips, tricks or commands on the shell script. I love to hear them. if [ "$(dpkg --print-architecture)" = "amd64" -a "$(dpkg --print-foreign-architectures)" != "i386" ]; then This synta

Re: [SOLVED] Re: wine-unstable 64 bit

2014-06-19 Thread Henrique de Moraes Holschuh
On Thu, 19 Jun 2014, berenger.mo...@neutralite.org wrote: > This syntax "$(command)" is not portable. It is a POSIX shell construct. Anything that doesn't implement it should not be linked to /bin/sh in the first place. http://pubs.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html sec

Re: [SOLVED] Re: wine-unstable 64 bit

2014-06-19 Thread Martin Read
On 19/06/14 14:18, berenger.mo...@neutralite.org wrote: This syntax "$(command)" is not portable. The $() syntax for command substitution is *not* a bashism. It's been a POSIX Shell Command Language construct for at least a decade. http://pubs.opengroup.org/onlinepubs/009695399/utilities/xcu

Re: [SOLVED] Re: wine-unstable 64 bit

2014-06-19 Thread berenger . morel
Le 11.06.2014 14:42, Floris a écrit : If someone have any tips, tricks or commands on the shell script. I love to hear them. if [ "$(dpkg --print-architecture)" = "amd64" -a "$(dpkg --print-foreign-architectures)" != "i386" ]; then This syntax "$(command)" is not portable. If you want to w

[SOLVED] Re: wine-unstable 64 bit

2014-06-11 Thread Floris
Op Mon, 09 Jun 2014 13:44:04 +0200 schreef Ralf Mardorf : On Mon, 2014-06-09 at 11:45 +0200, berenger.mo...@neutralite.org wrote: Thank you both for your little "compile-it-yourself-how-to". I have add a patch [1] to the wine source package and successfully rebuild it. Also I have modifi

Re: wine-unstable 64 bit

2014-06-09 Thread Ralf Mardorf
On Mon, 2014-06-09 at 11:45 +0200, berenger.mo...@neutralite.org wrote: > Never tried to do that myself, but it should work: > > _ install build-dependencies of the package you want ( #aptitude > build-dep ) > _ download the source package ( $apt-get source ) > _ replace the source code with of

Re: wine-unstable 64 bit

2014-06-09 Thread Floris
Op Mon, 09 Jun 2014 11:19:32 +0200 schreef Floris : With the current version of wine64-unstable (1.7.19-1) there is no possibility to run a 64-bit wineserver floris@Alice:~$ rm -R win64 floris@Alice:~$ WINEPREFIX=/home/floris/win64 WINEARCH=win64 wine-unstable wincfg wine: created the con

Re: wine-unstable 64 bit

2014-06-09 Thread berenger . morel
Hello. Le 09.06.2014 11:19, Floris a écrit : With the current version of wine64-unstable (1.7.19-1) there is no possibility to run a 64-bit wineserver floris@Alice:~$ rm -R win64 floris@Alice:~$ WINEPREFIX=/home/floris/win64 WINEARCH=win64 wine-unstable wincfg wine: created the configuration

wine-unstable 64 bit

2014-06-09 Thread Floris
With the current version of wine64-unstable (1.7.19-1) there is no possibility to run a 64-bit wineserver floris@Alice:~$ rm -R win64 floris@Alice:~$ WINEPREFIX=/home/floris/win64 WINEARCH=win64 wine-unstable wincfg wine: created the configuration directory '/home/floris/win64' wine: WINEAR