Re: (Another) newbie problem

Re: (Another) newbie problem

[Jim Roy]

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 >

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

Re: (Another) newbie problem

[John R Hanson]

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
http://www.netzero.net/download/index.html

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

Re: (Another) newbie problem

[Chris Faylor]

On Wed, Sep 01, 1999 at 12:26:57AM +0000, John R Hanson wrote:
>Sadly because of the command line quoting issue that won't work.  Very
>Annoying!!

It is annoying that no one is willing to step forward and fix problems,
isn't it?  We seem to get a lot of complainers on this list and very few
people willing to pitch in and look into providing a fix.

What a shame.

-Chris Faylor
-Win32 Manager
-Cygnus Solutions

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

Re: (Another) newbie problem

[Mumit Khan]

JRSON@NetZero.Net (John R Hanson) writes:
> 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.

There will be some differences starting the next release. I 
just put the finishing touches on thread-safe C++ exceptions 
for Mingw, and that just won't work for "stock" Cygwin. Of
course, if you don't specify -mthreads option (which defines
-D_MT and adds in the thread-safe helper library), it'll be 
the same.

> 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.

Actually, there are other problems with this setup besides the
quoting issue -- the pathnames have to specially handled by
the driver before passing it on for example. UWIN folks do
this to drive MSVC and there's quite a bit of work to be done
(and I can still break it at will). If you can live with a 
little slowdown due to Cygwin overhead, why not just use a 
Cygwin hosted Mingw targeted toolchain (just install it somewhere 
else, and use PATH to switch to it)? As you can probably guess 
already, I have just the setup. In fact, I'm contemplating 
packaging it up (which takes a finite block of my time, hence 
the contemplation ;-) and putting it up for ftp.

> if you are using mingw32 gcc with -cygwin 
> (does anyone else do this but me?-)

Hey, I know of someone (trying to) build Linux kernel under Cygwin.
so there ;-)

Regards,
Mumit


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

Re: (Another) newbie problem

[Mumit Khan]

JRSON@NetZero.Net (John R Hanson) writes:
> 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.

There will be some differences starting the next release. I 
just put the finishing touches on thread-safe C++ exceptions 
for Mingw, and that just won't work for "stock" Cygwin. Of
course, if you don't specify -mthreads option (which defines
-D_MT and adds in the thread-safe helper library), it'll be 
the same.

> 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.

Actually, there are other problems with this setup besides the
quoting issue -- the pathnames have to specially handled by
the driver before passing it on for example. UWIN folks do
this to drive MSVC and there's quite a bit of work to be done
(and I can still break it at will). If you can live with a 
little slowdown due to Cygwin overhead, why not just use a 
Cygwin hosted Mingw targeted toolchain (just install it somewhere 
else, and use PATH to switch to it)? As you can probably guess 
already, I have just the setup. In fact, I'm contemplating 
packaging it up (which takes a finite block of my time, hence 
the contemplation ;-) and putting it up for ftp.

> if you are using mingw32 gcc with -cygwin 
> (does anyone else do this but me?-)

Hey, I know of someone (trying to) build Linux kernel under Cygwin.
so there ;-)

Regards,
Mumit


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

Re: (Another) newbie problem

[Jim Roy]

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 >

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

Re: (Another) newbie problem

[Chris Faylor]

On Wed, Sep 01, 1999 at 12:26:57AM +0000, John R Hanson wrote:
>Sadly because of the command line quoting issue that won't work.  Very
>Annoying!!

It is annoying that no one is willing to step forward and fix problems,
isn't it?  We seem to get a lot of complainers on this list and very few
people willing to pitch in and look into providing a fix.

What a shame.

-Chris Faylor
-Win32 Manager
-Cygnus Solutions

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

Re: (Another) newbie problem

[John R Hanson]

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
http://www.netzero.net/download/index.html

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

Re: (Another) newbie problem

[Earnie Boyd]

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 >

