(Another) newbie problem

John R Hanson JRSON@NetZero.Net
Tue Aug 31 17:31:00 GMT 1999

No, The compiler and binutils produce and use
the same input/output whether you are compiling
for mingw32 or cygwin. Only the startup files,
libraries and (some) include files need to be kept separate.

The ideal setup would be the cygwin gcc/++.exe compiler driver
and the mingw32 compiler and binutils
That way you could use symlinks where needed. And still have
the fast compiler, and tools.

Sadly because of the command line quoting 
issue that won't work. Very Annoying!!

Libraries and (libc) include files MUST be different
and installed into different directories.

-nostdinc and -nostandlib MUST be used in the
nondefault compiler.

if you are using cygwin gcc with -mno-cygwin
and getting errors about _reent then you are
compiling with the cygwin headers.

if you are using mingw32 gcc with -cygwin 
(does anyone else do this but me?-)
and getting undefined link errors or
conflicting type errors on common functions
then you are picking up the cygwin headers.

gcc --help;            will tell you a lot
gcc -v --help;        will probably overwhelm you ;-)
gcc (opt) -print-search-dirs;     will show where programs includes and libs are being searched
gcc (opt) -c -H file.c -o file.o;     will show headers included by file.c
echo|gcc (opt) -E -dM -;      will show you what macros are predefined with that opt's

On Tue, 31 Aug 99 11:57:22 PDT, you wrote:

>Lighten up Earnie.
>A lot of us are in the same boat.  This stuf is complex.  I've
>read a lot of web pages and even got a couple of  projects to
>build and work.  Still, it's not *obvious* to me that he's mixing
>Ming32 and Cygwin.  I'm not sure I even know exactly what that means.
>( May be why some stuf I try still doesn't work :-} ) 
>Are you saying that *ALL* of the libraries, header files, & build
>tools come in separate flavors, one for cygwin and one for mingw32?
>That when building mingw pgms, the only part of the cygwin package
>one should be using is the shell & shell tools?
>That's the picture
>I have, but I'm not completely sure I have it set up that way.  One
>set of docs says to dump the mingw stuf in a particular directory
>and the compiler will find the runtime automatically, and another doc
>says to install in a separate place and point to it with -I & -L flags.
>Don't get me wrong, I'm not trying to be critical of these great
>tools, or the documentation either for that matter, just this
>reply.  If you are just going to tell someone to RTFM, ( especially
>someone who obviously already has R'd a lot of TFM )
>why post it to the list?  You are the expert here, #include a little
>insite with the chastisement.
>Jim Roy                      voice  541 757 7231
>Sys. Admin.                  fax    541 757 7331
>NW Geophysical Assoc.        http://www.nga.com
>Corvallis Or. US
>> From: Earnie Boyd <earnie_boyd@yahoo.com>
>> Go back to Mumit's site and read it.  You can't mix Mingw32 and Cygwin which
>> you've obviously done.  You might want to read my site as well.
>> ===
>> Earnie Boyd < mailto:earnie_boyd@yahoo.com >
>> Newbies, please visit
>> < http://www.freeyellow.com/members5/gw32/index.html >

NetZero - We believe in a FREE Internet.  Shouldn't you?
Get your FREE Internet Access and Email at

Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

More information about the Cygwin mailing list