From: Simon Gornall <simon@unique-id.com>
To: cygwin mailing list <cygwin@sourceware.cygnus.com>
Subject: Re: (Another) newbie problem
Date: Tue, 31 Aug 1999 16:55:00 -0000 [thread overview]
Message-ID: <37CC6BEC.67082C4B@unique-id.com> (raw)
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
WARNING: multiple messages have this Message-ID
From: Simon Gornall <simon@unique-id.com>
To: cygwin mailing list <cygwin@sourceware.cygnus.com>
Subject: Re: (Another) newbie problem
Date: Tue, 31 Aug 1999 23:49:00 -0000 [thread overview]
Message-ID: <37CC6BEC.67082C4B@unique-id.com> (raw)
Message-ID: <19990831234900.k5AP9h4-9Lw64_cPCqHl8zkUjB9N-rkHp04PGZxBZuo@z> (raw)
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
next reply other threads:[~1999-08-31 16:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-31 16:55 Simon Gornall [this message]
1999-08-31 23:49 ` Simon Gornall
-- strict thread matches above, loose matches on Subject: below --
1999-08-31 18:57 Earnie Boyd
1999-08-31 23:49 ` Earnie Boyd
1999-08-31 12:29 Earnie Boyd
1999-08-31 23:49 ` Earnie Boyd
1999-08-31 11:57 Jim Roy
1999-08-31 17:31 ` John R Hanson
1999-08-31 17:57 ` Chris Faylor
1999-08-31 23:49 ` Chris Faylor
1999-08-31 18:01 ` Mumit Khan
1999-08-31 23:49 ` Mumit Khan
1999-08-31 23:49 ` John R Hanson
1999-08-31 23:49 ` Jim Roy
1999-08-31 10:15 Earnie Boyd
1999-08-31 23:49 ` Earnie Boyd
1999-08-31 9:59 Simon Gornall
1999-08-31 23:49 ` Simon Gornall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37CC6BEC.67082C4B@unique-id.com \
--to=simon@unique-id.com \
--cc=cygwin@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).