(If you respond to the list, then please don't cc me)
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com


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

Re: (Another) newbie problem

[Earnie Boyd]

Here's what I do:

dir:
c:\root\b20
c:\root\mingw32

Install cygwin related headers and libraries under c:\root\b20 in directories
usr/include, usr/lib, ... and install mingw32 related headers and libraries
under c:\root\mingw32 in directories usr/include, usr/lib, ... and also copy to
usr/bin any appropriate user binary; you know, bash, sh, cygwin1.dll, ls, etc. 
and put the binaries for gcc and binutils for mingw32 there also.  You'll need
to setup the GCC related environment variables such as GCC_EXEC_PREFIX, etc for
the mingw32 version of gcc to find it or just use the cygwin version of the gcc
and modify the specs file to make the -mno-cygwin the default.  

Now, in the cygnus.bat file add `sh -c 'cd usr/bin && ./umount / && ./mount
c:\\root\\mingw32 /'' for the mingw32 startup before starting bash and do the
same for the cygwin startup but instead of c:\\root\\mingw32 use c:\\root\\b20.
 Create a shortcut on your desktop for each of these naming one b20 and the
other mingw32.  Now, you've two separate environments.  One for cygwin, the
other for mingw32.

--- Jim Roy <jim@nga.com> 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 :-} ) 

It was obvious from the output of gcc -v supplied with the post.

> 
> Are you saying that *ALL* of the libraries, header files, & build
> tools come in separate flavors, one for cygwin and one for mingw32?
-8<-

All _cygwin_ related objects and libraries.  Mingw32 uses the runtime, the one
supplied by M$, and objects and libraries won't change for them.

I hope this helps.  Feel free to post any question.  Sorry if you felt that I
wasn't helpful enough earlier but this has been discussed many times before.
===
Earnie Boyd < mailto:earnie_boyd@yahoo.com >

Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >

(If you respond to the list, then please don't cc me)
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com


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

(Another) newbie problem

[Simon Gornall]

I've been strugling with cygwin for a while, not quite sure of
what I've been doing wrong. Anyway, I decided to download a
fresh B20.1 full.exe and install the tools from Mumit's site
to get myself a working gcc-2.95

I installed the mingw32 extras into /lib and /include and prefixed
the g++ arguments with -I/include or -L/lib as instructed

Having done that, I tried compiling a simple hello-world.cc
file and it worked fine.

Next I tried the real source code, and I'm getting the following
(full -v output, sorry about that :-)

c -v -g -mno-cygwin -g -I/include -I../gtk+/gdk/win32 -I../glib
-I../gtk+ -I../jpeg-6b    -DDEBUG -c main.cc -o main.o
Reading specs from
//E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/specs
gcc version 2.95 19990728 (release)

(so it's picking up the correct specs, I suppose. There is a directory
 ...i586-cygwin32/egcs-2.91.57/... as well, which I assume came from
full.exe)

 //E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/cpp.exe
-lang-c++ -v -I/include -I../gtk+/gdk/win32 -I../glib -I../gtk+
-I../jpeg-6b -iprefix
//E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/
-D__GNUC__=2 -D__GNUG__=2 -D__GNUC_MINOR__=95 -D__cplusplus -Di386
-D_WIN32 -DWINNT -D_X86_=1 -D__STDC__=1
-D__stdcall=__attribute__((__stdcall__))
-D__cdecl=__attribute__((__cdecl__)) -D__declspec(x)=__attribute__((x))
-D__i386__ -D_WIN32 -D__WINNT__ -D_X86_=1 -D__STDC__=1
-D__stdcall=__attribute__((__stdcall__))
-D__cdecl=__attribute__((__cdecl__)) -D__declspec(x)=__attribute__((x))
-D__i386 -D__WINNT -Asystem(winnt) -Acpu(i386) -Amachine(i386)
-D__EXCEPTIONS -g -g -remap -Acpu(i386) -Amachine(i386) -Di386 -D__i386
-D__i386__ -Di586 -Dpentium -D__i586 -D__i586__ -D__pentium
-D__pentium__ -iwithprefixbefore
../../../../i586-cygwin32/include/mingw32 -D__MINGW32__=0.2 -DDEBUG
main.cc C:\WINDOWS\TEMP/ccRvaaaa.ii
GNU CPP version 2.95 19990728 (release) (80386, BSD syntax)
#include "..." search starts here:
#include <...> search starts here:
 /include
 ../gtk+/gdk/win32
 ../glib
 ../gtk+
 ../jpeg-6b

//E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/../../../../i586-cygwin32/include/mingw32

//E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/../../../../../include/g++-3

//E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/../../../../../include

//E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/../../../../i586-cygwin32/include
 //E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/include
End of search list.
The following default directories have been omitted from the search
path:
 /usr/include
End of omitted list.

//E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/cc1plus.exe
C:\WINDOWS\TEMP/ccRvaaaa.ii -quiet -dumpbase main.cc -mno-cygwin -g -g
-version -o C:\WINDOWS\TEMP/ccyRaaaa.s
GNU C++ version 2.95 19990728 (release) (i586-cygwin32) compiled by GNU
C version 2.95 19990728 (release).
In file included from
//E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/../../../../i586-cygwin32/include/asm/socket.h:4,
                 from
//E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/../../../../i586-cygwin32/include/cygwin/socket.h:13,
                 from
//E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/../../../../i586-cygwin32/include/sys/socket.h:5,
                 from Fetcher.h:28,
                 from main.cc:9:
//E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/../../../../i586-cygwin32/include/cygwin/if.h:63:
syntax error before `;'
make: *** [main.o] Error 1

The line in question uses caddr_t, which is supposed to be set by
<sys/types.h> which 
I had already included, but I inserted it again before any other
include, unfortunately
this made no difference :-(

Presumably I've installed things in the wrong place somewhere. The
problem is that
there are so many places where include files go, that I'm not sure where
to start
looking... Any help about what I've done wrong appreciated.

ATB,	
Simon.

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

Re: (Another) newbie problem

[Earnie Boyd]

--- Mumit Khan <khan@xraylith.wisc.EDU> wrote:
> Actually, there are other problems with this setup besides the
> quoting issue -- the pathnames have to specially handled by
> the driver before passing it on for example. UWIN folks do
> this to drive MSVC and there's quite a bit of work to be done
> (and I can still break it at will). If you can live with a 
> little slowdown due to Cygwin overhead, why not just use a 
> Cygwin hosted Mingw targeted toolchain (just install it somewhere 
> else, and use PATH to switch to it)? As you can probably guess 
> already, I have just the setup. In fact, I'm contemplating 
> packaging it up (which takes a finite block of my time, hence 
> the contemplation ;-) and putting it up for ftp.

I don't have to change the PATH with my setup, I just do an effective change
root command.  I use all cygwin tools with the mingw32 compiler/binutils set
and giving the appropriate paths to the appropriate environment variables.  I
have never ever, as I'm sure that Mumit hasn't either, had a conflict of
headers and libraries.  Keep the two sets separated in there own world and you
won't have a problem.

BTW: This setup allows me to install a snapshot for testing without disturbing
what I know already works.
===
Earnie Boyd < mailto:earnie_boyd@yahoo.com >

Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >

(If you respond to the list, then please don't cc me)
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com


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

Re: (Another) newbie problem

[Simon Gornall]

Earnie Boyd wrote:
> 
> Here's what I do:
>
[useful stuff snipped]

Thanks, I'll give it a whirl and see how it goes. Perhaps this
should be on a FAQ somewhere ? The existing docs (while useful,
definately essential!) aren't quite enough to get going, I think.

I'm hardly a beginner to Unix etc. but unless you have some idea
where things should go in the first place, it's pretty difficult
to make use of the output of 'gcc -v'. As mentioned in the docs, 
it's a problem when (because something is missing in mingw32) a 
file is picked up in cygwin32 when it shouldn't be. This in fact 
was my problem I think. That and a miniscule knowledge of how to
program under windows...

Of course, a *really* useful resource would be a tarball of a
working setup for mingw32 (the cygwin full.exe presumably fits
the bill for the cygwin environment :-). Such that you d/l and
install full.exe, then d/l and extract mingw32.tar.gz on top of
it.

If anyone wants to contribute one, I'd gladly host it on the web.
I'd do it myself, but mine doesn't work :-(

ATB,
        Simon.

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

Re: (Another) newbie problem

[Earnie Boyd]

--- Mumit Khan <khan@xraylith.wisc.EDU> wrote:
> Actually, there are other problems with this setup besides the
> quoting issue -- the pathnames have to specially handled by
> the driver before passing it on for example. UWIN folks do
> this to drive MSVC and there's quite a bit of work to be done
> (and I can still break it at will). If you can live with a 
> little slowdown due to Cygwin overhead, why not just use a 
> Cygwin hosted Mingw targeted toolchain (just install it somewhere 
> else, and use PATH to switch to it)? As you can probably guess 
> already, I have just the setup. In fact, I'm contemplating 
> packaging it up (which takes a finite block of my time, hence 
> the contemplation ;-) and putting it up for ftp.

I don't have to change the PATH with my setup, I just do an effective change
root command.  I use all cygwin tools with the mingw32 compiler/binutils set
and giving the appropriate paths to the appropriate environment variables.  I
have never ever, as I'm sure that Mumit hasn't either, had a conflict of
headers and libraries.  Keep the two sets separated in there own world and you
won't have a problem.

BTW: This setup allows me to install a snapshot for testing without disturbing
what I know already works.
===
Earnie Boyd < mailto:earnie_boyd@yahoo.com >

Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >

(If you respond to the list, then please don't cc me)
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com


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

Re: (Another) newbie problem

[Simon Gornall]

Earnie Boyd wrote:
> 
> Here's what I do:
>
[useful stuff snipped]

Thanks, I'll give it a whirl and see how it goes. Perhaps this
should be on a FAQ somewhere ? The existing docs (while useful,
definately essential!) aren't quite enough to get going, I think.

I'm hardly a beginner to Unix etc. but unless you have some idea
where things should go in the first place, it's pretty difficult
to make use of the output of 'gcc -v'. As mentioned in the docs, 
it's a problem when (because something is missing in mingw32) a 
file is picked up in cygwin32 when it shouldn't be. This in fact 
was my problem I think. That and a miniscule knowledge of how to
program under windows...

Of course, a *really* useful resource would be a tarball of a
working setup for mingw32 (the cygwin full.exe presumably fits
the bill for the cygwin environment :-). Such that you d/l and
install full.exe, then d/l and extract mingw32.tar.gz on top of
it.

If anyone wants to contribute one, I'd gladly host it on the web.
I'd do it myself, but mine doesn't work :-(

ATB,
        Simon.

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

Re: (Another) newbie problem

[Earnie Boyd]

Here's what I do:

dir:
c:\root\b20
c:\root\mingw32

Install cygwin related headers and libraries under c:\root\b20 in directories
usr/include, usr/lib, ... and install mingw32 related headers and libraries
under c:\root\mingw32 in directories usr/include, usr/lib, ... and also copy to
usr/bin any appropriate user binary; you know, bash, sh, cygwin1.dll, ls, etc. 
and put the binaries for gcc and binutils for mingw32 there also.  You'll need
to setup the GCC related environment variables such as GCC_EXEC_PREFIX, etc for
the mingw32 version of gcc to find it or just use the cygwin version of the gcc
and modify the specs file to make the -mno-cygwin the default.  

Now, in the cygnus.bat file add `sh -c 'cd usr/bin && ./umount / && ./mount
c:\\root\\mingw32 /'' for the mingw32 startup before starting bash and do the
same for the cygwin startup but instead of c:\\root\\mingw32 use c:\\root\\b20.
 Create a shortcut on your desktop for each of these naming one b20 and the
other mingw32.  Now, you've two separate environments.  One for cygwin, the
other for mingw32.

--- Jim Roy <jim@nga.com> 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 :-} ) 

It was obvious from the output of gcc -v supplied with the post.

> 
> Are you saying that *ALL* of the libraries, header files, & build
> tools come in separate flavors, one for cygwin and one for mingw32?
-8<-

All _cygwin_ related objects and libraries.  Mingw32 uses the runtime, the one
supplied by M$, and objects and libraries won't change for them.

I hope this helps.  Feel free to post any question.  Sorry if you felt that I
wasn't helpful enough earlier but this has been discussed many times before.
===
Earnie Boyd < mailto:earnie_boyd@yahoo.com >

Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >

(If you respond to the list, then please don't cc me)
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com


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

Re: (Another) newbie problem

[Earnie Boyd]

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 >

(If you respond to the list, then please don't cc me)
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com


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

(Another) newbie problem

[Simon Gornall]

I've been strugling with cygwin for a while, not quite sure of
what I've been doing wrong. Anyway, I decided to download a
fresh B20.1 full.exe and install the tools from Mumit's site
to get myself a working gcc-2.95

I installed the mingw32 extras into /lib and /include and prefixed
the g++ arguments with -I/include or -L/lib as instructed

Having done that, I tried compiling a simple hello-world.cc
file and it worked fine.

Next I tried the real source code, and I'm getting the following
(full -v output, sorry about that :-)

c -v -g -mno-cygwin -g -I/include -I../gtk+/gdk/win32 -I../glib
-I../gtk+ -I../jpeg-6b    -DDEBUG -c main.cc -o main.o
Reading specs from
//E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/specs
gcc version 2.95 19990728 (release)

(so it's picking up the correct specs, I suppose. There is a directory
 ...i586-cygwin32/egcs-2.91.57/... as well, which I assume came from
full.exe)

 //E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/cpp.exe
-lang-c++ -v -I/include -I../gtk+/gdk/win32 -I../glib -I../gtk+
-I../jpeg-6b -iprefix
//E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/
-D__GNUC__=2 -D__GNUG__=2 -D__GNUC_MINOR__=95 -D__cplusplus -Di386
-D_WIN32 -DWINNT -D_X86_=1 -D__STDC__=1
-D__stdcall=__attribute__((__stdcall__))
-D__cdecl=__attribute__((__cdecl__)) -D__declspec(x)=__attribute__((x))
-D__i386__ -D_WIN32 -D__WINNT__ -D_X86_=1 -D__STDC__=1
-D__stdcall=__attribute__((__stdcall__))
-D__cdecl=__attribute__((__cdecl__)) -D__declspec(x)=__attribute__((x))
-D__i386 -D__WINNT -Asystem(winnt) -Acpu(i386) -Amachine(i386)
-D__EXCEPTIONS -g -g -remap -Acpu(i386) -Amachine(i386) -Di386 -D__i386
-D__i386__ -Di586 -Dpentium -D__i586 -D__i586__ -D__pentium
-D__pentium__ -iwithprefixbefore
../../../../i586-cygwin32/include/mingw32 -D__MINGW32__=0.2 -DDEBUG
main.cc C:\WINDOWS\TEMP/ccRvaaaa.ii
GNU CPP version 2.95 19990728 (release) (80386, BSD syntax)
#include "..." search starts here:
#include <...> search starts here:
 /include
 ../gtk+/gdk/win32
 ../glib
 ../gtk+
 ../jpeg-6b

//E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/../../../../i586-cygwin32/include/mingw32

//E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/../../../../../include/g++-3

//E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/../../../../../include

//E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/../../../../i586-cygwin32/include
 //E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/include
End of search list.
The following default directories have been omitted from the search
path:
 /usr/include
End of omitted list.

//E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/cc1plus.exe
C:\WINDOWS\TEMP/ccRvaaaa.ii -quiet -dumpbase main.cc -mno-cygwin -g -g
-version -o C:\WINDOWS\TEMP/ccyRaaaa.s
GNU C++ version 2.95 19990728 (release) (i586-cygwin32) compiled by GNU
C version 2.95 19990728 (release).
In file included from
//E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/../../../../i586-cygwin32/include/asm/socket.h:4,
                 from
//E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/../../../../i586-cygwin32/include/cygwin/socket.h:13,
                 from
//E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/../../../../i586-cygwin32/include/sys/socket.h:5,
                 from Fetcher.h:28,
                 from main.cc:9:
//E/GNU/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/2.95/../../../../i586-cygwin32/include/cygwin/if.h:63:
syntax error before `;'
make: *** [main.o] Error 1

The line in question uses caddr_t, which is supposed to be set by
<sys/types.h> which 
I had already included, but I inserted it again before any other
include, unfortunately
this made no difference :-(

Presumably I've installed things in the wrong place somewhere. The
problem is that
there are so many places where include files go, that I'm not sure where
to start
looking... Any help about what I've done wrong appreciated.

ATB,	
Simon.

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