Re: name of cc in the renamed rumprun toolchain

  • From: Martin Lucina <martin@xxxxxxxxxx>
  • To: rumpkernel-users@xxxxxxxxxxxxx
  • Date: Fri, 3 Jul 2015 11:59:03 +0200

On Thursday, 02.07.2015 at 21:52, Antti Kantee wrote:

On 02/07/15 15:50, Martin Lucina wrote:
If so, should we keep -cc as an alias for -gcc, so as to simplify
instructions to not always have to contain "if you want to use gcc,
set CC to -gcc, if you want to use clang, set CC to -clang"?

The instructions can just say "set CC to the rumprun cross compiler you
built" or similar, I'd not bother enumerating the possibilities.

That adds a level of complication as opposed to just building
software for the host. If you run build-rr without setting CC, you
now have to know if your cc is gcc or clang. I assume most people
are like me: don't care what cc is as long as it produces runnable

Ok, if we want the easiest possible "out of the box" experience for
newbies, then I have a better idea:

- introduce a helper script / / whatever, called

- This script either just uses $RUMPRUN_PLATFORM if set, setting $CC /
$HOST appropriately

- If $RUMPRUN_PLATFORM is not set, it goes hunting for
*-rumprun-netbsd*-gcc on $PATH. If it finds a *single* toolchain, it uses
that automatically.

- If it does not find a toolchain, it complains.

How does that sound?

Of course, you do need to know if you're on 32bit or 64bit, but for
that 64bit is a reasonable default. I doubt that anyone will be
building on non-x86 in a tutorial context.

Fair enough.

Other related posts: