Re: On including 64-bit libs in 32-bit packages (see #344104)

2006-10-31 Thread Goswin von Brederlow
Faidon Liambotis <[EMAIL PROTECTED]> writes: > Matthew Garrett wrote: >> Bill Allombert <[EMAIL PROTECTED]> wrote: >>> On Mon, Oct 23, 2006 at 07:30:47PM +0100, Matthew Garrett wrote: Bear in mind that the 64-bit kernel doesn't offer all the functionality that the 32-bit one does. vm86

Re: On including 64-bit libs in 32-bit packages (see #344104)

2006-10-30 Thread Faidon Liambotis
Matthew Garrett wrote: > Bill Allombert <[EMAIL PROTECTED]> wrote: >> On Mon, Oct 23, 2006 at 07:30:47PM +0100, Matthew Garrett wrote: >>> Bear in mind that the 64-bit kernel doesn't offer all the functionality >>> that the 32-bit one does. vm86 is the most obvious thing missing. >> and it seems a

Re: On including 64-bit libs in 32-bit packages (see #344104)

2006-10-30 Thread Matthew Garrett
Bill Allombert <[EMAIL PROTECTED]> wrote: > On Mon, Oct 23, 2006 at 07:30:47PM +0100, Matthew Garrett wrote: >> Bear in mind that the 64-bit kernel doesn't offer all the functionality >> that the 32-bit one does. vm86 is the most obvious thing missing. > > and it seems a 64-bit kernel needs a 64-

Re: On including 64-bit libs in 32-bit packages (see #344104)

2006-10-30 Thread Bill Allombert
On Mon, Oct 23, 2006 at 07:30:47PM +0100, Matthew Garrett wrote: > Goswin von Brederlow <[EMAIL PROTECTED]> wrote: > > "Nikita V. Youshchenko" <[EMAIL PROTECTED]> writes: > >> Is it possible to make 64bit kernels available? > > > > Sarge does have them and the BTS has a patch for linux-2.6 to enab

Re: On including 64-bit libs in 32-bit packages (see #344104)

2006-10-25 Thread Goswin von Brederlow
Matthew Garrett <[EMAIL PROTECTED]> writes: > Juliusz Chroboczek <[EMAIL PROTECTED]> wrote: > >> If I'm reading the function int10LinuxLoadSubModule in >> os-support/linux/int10/linux.c right, it shouldn't matter. vm86 will >> return ENOSYS, which will cause vm86_tst to fail, which will cause the

Re: On including 64-bit libs in 32-bit packages (see #344104)

2006-10-25 Thread Goswin von Brederlow
Matthew Garrett <[EMAIL PROTECTED]> writes: > Hamish Moffatt <[EMAIL PROTECTED]> wrote: > >> That might explain some trouble with X on obscure video chipsets >> recently reported on debian-amd64 then. > > On any architecture other than i386, Xorg builds use the x86emu backend > rather than the vm8

Re: On including 64-bit libs in 32-bit packages (see #344104)

2006-10-24 Thread Matthew Garrett
Juliusz Chroboczek <[EMAIL PROTECTED]> wrote: > If I'm reading the function int10LinuxLoadSubModule in > os-support/linux/int10/linux.c right, it shouldn't matter. vm86 will > return ENOSYS, which will cause vm86_tst to fail, which will cause the X > server to use x86emu instead of vm86. > > Or

Re: On including 64-bit libs in 32-bit packages (see #344104)

2006-10-24 Thread Juliusz Chroboczek
> >> Bear in mind that the 64-bit kernel doesn't offer all the functionality > >> that the 32-bit one does. vm86 is the most obvious thing missing. > In arch/x86_64/ia32/ia32entry.S, both the vm86 calls (vm86 and vm86old) > are stubbed to sys32_vm86_warning, which just printks "vm86 mode not >

Re: On including 64-bit libs in 32-bit packages (see #344104)

2006-10-23 Thread Matthew Garrett
Hamish Moffatt <[EMAIL PROTECTED]> wrote: > That might explain some trouble with X on obscure video chipsets > recently reported on debian-amd64 then. On any architecture other than i386, Xorg builds use the x86emu backend rather than the vm86 one. In theory that should let things work happily, b

Re: On including 64-bit libs in 32-bit packages (see #344104)

2006-10-23 Thread Hamish Moffatt
On Tue, Oct 24, 2006 at 01:52:05AM +0100, Matthew Garrett wrote: > Hamish Moffatt <[EMAIL PROTECTED]> wrote: > > On Mon, Oct 23, 2006 at 07:30:47PM +0100, Matthew Garrett wrote: > >> Bear in mind that the 64-bit kernel doesn't offer all the functionality > >> that the 32-bit one does. vm86 is the

Re: On including 64-bit libs in 32-bit packages (see #344104)

2006-10-23 Thread Matthew Garrett
Hamish Moffatt <[EMAIL PROTECTED]> wrote: > On Mon, Oct 23, 2006 at 07:30:47PM +0100, Matthew Garrett wrote: >> Bear in mind that the 64-bit kernel doesn't offer all the functionality >> that the 32-bit one does. vm86 is the most obvious thing missing. > > [8:23am] [EMAIL PROTECTED]:~> grep VM86

Re: On including 64-bit libs in 32-bit packages (see #344104)

2006-10-23 Thread Hamish Moffatt
On Mon, Oct 23, 2006 at 07:30:47PM +0100, Matthew Garrett wrote: > Goswin von Brederlow <[EMAIL PROTECTED]> wrote: > > "Nikita V. Youshchenko" <[EMAIL PROTECTED]> writes: > >> Is it possible to make 64bit kernels available? > > > > Sarge does have them and the BTS has a patch for linux-2.6 to enab

Re: On including 64-bit libs in 32-bit packages (see #344104)

2006-10-23 Thread Matthias Julius
Matthew Garrett <[EMAIL PROTECTED]> writes: > Goswin von Brederlow <[EMAIL PROTECTED]> wrote: >> "Nikita V. Youshchenko" <[EMAIL PROTECTED]> writes: >>> Is it possible to make 64bit kernels available? >> >> Sarge does have them and the BTS has a patch for linux-2.6 to enable >> them again. Now go

Re: On including 64-bit libs in 32-bit packages (see #344104)

2006-10-23 Thread Matthew Garrett
Goswin von Brederlow <[EMAIL PROTECTED]> wrote: > "Nikita V. Youshchenko" <[EMAIL PROTECTED]> writes: >> Is it possible to make 64bit kernels available? > > Sarge does have them and the BTS has a patch for linux-2.6 to enable > them again. Now go and hit the kernel team till they apply the > patch

Re: On including 64-bit libs in 32-bit packages (see #344104)

2006-10-23 Thread Goswin von Brederlow
"Nikita V. Youshchenko" <[EMAIL PROTECTED]> writes: >> Am Samstag 21 Oktober 2006 11:49 schrieb Nikita V. Youshchenko: >>> Question is - does Debian i386 currently support running on 64-bit >>> binaries if hardware supports it? >> >> _and_ if the kernel supports it. >> >>> Linux blacky 2.6.18-1-

Re: On including 64-bit libs in 32-bit packages (see #344104)

2006-10-21 Thread Stanislav Maslovski
On Sat, Oct 21, 2006 at 03:18:45PM -0600, Bruce Sass wrote: > On Sat October 21 2006 13:35, Darren Salt wrote: > > I demand that Hendrik Sattler may or may not have written... > > > 64bit kernels are not available in the i386 archive. That makes the > > > 64bit libs rather useless, doesn't it? > >

Re: On including 64-bit libs in 32-bit packages (see #344104)

2006-10-21 Thread Bruce Sass
On Sat October 21 2006 13:35, Darren Salt wrote: > I demand that Hendrik Sattler may or may not have written... > > 64bit kernels are not available in the i386 archive. That makes the > > 64bit libs rather useless, doesn't it? > > No - you could be using a locally-built 64-bit kernel. Perhaps i386

Re: On including 64-bit libs in 32-bit packages (see #344104)

2006-10-21 Thread Nikita V. Youshchenko
> Am Samstag 21 Oktober 2006 11:49 schrieb Nikita V. Youshchenko: >> Question is - does Debian i386 currently support running on 64-bit >> binaries if hardware supports it? > > _and_ if the kernel supports it. > >> Linux blacky 2.6.18-1-k7 #1 SMP Fri Sep 29 17:06:47 UTC 2006 i686 >> GNU/Linux >

Re: On including 64-bit libs in 32-bit packages (see #344104)

2006-10-21 Thread Darren Salt
I demand that Hendrik Sattler may or may not have written... [snip] > 64bit kernels are not available in the i386 archive. That makes the 64bit > libs rather useless, doesn't it? No - you could be using a locally-built 64-bit kernel. -- | Darren Salt| linux or ds at | nr. Ashin

Re: On including 64-bit libs in 32-bit packages (see #344104)

2006-10-21 Thread Hendrik Sattler
Am Samstag 21 Oktober 2006 11:49 schrieb Nikita V. Youshchenko: > Question is - does Debian i386 currently support running on 64-bit binaries > if hardware supports it? _and_ if the kernel supports it. > Linux blacky 2.6.18-1-k7 #1 SMP Fri Sep 29 17:06:47 UTC 2006 i686 GNU/Linux -k7 is for Athlo

On including 64-bit libs in 32-bit packages (see #344104)

2006-10-21 Thread Nikita V. Youshchenko
Question is - does Debian i386 currently support running on 64-bit binaries if hardware supports it? Just checked: $ apt-get install libc6-dev-amd64 ... $ gcc -m64 -o hello hello.c $ ./hello bash: ./hello: cannot execute binary file $ cat /proc/cpuinfo ... model name : AMD Athlon(tm) 64 X2