CODEWITHSUNDEEP
compilationmipscross-compilingnetbsd
user2882307
user2882307

Reputation:

compile simple hello-world c program for mips netbsd

the last week I have been trying to set-up a compiler which can compile to netbsd with mips architecture.

I cannot find anything on the internet how to do this. All documents refer to compiling the kernel to the architecture but not programs.

How can this be so hard....

host is netbsd amd64 machine

Upvotes: 1

Views: 782

Answers (2)

Kuba hasn't forgotten Monica
Kuba hasn't forgotten Monica

Reputation: 98425

Generally speaking, the goal is to have a working cross-compiler and a filesystem root for the target, all installed on your development machine. The target root is needed since you need all sorts of libraries to build userland applications. Those libraries need to be compiled for the target, not for the host.

Assuming you build everything from source, it goes as follows:

  1. Choose a prefix for the toolchain (say /opt/mips) and another prefix for the root filesystem of the target (say /opt/target). All of those are on your development machine, not on the target!

  2. Configure, build and install the cross-compiler for your target. This goes into the toolchain prefix.

  3. Configure, build and install the kernel for your target, into the target root prefix. This should install the necessary kernel development headers needed later. If you can install such headers without compiling the kernel, more power to you, of course.

  4. Configure, build and install the C library (say glibc) for your target, into the target root.

  5. Configure, build and install whatever other libraries your userland application needs - into the target root.

  6. Finally, configure, build and install the userland application. Once installed into the target root, you can copy it over to the target into the same prefix (say /opt/target as suggested before).

    Generally to install into a different prefix - one that overlaps stuff on your build host (like /usr) - you'd need to do some tricks to fool make install into seeing the target prefix instead of your own. A simple approach would be to have a chroot environment on your build host, where you can bind-mount the prefix (say /usr) read-only, with a writable (mount_union) overlay on top of it.

When you build stuff for the target, you need to pass proper arguments to configure, of course.

Upvotes: 0

Eric Schnoebelen
Eric Schnoebelen

Reputation: 86

Set the compiler appropriately. Point it at the version of gcc in your TOOLDIR. In this case, something like mips--netbsd-gcc. Definitely make sure TOOLDIR is on your path, so the driver can find the proper assembler, proper loader, and proper libraries.

Take a look at the Makefile in any of src/bin/* as an example, and read through the system mk include files referenced (in src/share/mk)

Upvotes: 1

Related Questions