Re: No luck with Kaffe

• To: hohmuth@innocent.com (Michael Hohmuth)
• Subject: Re: No luck with Kaffe
• From: Godmar Back <gback@cs.utah.edu>
• Date: Tue, 12 Oct 1999 12:37:21 -0600 (MDT)
• Cc: oskit-users@cs.utah.edu
• In-Reply-To: <7soge44gux.fsf@os.inf.tu-dresden.de> from "Michael Hohmuth" at Oct 12, 99 07:40:54 pm
• Sender: owner-oskit-users@fast.cs.utah.edu

> 
> oskit-users,
> 
> after a painful build experience ("./configure --target=i386-oskit; make"?
> No way!)  and with a lot of help from some nice guys at Utah, I

FWIW, even in the "ideal" GNU world by some people's standards where everybody 
followed GNU standards, this wouldn't be the command to issue.  The --target 
option is only used to build cross-tools which have to be configured for a
given target.  For instance, if you build a cross-compiler for the
StrongARM architecture---no matter what architecture you're building
on and no matter what architecture the compiler will run on, you'd
say --target.

For instance,

	configure --build=hpux --host=i386 --target=strongarm

Builds on an HPUX machine a compiler which, when run on the i386,
will produce strongarm machine code.

For the OSKit, the right parameter would be --host=i386-oskit.
Granted, that probably doesn't work.  In part it's because other
people are as confused as you are about what --target means.
I'm not excluding myself, in fact, I'm very much including myself here.
Kaffe's configure at times uses $target_os when it really means $host_os.  
But we should fix that.

	- Godmar

• No luck with Kaffe
• From: Michael Hohmuth <hohmuth@innocent.com>

• Prev: Re: Overriding stuff from OSKit libs, some random remarks, and patches
• Next: Re: No luck with Kaffe
• Index(es):
  • Main
  • Thread