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, Bastian Blank wrote:
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 peaceful -- not for conquest. When we do battle, it
is only because we have no choice.
-- Kirk, "The Squire of Gothos", stardate 2124.5
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
