On Wed, Jan 26, 2011 at 06:46:33PM +0100, Goswin von Brederlow wrote:
> Adam Borowski writes:
> > Aren't ia32-libs on their way out, together with rest of the bi-arch stuff?
>
> Since sarge, yes. Nothing is as permanent as a quick temporary hack.
With no multiarch on horizon, there wasn't anythi
Adam Borowski writes:
> On Wed, Jan 26, 2011 at 12:44:02PM +0100, Goswin von Brederlow wrote:
>> Adam Borowski writes:
>> > On Mon, Jan 17, 2011 at 11:49:17AM +0800, Paul Wise wrote:
>> >> Add lib32 packages for the deps.
>>
>> Actually you need ia32-libs-dev and also gcc-multilib when you COMP
On Wed, Jan 26, 2011 at 12:44:02PM +0100, Goswin von Brederlow wrote:
> Adam Borowski writes:
> > On Mon, Jan 17, 2011 at 11:49:17AM +0800, Paul Wise wrote:
> >> Add lib32 packages for the deps.
>
> Actually you need ia32-libs-dev and also gcc-multilib when you COMPILE a
> 32bit package. ia32-lib
Adam Borowski writes:
> On Mon, Jan 17, 2011 at 11:49:17AM +0800, Paul Wise wrote:
>> On Mon, Jan 17, 2011 at 11:25 AM, Steve M. Robbins wrote:
>>
>> > What is the recommended course of action for such a package?
>>
>> For now: build on a 32-bit system or in a 32-bit chroot.
>>
>> Other optio
On Mon, 17 Jan 2011 10:53:58 +0100
Adam Borowski wrote:
> On Mon, Jan 17, 2011 at 11:49:17AM +0800, Paul Wise wrote:
> > On Mon, Jan 17, 2011 at 11:25 AM, Steve M. Robbins wrote:
> >
> > > What is the recommended course of action for such a package?
> >
> > For now: build on a 32-bit system or
On Mon, Jan 17, 2011 at 11:49:17AM +0800, Paul Wise wrote:
> On Mon, Jan 17, 2011 at 11:25 AM, Steve M. Robbins wrote:
>
> > What is the recommended course of action for such a package?
>
> For now: build on a 32-bit system or in a 32-bit chroot.
>
> Other options in increasing order of prefere
On Mon, Jan 17, 2011 at 11:25 AM, Steve M. Robbins wrote:
> What is the recommended course of action for such a package?
For now: build on a 32-bit system or in a 32-bit chroot.
Other options in increasing order of preference:
Add deps to ia32-libs.
Add lib32 packages for the deps.
Help fix
Hi,
I've recently adopted a package (nyquist) that only builds in 32-bit
mode. I'm struggling with supporting it on amd64 and other 64-bit
architectures in Debian.
First: yes, clearly the code should be migrated to 64-bits. Upstream
is aware of that and it's a nontrivial effort. I'm interested
8 matches
Mail list logo