Re: problem running Xprint on amd64 (x86-64)

DP == Drew Parsons [EMAIL PROTECTED] writes: DP One of my Debian users has experienced some problems running Xprint on DP amd64 (x86-64). This would be me... DP Originally he was getting a segfault DP (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=278510) DP He now reports the

Re: problem running Xprint on amd64 (x86-64)

On Wed, 2004-11-24 at 11:25 +1100, Drew Parsons wrote: One of my Debian users has experienced some problems running Xprint on amd64 (x86-64). Originally he was getting a segfault (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=278510) He now reports the segfault is no longer occuring,

Re: testing d-i on amd64

Harald Dunkel [EMAIL PROTECTED] writes: Hi folks, I tried to build and test d-i on amd64 (gcc-3.4), but for the current version 'make build-monolithic' failed with some broken dependencies and missing packages: ... Would somebody mind to update the udebs for amd64 (gcc-3.4)? Many thanx

strategy for setting up an AMD64 system

I'm thinking about buying a 64 it system and have some questions. I've looked at the HOW-TO and see comments about installing 64 bit directly or installing 32 bit and then installing 64 bit in a chroot. I'm confident that I can install a 32 bit system with no more difficulties than getting

Problem with htDig

Hello, I use the pure64 distribution with htDig 3.1.6-10.1. I can create the database for htDig and it seems to work, because htmerge outputs a lot of correct informations. But the commands htdumd and htsearch give no output. I think I have indexed more than 2 pages. Has anyone expirience

Re: [ Spam 50 ]::Mplayer?

Ernest jw ter Kuile wrote: On Tuesday 23 November 2004 10:56, Johan Groth wrote: It is not that difficult to compile by yourself. I did that, and did some experimenting with it, using the 32 bit version of mencoder as reference. For some reason the 32bit mencoder beats the hell out of the 64

Re: Mirorring Debian AMD 64 bit version

Hi, yes please, could someone give a bit more information about that. I have looked the http://debian-amd64.alioth.debian.org/archive-structure.txt file, I also I have realized that there's also some directories as: http://debian-amd64.alioth.debian.org/openoffice.org/

Re: strategy for setting up an AMD64 system

Hello, It looks like there are two current strategies: - Install a 64 bit system followed by a 32 bit system in a chroot. - Install a 32 but system followed by a 64 bit system also in a chroot. I have just installed (or better say: the base system is working, the rest is being added during

Re: strategy for setting up an AMD64 system

On Wed, Nov 24, 2004 at 04:59:33AM -0600, Hank Barta wrote: [snip] My second concern is that I be able to run 32 bit apps for which no 64 bit counterparts exist. It looks like there are two current strategies: - Install a 64 bit system followed by a 32 bit system in a chroot. - Install a

/pure64 vs. /gcc-3.4

Hello, I read this list since last week. But my question is, which tree I should use. At the moment I have the /pure64. Make it sense to use the /gcc-3.4? If yes, what is the easiest way, to change the distribution. Best Regards Stefan Luethje

ia32-libs vs. ia32 chroot

Hi, In the AMD64 HOW-TO, two ways to run 32 bit apps are described, the quick way via ia32-libs and Installing a Debian IA32 chroot system. Can someone expand on the pros/cons of the two approaches? Is the ia32-libs approach just too limited for most people? My need is to run VSS under wine.

Re: ia32-libs vs. ia32 chroot

IA32 Chroot: + Can install other libraries very easily + Can add library directories to /etc/ld.so.conf so it runs like the ia32-libs - Slightly more effort to setup - Takes up quite a bit more space ia32-libs: + Install and run (for limited library dependencies) - Not a complete 32bit system

Re: /pure64 vs. /gcc-3.4

I can tell you that if you're planning on using the latest nvidia module, you'll need gcc-3.4. Other than that I'm not entirely certain about the differences between the two archives, but I can point you to a thread we had shortly before you arrived on the list about the same subject.

Re: /pure64 vs. /gcc-3.4

Jared Burke wrote: I can tell you that if you're planning on using the latest nvidia module, you'll need gcc-3.4. Other than that I'm not entirely certain about the differences between the two archives, but I can point you to a thread we had shortly before you arrived on the list about the

Re: /pure64 vs. /gcc-3.4

Jared Burke wrote: I can tell you that if you're planning on using the latest nvidia module, you'll need gcc-3.4. You only need to compile the module with gcc-3.4 because the kernel in pure64 was also compiled that way. I am using the latest nvidia module with /pure64. Assuming you are using

Re: I need explanation on the design of debian-amd64.

[EMAIL PROTECTED] wrote: I only have a 10Gb HD (for the moment, I'm saving to get another), so I don't find it really attractive to install the full 64bits system, and then install lots of 32bits libraries (and maybe other binaries) in a chroot jail just to run, say, doom3, or openoffice.org.

of mice, Linux and X

Just for completness. you don't seem to mention what type of mouse you have, Normally all this should be correctly detected by the automatic HW detection system. Automatique mouse detection is currently quite good, however, it has, indeed, been known to fail. for mice plugged on the PS/2

Re: Bug#282763: Installation report amd64 (gcc-3.4)

Harald Dunkel wrote: Joey Hess wrote: I thought EFI was only an ia64 thing. Strange. Could you send a tarball of /var/log/debian-installer/ from the installed system so I can try to see why it was doing EFI stuff? See attachment. From the d-i status file: Package: partman-efi Status: