Re: Problems compiling wine
On Thu, Aug 11, 2005 at 05:14:17PM +0200, Michelasso wrote: > The problem is that at the moment I cannot get a i386 chroot; I have > followed the guidelines here: > https://alioth.debian.org/docman/view.php/30192/21/debian-amd64-howto.html > (that I cannot read at the moment because of a server problem) > > But I failed: > > aquila:/opt/wine# cd /var/ > aquila:/var# mkdir chroot > aquila:/var# mkdir sid-ia32 > aquila:/var# debootstrap --arch i386 sid /var/chroot/sid-ia32 > http://ftp.debian.org/debian/ > I: Retrieving Release > I: Retrieving Packages > I: Validating Packages > [...] > W: Failure while configuring base packages. This will be attempted 5 times. > W: Failure while configuring base packages. This will be attempted 5 times. > W: Failure while configuring base packages. This will be attempted 5 times. > W: Failure while configuring base packages. This will be attempted 5 times. > W: Failure while configuring base packages. This will be attempted 5 times. > I: Base system installed successfully. > aquila:/var# chroot /var/chroot/sid-ia32/ > aquila:/# aptitude > aptitude: error while loading shared libraries: libsigc-1.2.so.5: > cannot open shared object file: No such file or directory I was trying to help someone yesterday with deboostrap and it seemed that debootstrap 0.2.x from amd64 sarge works perfectly (at least to debootstrap i386 sarge), while 0.3.x from sid is rather broken. So perhaps try debootstraping sarge i386, and then dist-upgrading if you want sid, or try debootstrap package from stable, or try cdebootstrap. With allt he transitions and package changes in sid, it's hard for debootstrap to keep up at all times. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems compiling wine
Michelasso wrote: On 8/11/05, Jo Shields <[EMAIL PROTECTED]> wrote: Once you've got yourself an i386 chroot, why not save yourself the bother of compiling it and just install the i386 debian packages? The problem is that at the moment I cannot get a i386 chroot; I have followed the guidelines here: https://alioth.debian.org/docman/view.php/30192/21/debian-amd64-howto.html (that I cannot read at the moment because of a server problem) But I failed: aquila:/opt/wine# cd /var/ aquila:/var# mkdir chroot aquila:/var# mkdir sid-ia32 aquila:/var# debootstrap --arch i386 sid /var/chroot/sid-ia32 http://ftp.debian.org/debian/ I: Retrieving Release I: Retrieving Packages I: Validating Packages [...] W: Failure while configuring base packages. This will be attempted 5 times. W: Failure while configuring base packages. This will be attempted 5 times. W: Failure while configuring base packages. This will be attempted 5 times. W: Failure while configuring base packages. This will be attempted 5 times. W: Failure while configuring base packages. This will be attempted 5 times. I: Base system installed successfully. aquila:/var# chroot /var/chroot/sid-ia32/ aquila:/# aptitude aptitude: error while loading shared libraries: libsigc-1.2.so.5: cannot open shared object file: No such file or directory Any suggestion? Sid is broken. Use Sarge. --Jo Shields -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems compiling wine
On 8/11/05, Jo Shields <[EMAIL PROTECTED]> wrote: > Once you've got yourself an i386 chroot, why not save yourself the > bother of compiling it and just install the i386 debian packages? > The problem is that at the moment I cannot get a i386 chroot; I have followed the guidelines here: https://alioth.debian.org/docman/view.php/30192/21/debian-amd64-howto.html (that I cannot read at the moment because of a server problem) But I failed: aquila:/opt/wine# cd /var/ aquila:/var# mkdir chroot aquila:/var# mkdir sid-ia32 aquila:/var# debootstrap --arch i386 sid /var/chroot/sid-ia32 http://ftp.debian.org/debian/ I: Retrieving Release I: Retrieving Packages I: Validating Packages [...] W: Failure while configuring base packages. This will be attempted 5 times. W: Failure while configuring base packages. This will be attempted 5 times. W: Failure while configuring base packages. This will be attempted 5 times. W: Failure while configuring base packages. This will be attempted 5 times. W: Failure while configuring base packages. This will be attempted 5 times. I: Base system installed successfully. aquila:/var# chroot /var/chroot/sid-ia32/ aquila:/# aptitude aptitude: error while loading shared libraries: libsigc-1.2.so.5: cannot open shared object file: No such file or directory Any suggestion?
Re: Problems compiling wine
On Thu, Aug 11, 2005 at 03:56:11PM +0100, Jo Shields wrote: > Once you've got yourself an i386 chroot, why not save yourself the > bother of compiling it and just install the i386 debian packages? Maybe to get a newer wine version? I don't know... :) Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems compiling wine
Lennart Sorensen wrote: On Thu, Aug 11, 2005 at 03:25:33PM +0200, Michelasso wrote: Hello everybody, I am running sid 64bit on my turion64 based laptop, and since there are no debian packages for wine for this architecture I am trying to build it form cvs sources. However I get an error when doing make depend: [...] ../../include/winnls.h:756: warning: '__stdcall__' attribute ignored ../../include/winnls.h:757: warning: '__stdcall__' attribute ignored ../../include/winnls.h:758: warning: '__stdcall__' attribute ignored make[2]: *** [casemap.o] Error 1 make[2]: Leaving directory `/opt/wine/libs/unicode' make[1]: *** [unicode] Error 2 make[1]: Leaving directory `/opt/wine/libs' make: *** [libs] Error 2 - (I imagine the line with the errors is somewhere above, but I cannot find it in my terminal buffer.) Any suggestions? Given wine is for emulating the system calls of win32, I would not expect it to even compile on anything other than i386. Does it build inside an i386 chroot OK? Once built as i386 binary I would expect it to run fine on amd64 just as most other i386 binaries do. Len Sorensen Once you've got yourself an i386 chroot, why not save yourself the bother of compiling it and just install the i386 debian packages? --Jo Shields -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems compiling wine
Michelasso <[EMAIL PROTECTED]> writes: > I am running sid 64bit on my turion64 based laptop, and since there > are no debian packages for wine for this architecture I am trying to > build it form cvs sources. Why do you want to run a 64 bit wine? Do you have 64 bit Windows apps you want to use? I doubt that 32 bit programs will run under 64 bit wine even if you would get it to compile. And regarding compiling of wine from CVS sources you probably better ask the wine folks at wine-devel@winehq.org or [EMAIL PROTECTED] Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems compiling wine
On Thu, Aug 11, 2005 at 03:25:33PM +0200, Michelasso wrote: > Hello everybody, > I am running sid 64bit on my turion64 based laptop, and since there > are no debian packages for wine for this architecture I am trying to > build it form cvs sources. > However I get an error when doing make depend: > > > [...] > ../../include/winnls.h:756: warning: '__stdcall__' attribute ignored > ../../include/winnls.h:757: warning: '__stdcall__' attribute ignored > ../../include/winnls.h:758: warning: '__stdcall__' attribute ignored > make[2]: *** [casemap.o] Error 1 > make[2]: Leaving directory `/opt/wine/libs/unicode' > make[1]: *** [unicode] Error 2 > make[1]: Leaving directory `/opt/wine/libs' > make: *** [libs] Error 2 > - > > (I imagine the line with the errors is somewhere above, but I cannot > find it in my terminal buffer.) > > Any suggestions? Given wine is for emulating the system calls of win32, I would not expect it to even compile on anything other than i386. Does it build inside an i386 chroot OK? Once built as i386 binary I would expect it to run fine on amd64 just as most other i386 binaries do. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]