Be sure that your build directory is mounted such that it has the same path either as a cygwin path ('/build/xemacs') or as a Windows path ('c:\build\xemacs'). Specify the target location of the extra libs on the command line to 'configure', e.g.for 21.4 or earlier './configure --site-prefixes=/build/libs i586-pc-mingw32' and for 21.5 or later './configure --with-site-prefixes=/build/libs i586-pc-mingw32'.

Yes. Hanzac has provided support for using MinGW to compile the FD32 kernel and drivers under a Windows platform. Although it should work, we have not tried to compile FreeDOS-32 with Cygwin: please let us know if Cygwin is working for you. [Contents]

For those who would like to use the Cygwin environment for development, yet generate non-Cygwin-dependant executables, a much easier option to "-mno-cygwin" does exist. Simply install Cygwin and the MinGW distribution in seperate directories (i.e. "C:\CYGWIN" and "C:\MINGW"), and make sure that the "/bin" subdirectory beneath your MinGW installation comes before Cygwin's "/bin" subdirectory in your PATH environment variable (i.e. "PATH=%PATH%;C:\MINGW\BIN;C:\CYGWIN\BIN").

Many "hardened" systems (eg. SSP/ProPolice) interfere with the way QEMU does dynamic code generation. The general solution is to disable these systems for QEMU. The QEMU design involves generating and running code on the fly, so it's unlikely these would provide any meaningful protection anyway. gcc-config -l (shows you a list of available cc) gcc-config i686-pc-linux-gnu-3.3.6-hardenednopiessp (use the correct version) source /etc/profile emerge qemu-cvs gcc-config i686-pc-linux-gnu-3.3.

MinGW ("Minimalistic GNU for Windows") refers to a set of runtime headers, used in building a compiler system based on the GNU GCC and binutils projects. It compiles and links code to be run on Win32 platforms... providing C, C++ and Fortran compilers plus other related tools. If you see references to "mingw32" instead of "MinGW", they are referring to the same compiler system.

The simplest way is to compile them all together with one command line, so for example if your program is made up of testharness.cpp and assignment.cpp, then you could compile them as follows: If any of these were particularly large, or if there were several implementation files, then you might consider compiling and linking separately:

I have set up /etc/nis.conf, and the Linux libc 5 with NYS works great. But the glibc NIS+ doesn't seem to work. Under Linux/Alpha, I always get "do_ypcall: clnt_call: RPC: Unable to receive; errno = Connection refused" when using NIS.

Unconfirmed) The Cygwin version doesn't understand '//machine/path' type paths so you will need to manually mount a directory of this form under a unix style directory for a build to work on the directory; If you're building WITHOUT X11, don't forget to change symlinks '/usr/lib/libXpm.a' and '/usr/lib/libXpm.dll.a' to point to the non-X versions of these libraries. By default they point to the X versions. So: This advice may now be obsolete because of the availability of the cygXpm-noX4.

I'm using RedHat Linux 5.0, or some other glibc-based Linux system, and I get errors with the crypt function when I attempt to build Apache 1.2.

Cygwin tools are, in the words of the Cygwin homepage, "ports of the popular GNU development tools and utilities for Windows 95, 98, and NT. They function by using the Cygwin library which provides a UNIX-like API on top of the Win32 API." Cygwin provides the compiler (gcc), libraries, headers, and other utilities which build and support the operation of Cygwin/X.

When Colin Peters released the MinGW runtime he placed the source into the public domain. No one owns a copyright (C) to the source because of this. You as a software manufacturer are free to use the MinGW runtime in your proprietary and OpenSource software as you see fit. The only thing you can't do is to claim ownership of the source and use Colin Peters' name, the MinGW name or the name of any of it's contributors in endorsement of any product.

The current version of BENV does not support from working within the CYGWIN or MSYS environments. The problem is how these environments handle the file system root/C drive issue. BENV support for CYGWIN and MSYS is planned, but has not yet been completed.

To answer the second part of the question: No, you, you don't need Cygwin or MinGW to build or to run XEmacs. But if you have them and want to use them, XEmacs supports these environments. One important reason to support Cygwin is that it lets the MS Windows developers test out their code in a Unix environment without actually having to have a Unix machine around. For this reason alone, Cygwin support is likely to remain supported for a long time in XEmacs.

I have installed the lucene package for my distribution but after looking at the config.log for libferris it is not properly detecting it.

The Cygwin gcc compiler port seems to use the same object file format as Microsoft's Visual C/C++ compiler. So the Microsoft examples should work with the Cygwin compiler. One person has confirmed that it does, but I have not installed the Cygwin compiler to confirm this myself.

The -mno-cygwin flag to gcc makes gcc link against standard Microsoft DLLs instead of Cygwin. This is desirable for native Windows programs that don't need a UNIX emulation layer. This is not to be confused with 'MinGW' (Minimalist GNU for Windows), which is a completely separate effort. That project's home page is http://www.mingw.org/index.shtml.

When using the db-2 library which comes with glibc is used in the Perl db modules the testsuite is not passed. This did not happen with db-1, gdbm, or ndbm. The pow() inline function I get when including <math.h> is broken. I get segmentation faults when I run the program.

It's easy to configure an MSYS environment for MinGW useage, since there is no overlap in functionality to contend with (as there is with Cygwin). Simply decompress the contents of each archive into directories of your choosing, and add the MinGW "/bin" subdirectory to your PATH (either within MSYS's " /etc/profile" or in your overall system PATH). There is no need to add MSYS's "/bin" to your system PATH.

Interestingly, that one's clear-cut. It's absolutely illegal. The Supreme Court decision Halter v Nebraska way back in 1907 held that you can't use the flag in advertising. Other cases have upheld that commercial speech doesn't have the same protection as political speech. So the Republican Party, which uses flags printed on its letterhead, is in clear violation of the Flag Protection Act of 1989, as well as all the other state and federal laws against flag desecration.

Unfortunately, this will be difficult. Exception handling and signals support semantics and args have been designed for x86 so you would need to write specific support for your platform. We don't know of any other incompatibilities. Please send us patches if you do this work!

GCC is the C compiler provided free to the computer community by GNU. It is the compiler of choice for working with muds on a Unix system, and recently has become available for Microsoft Windows 95 and NT in the Cygnus package. If your system has gcc installed, you are strongly advised to use it for your compilation needs, as it provides a much more coherent and solid base than do some standard unix based 'cc' compilers.

Assume we have a testdll.h, testdll.c, and testmain.c. In the first case, we will compile testdll.c with MinGW, and let the MSVC-compiled testmain call it. You should use gcc -shared -o testdll.dll testdll.c \ to produce the DLL and DEF files. MSVC cannot use the MinGW library, but since you have already the DEF file you may easily produce one by the Microsoft LIB tool: lib /machine:i386 /def:testdll.def Once you have testdll.lib, it is trivial to produce the executable with MSVC: cl testmain.