CROSS_COMPILE specifies the prefix used for all executables used during compilation. Only gcc and related binutils executables are prefixed with $(CROSS_COMPILE) in the makefiles. CROSS_COMPILE can be set on the command line: make CROSS_COMPILE=arm-linux-uclibcgnueabi- Alternatively CROSS_COMPILE can be set in the environment. Default value for CROSS_COMPILE is not to prefix executables.

Basically, you have to download the same source version compiler as the one on your OS X box, build it on you Linux PC, etc. The assembler now works on Linux as well, so that other issue you had should be moot. That is, you should compile the Apple source on your non-Apple machine. Apple have some patches that are not in the upstream gcc release so a compiler built from the gnu.org source will not be compatible.

BusyBox is a package that replaces a dozen standard packages, but it is not by itself a complete bootable system. Building an entire Linux distribution from source is a bit beyond the scope of this FAQ, but it understandably keeps cropping up on the mailing list, so here are some pointers. Start by learning how to strip a working system down to the bare essentials needed to run one or two commands, so you know what it is you actually need.

A : If you want a cross-compiler for m68k on a DOS machine, you need is DJGPP configured as host=i386-go32, and target=m68k-coff. This has been done already. The binaries there are based on GCC 2.6.0. This package is reportedly no longer supported, but if you have questions about it, you can send them to Jim Karpinski. For building GCC as a Unix-to-DOS cross-compiler, here are the instructions on how to do it.

If using Borland C++ 3.11, the project files I used to make the library are supplied in the zip file, so you should be able to just build it. Set the Make options so it runs the librarian instead of running the ordinary linker. The librarian makes a LIB instead of an EXE. If all goes well, you will have produced a new graphapp.lib file for use with your compiler. If all doesn't go well, forget it and use the next method instead.

On the Macintosh, you can only use the g++ compiler. All examples use this compiler. If you type 'g++' inside a 'Terminal' and it gives some output, then it is already installed. If the command is not found, then you should download it together with ProjectBuilder or Xcode, which are nice graphical editors (IDE's). On Windows, the only supported compiler is Microsoft C++ (5 or higher), though a lot of people have worked with all kinds of other compilers succesfully as well.

In theory, any ANSI C compiler can be used to build WinBinder. LCC-Win32, by Jacob Navia, is the standard compiler. MS Visual Studio was already tested successfully. MinGW and Pelles C worked with variable degrees of success. Other target compilers include Dev-C++ and Digital Mars . Please contact me if you want to use a compiler other than LCC-Win32 so I can help you.

Yes. Thanks to everyone who has contributed to this one. There is a HOWTO by Markus Hitter (hitterm@trier.fh-rpl.de) located at: http://www.macbsd.com/macbsd/howto/cc-HOWTO Also, Alan Palmer (hawks@mcs.com) has setup a cross-compiler for Solaris 2.4. It can be found at: ftp://ftp.macbsd.com/pub/NetBSD/contrib/cross-compiling/ Although the above HOWTO's might be slightly out of date, work is ongoing to make it easier to cross-compile NetBSD on other platforms.

If you do a build on a system without the cross compiler, it will be built for you as part of the build.

Yes, the Mainsoft for Java EE cross compiler handles delegates, generics, multi-dimensional arrays, nullable types, unsigned types, structs, enums, boxing, etc. It also maps the basic .NET types to the Java Virtual Machine built-in types (e.g. System.Object maps to java.lang.Object) in order to take full advantage of the Java VM capacities.

Busybox is configured similarly to the linux kernel. Create a default configuration and then run "make menuconfig" to modify it. The end result is a .config file that tells the busybox build process what features to include. So instead of "./configure; make; make install" the equivalent busybox build would be "make defconfig; make; make install". Busybox configured with all features enabled is a little under a megabyte dynamically linked on x86.

Busybox aims to be the smallest and simplest correct implementation of the standard Linux command line tools. First and foremost, this means the smallest executable size we can manage. We also want to have the simplest and cleanest implementation we can manage, be standards compliant, minimize run-time memory usage (heap and stack), run fast, and take over the world.

Busybox is like a swiss army knife: one thing with many functions. The busybox executable can act like many different programs depending on the name used to invoke it. Normal practice is to create a bunch of symlinks pointing to the busybox binary, each of which triggers a different busybox function. (See getting started in the FAQ for more information on usage, and the busybox documentation for a list of symlink names and what they do.

The following login accounts currently exist on busybox.net. (I.E. these people can commit patches into subversion for the BusyBox, uClibc, and buildroot projects.) aldot :Bernhard Fischer andersen :Erik Andersen - uClibc and BuildRoot maintainer.

Sun WorkShop 5.0 was the first compiler from Sun to generate 64-bit code. The latest WorkShop compiler is now part of the Sun Studio line of developer tools. Using the Forte (WorkShop) C compiler, you specify the instruction set architecture (ISA) using -xarch. xarch=v9a adds the Visual Instruction Set (VIS) and extensions specific to UltraSPARC processors to the SPARC-V9 ISA, and enables the compiler to generate code for good performance on the V9 SPARC architecture.

The problem is not in PAPI, but in libpfm 3.x. When this library is built using icc, the file pfmlib_gen_ia64.c generates a series of errors. One workaround for this may be to make the libpfm library separately using gcc and then build PAPI with icc. Or just use gcc. PAPI requires your Linux kernel to be patched with the PerfCtr patch. For compatability reasons, we have included this patch here. You should patch your kernel using the PerfCtr distribution found in the papi/src/perfctr directory.

of this fall, all Linux machines should use Fedora Core 2, where the system compiler is gcc 3.3.3. This is a fairly cutting-edge gcc and should handle most modern C/C++ code. On Solaris 2.5, the supported GNU C compiler is much older and buggier and should not be used; use the version in /uns if at all possible. Please note that various versions of gcc/g++ (particularly, though not limited to, 2.x and 3.x lines) may use mutually incompatible C++ object ABI's.

If you are using a project, then add the missing package to the project. Another option is to add the classpaths that you need using the standard or custom classpaths dialog. Still another option is to add the classpath to your CLASSPATH environment variable and turn on the option "use environment classpath" in JDK/Edit Options... dialog. You also need to be sure that your source files are in the proper directory. For example, Java expects the goo.

Unfortunately we are not staffed to provide answers to these types of questions. Many of these questions are answered in The Java Tutorial. You can also try the Java Technologies for Web Services at the JDC. By the way, we tested all of the examples in the book on Suns, and PCs. The examples work for us. If you are having problems with the examples, then you are probably having configuration problems. We get a fair number of messages to our e-mail address, users@jwsdp.dev.java.