I believe the fix for this is to create a new tachyon architecture
linux-base-thr that doesn't assume x86 and thus leaves off -m32.
I've placed a new source package that should fix this problem at
http://web.mit.edu/sage/export/tachyon_0.98~beta.dfsg-1.dsc. I've not
been able to test this
On Fri, Jun 20, 2008 at 11:36:55AM -0400, Timothy G Abbott wrote:
I believe the fix for this is to create a new tachyon architecture
linux-base-thr that doesn't assume x86 and thus leaves off -m32.
It is wrong even on x86. The compiler knows its default target.
Bastian
--
Our missions are
Well, upstream does not provide any build target that does not explicitly
specify -m(something); the new Make-arch entry I've added does not add
this property.
I think you are right however that I should be using the new entry on all
architectures.
-Tim Abbott
On Fri, 20 Jun 2008,
Package: tachyon
Version: 0.98~beta-1
Severity: serious
There was an error while trying to autobuild your package:
Automatic build of tachyon_0.98~beta-1 on debian-31.osdl.marist.edu by
sbuild/s390 98
[...]
make[3]: Nothing to be done for `../compile/linux-thr'.
make[3]: Nothing to be done
4 matches
Mail list logo
