On Sun, Jul 24, 2011 at 12:59:46AM +0200, Bastian Blank wrote:
On Wed, Jul 20, 2011 at 08:52:45PM +0200, Philipp Kern wrote:
I think that's a misconfiguration of the buildds. They're supposed to
put linux32 into the schroot configuration if the kernel arch differs
from the userspace arch,
On Sun, Jul 24, 2011 at 11:33:42 (CEST), Philipp Kern wrote:
On Sun, Jul 24, 2011 at 12:59:46AM +0200, Bastian Blank wrote:
On Wed, Jul 20, 2011 at 08:52:45PM +0200, Philipp Kern wrote:
I think that's a misconfiguration of the buildds. They're supposed to
put linux32 into the schroot
On Sun, Jul 24, 2011 at 11:33:42 (CEST), Philipp Kern wrote:
On Sun, Jul 24, 2011 at 12:59:46AM +0200, Bastian Blank wrote:
On Wed, Jul 20, 2011 at 08:52:45PM +0200, Philipp Kern wrote:
I think that's a misconfiguration of the buildds. They're
supposed to put linux32 into the schroot
On Sun, Jul 24, 2011 at 12:59:11PM +0200, David Kuehling wrote:
Well, if it allows people like me to just do 'apt-get source' and
'dpkg-buildpackage' without thinking about which kernel they run, it
does more good than harm, doesn't it :)
Maybe the really correct, and right way to fix that,
On Sun, Jul 24, 2011 at 12:03:59AM +0200, Aurelien Jarno wrote:
It at least does the right thing on the i386 buildds. Maybe the
chroot was older?
It's what I thought first, but the script [1] doesn't seems to do that,
or at least I fail to see where.
[1]
On Sun, Jul 24, 2011 at 12:59:46AM +0200, Bastian Blank wrote:
On Wed, Jul 20, 2011 at 08:52:45PM +0200, Philipp Kern wrote:
I think that's a misconfiguration of the buildds. They're supposed to
put linux32 into the schroot configuration if the kernel arch differs
from the userspace arch,
* Kurt Roeckx (k...@roeckx.be) [110724 15:30]:
/usr/sbin/sbuild-createchroot has:
I use /usr/share/sbuild/create-chroot.sh (which is actually the one
doing it right for lvm-type chroots), and that does it for mips*,
sparc, s390, powerpc.
Andi
___
On Sun, Jul 24, 2011 at 03:37:13PM +0200, Andreas Barth wrote:
* Kurt Roeckx (k...@roeckx.be) [110724 15:30]:
/usr/sbin/sbuild-createchroot has:
I use /usr/share/sbuild/create-chroot.sh (which is actually the one
doing it right for lvm-type chroots), and that does it for mips*,
sparc,
On Sun, Jul 24, 2011 at 13:07:11 (CEST), Philipp Kern wrote:
On Sun, Jul 24, 2011 at 12:59:11PM +0200, David Kuehling wrote:
Well, if it allows people like me to just do 'apt-get source' and
'dpkg-buildpackage' without thinking about which kernel they run, it
does more good than harm, doesn't
On Sun, Jul 24, 2011 at 05:39:20PM +0200, Reinhard Tartler wrote:
On Sun, Jul 24, 2011 at 13:07:11 (CEST), Philipp Kern wrote:
On Sun, Jul 24, 2011 at 12:59:11PM +0200, David Kuehling wrote:
Well, if it allows people like me to just do 'apt-get source' and
'dpkg-buildpackage' without
On Sun, Jul 24, 2011 at 18:56:21 (CEST), Kurt Roeckx wrote:
On Sun, Jul 24, 2011 at 05:39:20PM +0200, Reinhard Tartler wrote:
On Sun, Jul 24, 2011 at 13:07:11 (CEST), Philipp Kern wrote:
On Sun, Jul 24, 2011 at 12:59:11PM +0200, David Kuehling wrote:
Well, if it allows people like me to
On Sun, Jul 24, 2011 at 05:39:20PM +0200, Reinhard Tartler wrote:
[..]
Maybe the really correct, and right way to fix that, though, is to
patch the configure script to check for the ABI used by $CC
instead of 'uname -m'. That kind of fix could then also go
upstream.
Normally you pass
On Wed, Jul 20, 2011 at 08:52:45PM +0200, Philipp Kern wrote:
[ mips* buildds Cc'ed ]
On Tue, Jul 19, 2011 at 09:58:34PM +0200, David Kuehling wrote:
The complete userspace *is* o32, just the kernel is not. I think that
is a pretty valid way to run a system, compiling the kernel for
On Sat, Jul 23, 2011 at 10:44:22PM +0200, Aurelien Jarno wrote:
On Wed, Jul 20, 2011 at 08:52:45PM +0200, Philipp Kern wrote:
[ mips* buildds Cc'ed ]
On Tue, Jul 19, 2011 at 09:58:34PM +0200, David Kuehling wrote:
The complete userspace *is* o32, just the kernel is not. I think that
On Sat, Jul 23, 2011 at 11:37:08PM +0200, Kurt Roeckx wrote:
On Sat, Jul 23, 2011 at 10:44:22PM +0200, Aurelien Jarno wrote:
On Wed, Jul 20, 2011 at 08:52:45PM +0200, Philipp Kern wrote:
[ mips* buildds Cc'ed ]
On Tue, Jul 19, 2011 at 09:58:34PM +0200, David Kuehling wrote:
The
On Wed, Jul 20, 2011 at 08:52:45PM +0200, Philipp Kern wrote:
I think that's a misconfiguration of the buildds. They're supposed to
put linux32 into the schroot configuration if the kernel arch differs
from the userspace arch, to get the right entry into uname.
Negative. The build have to
* Aurelien Jarno (aurel...@aurel32.net) [110723 23:17]:
On Wed, Jul 20, 2011 at 08:52:45PM +0200, Philipp Kern wrote:
[ mips* buildds Cc'ed ]
On Tue, Jul 19, 2011 at 09:58:34PM +0200, David Kuehling wrote:
The complete userspace *is* o32, just the kernel is not. I think that
is a
[ mips* buildds Cc'ed ]
On Tue, Jul 19, 2011 at 09:58:34PM +0200, David Kuehling wrote:
The complete userspace *is* o32, just the kernel is not. I think that
is a pretty valid way to run a system, compiling the kernel for mips64
gives better performance on those machines that can run mips64
On 07/17/2011 01:14 PM, Reinhard Tartler wrote:
cOn Sun, Jul 17, 2011 at 12:36:23 (CEST), David Kuehling wrote:
[..]
Grepping over a copy of the ffmpeg sources, I find ldl in
inline-assembler fragments in various files, such as intreadwrite.h.
These are #ifdefed checking for ARCH_MIPS64,
From: David Kuehling dvdkh...@gmx.de
Subject: Re: Libav 0.7 FTBFS on mipsel: Error: opcode not supported on this
processor: mips2 (mips2) `ldl $2, 7($13)'
Forcing ./configure --arch=mips/mipsel might
help.
That makes sense to me. I'll add
--arch=$(DEB_BUILD_CPU) to the
Reinhard == Reinhard Tartler siret...@tauware.de writes:
Hi, I've noticed that Libav FTBFS on mipsel in experimental. The
buildlog looks like this:
/tmp/ccztZJXP.s: Assembler messages: /tmp/ccztZJXP.s:334: Error:
opcode not supported on this processor: mips2 (mips2) `ldl $2,7($13)'
[..]
On Sun, Jul 17, 2011 at 12:36:23 (CEST), David Kuehling wrote:
Reinhard == Reinhard Tartler siret...@tauware.de writes:
Hi, I've noticed that Libav FTBFS on mipsel in experimental. The
buildlog looks like this:
/tmp/ccztZJXP.s: Assembler messages: /tmp/ccztZJXP.s:334: Error:
opcode not
22 matches
Mail list logo
