Bug#366741: get i686-linux-gnu binaries on amd64
package boinc boinc-client boinc-dev boinc-manager boinc-server tags 366741 + pending fixed-upstream thanks The alternative platform mechanism now also works for x86_64-pc-linux-gnu (amd64), see http://boinc.berkeley.edu/trac/changeset/12467. This bug can be closed in versions 5.9.4. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366741: get i686-linux-gnu binaries on amd64
On Tue, Jul 11, 2006 at 12:51:22AM +0200, Frank S. Thomas wrote: severity 366741 normal stop On Sunday 21 May 2006 11:03, Frank S. Thomas wrote: On Wednesday 10 May 2006 21:28, Robert Millan wrote: TTBOMK, no boinc projects are providing core binaries for amd64. So our only hope of making this package useful on that platform is requesting i686 ones instead. Another alternative would be if we would package and upload at least one open source project application. Thus ensuring that BOINC is also useful on all other architectures Debian supports and not i386 and amd64 only. I'm currently preparing the [EMAIL PROTECTED] application[1] for release. The [EMAIL PROTECTED] Enhanced application for BOINC has been uploaded a few days ago to Debian unstable. The name of the package is boinc-app-seti and it should integrate nicely if using Debian's standard BOINC data directory (which is /var/lib/boinc-client/). If using not the default data directory some manual work is needed, consult /usr/share/doc/boinc-client/README.Debian for more information. Please note that this doesn't address this bug (unpatched boinc for amd64 is not usable on most projects). -- Robert Millan My spam trap is [EMAIL PROTECTED] Note: this address is only intended for spam harvesters. Writing to it will get you added to my black list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366741: get i686-linux-gnu binaries on amd64
On Tuesday 11 July 2006 08:21, Robert Millan wrote: On Tue, Jul 11, 2006 at 12:51:22AM +0200, Frank S. Thomas wrote: severity 366741 normal stop On Sunday 21 May 2006 11:03, Frank S. Thomas wrote: On Wednesday 10 May 2006 21:28, Robert Millan wrote: TTBOMK, no boinc projects are providing core binaries for amd64. So our only hope of making this package useful on that platform is requesting i686 ones instead. Another alternative would be if we would package and upload at least one open source project application. Thus ensuring that BOINC is also useful on all other architectures Debian supports and not i386 and amd64 only. I'm currently preparing the [EMAIL PROTECTED] application[1] for release. The [EMAIL PROTECTED] Enhanced application for BOINC has been uploaded a few days ago to Debian unstable. The name of the package is boinc-app-seti and it should integrate nicely if using Debian's standard BOINC data directory (which is /var/lib/boinc-client/). If using not the default data directory some manual work is needed, consult /usr/share/doc/boinc-client/README.Debian for more information. Please note that this doesn't address this bug (unpatched boinc for amd64 is not usable on most projects). I'm well aware of that but the situation changed with boinc-app-seti from not usable on all projects to not usable on all but one project. - Frank pgp7SdqmKnIZY.pgp Description: PGP signature
Bug#366741: get i686-linux-gnu binaries on amd64
severity 366741 normal stop On Sunday 21 May 2006 11:03, Frank S. Thomas wrote: On Wednesday 10 May 2006 21:28, Robert Millan wrote: TTBOMK, no boinc projects are providing core binaries for amd64. So our only hope of making this package useful on that platform is requesting i686 ones instead. Another alternative would be if we would package and upload at least one open source project application. Thus ensuring that BOINC is also useful on all other architectures Debian supports and not i386 and amd64 only. I'm currently preparing the [EMAIL PROTECTED] application[1] for release. The [EMAIL PROTECTED] Enhanced application for BOINC has been uploaded a few days ago to Debian unstable. The name of the package is boinc-app-seti and it should integrate nicely if using Debian's standard BOINC data directory (which is /var/lib/boinc-client/). If using not the default data directory some manual work is needed, consult /usr/share/doc/boinc-client/README.Debian for more information. - Frank -- The best way to accelerate any computer running Windows is at 9,81 m/s^2. pgpa3CJscTyym.pgp Description: PGP signature
Bug#366741: get i686-linux-gnu binaries on amd64
On Monday 22 May 2006 17:52, Marc F. Clemente wrote: Robert Millan wrote: Then I think the right fix would be to attempt a download of x86_64-pc-linux-gnu binary, and if that fails fallback to i386-pc-linux-gnu. In that situation libc6-i386 wouldn't be needed in Depends (maybe Recommends instead). Or maybe this alternative... Boinc checks to see if i386 libraries are installed. If they are, then try and download the i386 client binary. libc6-i386 could then be just a Suggests. I'll happily accept patches for both proposals, of course. However, amd64 isn't a niche arch and therefore should be supported by all major BOINC proejcts, IMHO. Robert, did you asked on the CPDN forum for amd64 binaries? I do agree that it would be nice to have a packaged binary client for all (or most) architectures. Seti is good. Thanks, Frank :-) Marc, did you tried to compile the boinc-app-seti package on your amd64? I'm curious if it compiles on amd64 without errors. Grüße, Frank -- ,''`. Frank S. Thomas [EMAIL PROTECTED] : :' : http://www.thomas-alfeld.de/frank `. `' GPG Key ID: 0xDC426429 `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366741: get i686-linux-gnu binaries on amd64
On Tue, May 23, 2006 at 12:56:36PM +0200, Frank S. Thomas wrote: On Monday 22 May 2006 17:52, Marc F. Clemente wrote: Robert Millan wrote: Then I think the right fix would be to attempt a download of x86_64-pc-linux-gnu binary, and if that fails fallback to i386-pc-linux-gnu. In that situation libc6-i386 wouldn't be needed in Depends (maybe Recommends instead). Or maybe this alternative... Boinc checks to see if i386 libraries are installed. If they are, then try and download the i386 client binary. libc6-i386 could then be just a Suggests. Why would one prefer the i386 binary over the amd64 one, in case both exist? If the amd64 performs worse than the i386 one, then the project in question shouldn't be distributing 64bit binaries in first place. -- Robert Millan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366741: get i686-linux-gnu binaries on amd64
On Tuesday 23 May 2006 14:57, Robert Millan wrote: On Monday 22 May 2006 17:52, Marc F. Clemente wrote: Robert Millan wrote: Then I think the right fix would be to attempt a download of x86_64-pc-linux-gnu binary, and if that fails fallback to i386-pc-linux-gnu. In that situation libc6-i386 wouldn't be needed in Depends (maybe Recommends instead). Or maybe this alternative... Boinc checks to see if i386 libraries are installed. If they are, then try and download the i386 client binary. libc6-i386 could then be just a Suggests. Why would one prefer the i386 binary over the amd64 one, in case both exist? I think Marc meant that the client should only try to download the i386 binary if the project does not distribute amd64 ones. It's like your proposal plus the additional check for the libc6-i386 package. Grüße, Frank -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366741: get i686-linux-gnu binaries on amd64
On Tue, May 23, 2006 at 03:55:36PM +0200, Frank S. Thomas wrote: On Tuesday 23 May 2006 14:57, Robert Millan wrote: On Monday 22 May 2006 17:52, Marc F. Clemente wrote: Robert Millan wrote: Then I think the right fix would be to attempt a download of x86_64-pc-linux-gnu binary, and if that fails fallback to i386-pc-linux-gnu. In that situation libc6-i386 wouldn't be needed in Depends (maybe Recommends instead). Or maybe this alternative... Boinc checks to see if i386 libraries are installed. If they are, then try and download the i386 client binary. libc6-i386 could then be just a Suggests. Why would one prefer the i386 binary over the amd64 one, in case both exist? I think Marc meant that the client should only try to download the i386 binary if the project does not distribute amd64 ones. It's like your proposal plus the additional check for the libc6-i386 package. Ah, ok. Sounds fine then. -- Robert Millan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366741: get i686-linux-gnu binaries on amd64
Robert Millan wrote: Then I think the right fix would be to attempt a download of x86_64-pc-linux-gnu binary, and if that fails fallback to i386-pc-linux-gnu. In that situation libc6-i386 wouldn't be needed in Depends (maybe Recommends instead). Or maybe this alternative... Boinc checks to see if i386 libraries are installed. If they are, then try and download the i386 client binary. libc6-i386 could then be just a Suggests. I do agree that it would be nice to have a packaged binary client for all (or most) architectures. Seti is good. Thanks, Frank :-) Marc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366741: get i686-linux-gnu binaries on amd64
On Wednesday 10 May 2006 21:28, Robert Millan wrote: TTBOMK, no boinc projects are providing core binaries for amd64. So our only hope of making this package useful on that platform is requesting i686 ones instead. Another alternative would be if we would package and upload at least one open source project application. Thus ensuring that BOINC is also useful on all other architectures Debian supports and not i386 and amd64 only. I'm currently preparing the [EMAIL PROTECTED] application[1] for release. Grüße, Frank [1] http://svn.debian.org/wsvn/pkg-boinc/trunk/boinc-app-seti/ -- bureaucracy, n: A method for transforming energy into solid waste. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366741: get i686-linux-gnu binaries on amd64
Robert Millan wrote: TTBOMK, no boinc projects are providing core binaries for amd64. So our only hope of making this package useful on that platform is requesting i686 ones instead. Patch attached. I disagree. I run a 64 bit Seti client on my amd64. I think that's useful enough. The 64 bit client for Seti is available from a third party, or it can be compiled form source. The client is not downloaded automatically because seti does not distribute a pre-compiled 64 bit client. Nonetheless, my amd64 is not a i386. I do not run 32 bit programs, I do not have 32 bit libraries, and I don't want them. I definitely do not want boinc-client to depend on 32 bit libraries. Marc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366741: get i686-linux-gnu binaries on amd64
On Fri, May 12, 2006 at 09:31:52AM -0500, Marc F. Clemente wrote: Robert Millan wrote: TTBOMK, no boinc projects are providing core binaries for amd64. So our only hope of making this package useful on that platform is requesting i686 ones instead. Patch attached. I disagree. I run a 64 bit Seti client on my amd64. I think that's useful enough. The 64 bit client for Seti is available from a third party, or it can be compiled form source. The client is not downloaded automatically because seti does not distribute a pre-compiled 64 bit client. Nonetheless, my amd64 is not a i386. I do not run 32 bit programs, I do not have 32 bit libraries, and I don't want them. I definitely do not want boinc-client to depend on 32 bit libraries. Then I think the right fix would be to attempt a download of x86_64-pc-linux-gnu binary, and if that fails fallback to i386-pc-linux-gnu. In that situation libc6-i386 wouldn't be needed in Depends (maybe Recommends instead). -- Robert Millan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366741: get i686-linux-gnu binaries on amd64
Package: boinc-client Version: 5.4.9-1+rmh Severity: important Tags: patch TTBOMK, no boinc projects are providing core binaries for amd64. So our only hope of making this package useful on that platform is requesting i686 ones instead. Patch attached. It also fixes the cpu check to work on non-Linux (where the best choice is, imho, assuming the kernel has Linux abi emulation). -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-amd64-k8 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Versions of packages boinc-client depends on: ii adduser 3.87 Add and remove users and groups ii libc6 2.3.6-7GNU C Library: Shared libraries ii libcomerr21.38+1.39-WIP-2006.04.09-1 common error description library ii libcurl3 7.15.3-1 Multi-protocol file transfer libra ii libgcc1 1:4.1.0-1 GCC support library ii libidn11 0.5.18-2 GNU libidn library, implementation ii libkrb53 1.4.3-6MIT Kerberos runtime libraries ii libssl0.9.8 0.9.8a-8 SSL shared libraries ii libstdc++64.1.0-1The GNU Standard C++ Library v3 ii lsb-base 3.1-5 Linux Standard Base 3.1 init scrip ii python2.4 2.4.2-2An interactive high-level object-o ii zlib1g1:1.2.3-11 compression library - runtime boinc-client recommends no packages. -- no debconf information --- boinc-5.4.9.old/debian/rules2006-05-10 20:46:58.0 +0200 +++ boinc-5.4.9/debian/rules2006-05-10 21:10:20.0 +0200 @@ -7,6 +7,7 @@ DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) +DEB_HOST_ARCH_CPU ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_CPU) ifeq ($(DEB_BUILD_GNU_TYPE), $(DEB_HOST_GNU_TYPE)) TYPE_FLAGS = --build $(DEB_HOST_GNU_TYPE) @@ -18,10 +19,16 @@ # If the core client reports that it was built for i486-pc-linux-gnu it won't # download any application or work units, so we use i686-linux-gnu as argument # for configure's --build and --host switches on i386 hosts. -ifeq ($(DEB_HOST_GNU_TYPE), i486-linux-gnu) +ifeq ($(DEB_HOST_ARCH_CPU), i386) DEB_HOST_GNU_TYPE = i686-linux-gnu endif -ifeq ($(DEB_BUILD_GNU_TYPE), i486-linux-gnu) +ifeq ($(DEB_HOST_ARCH_CPU), amd64) + DEB_HOST_GNU_TYPE = i686-linux-gnu +endif +ifeq ($(DEB_BUILD_ARCH_CPU), i386) + DEB_BUILD_GNU_TYPE = i686-linux-gnu +endif +ifeq ($(DEB_BUILD_ARCH_CPU), amd64) DEB_BUILD_GNU_TYPE = i686-linux-gnu endif
