Quoting Neil Williams :
For amd64 to i386, create an i386 chroot with debootstrap and build the
package inside that chroot. This ONLY works for particular combinations
of architectures and amd64 -> i386 is one of those pairs. i386 -> amd64
is NOT the same thing.
Yes, I expected that amd64
On Wed, Nov 09, 2011 at 05:11:49PM +, Neil Williams wrote:
> On Wed, 09 Nov 2011 17:50:09 +0100
> Ole Wolf wrote:
>
> > I'm trying to build packages for multiple architectures. The package builds
> > fine on the native system (amd64), but when I issue "debuild -ai386"
>
> For amd64 to i386,
On 10/11/2011 00:50, Ole Wolf wrote:
> I'm trying to build packages for multiple architectures. The package builds
> fine
> on the native system (amd64), but when I issue "debuild -ai386", I'm
> eventually
> greeted with an error stating that "dh_strip: i686-linux-gnu-strip" doesn't
> exist.
>
On Wed, 09 Nov 2011 17:50:09 +0100
Ole Wolf wrote:
> I'm trying to build packages for multiple architectures. The package builds
> fine on the native system (amd64), but when I issue "debuild -ai386"
For amd64 to i386, create an i386 chroot with debootstrap and build the
package inside that chro
I'm trying to build packages for multiple architectures. The package builds
fine on the native system (amd64), but when I issue "debuild -ai386", I'm
eventually greeted with an error stating that "dh_strip:
i686-linux-gnu-strip" doesn't exist.
Google reveals that several people have flagged thi
5 matches
Mail list logo