public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
To: Brian Keener <bkeener@thesoftwaresource.com>
Cc: cygwin@cygwin.com
Subject: Re: g++ iostream broken on windows 2000
Date: Wed, 17 Sep 2003 17:18:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.56.0309171306220.12411@slinky.cs.nyu.edu> (raw)
In-Reply-To: <VA.00000e69.00588e37@thesoftwaresource.com>

On Wed, 17 Sep 2003, Brian Keener wrote:

> Robert Collins wrote:
> > > /usr/develop/src/learning
> > > $ gcc -g -o ./debug/first.exe ./first.cpp
> >
> > g++ !
> >
> > Oh, and in your output, get rid of the \n, use
> > cout << "foo" << endl;
>
> Thanks Rob,
>
> That was sort of a duh wasn't it.  I guess I need some more reading -
> gcc shows in man as the GNU C and C++ compiler and if I do a man g++ I
> get the manual for gcc or if I do man "g++".  Thought that was the right
> one - even though I have seen both.
>
> Off to the books.
> bk

Brian,

FYI (and to get this into the archives), if there's only one input source
file, you can simply use the default make rules, and they should do the
right thing, i.e., if you say "make first", it should invoke the right
compiler to process first.cpp (at least you'll see what the right compiler
is).  If you want to pass extra flags, try "make CXXFLAGS=-g CFLAGS=-g
first").  Putting the file in a different directory, as in your case, will
not be as easy, though...
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2003-09-17 17:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-15 23:43 Vijay Kumar
2003-09-15 23:53 ` Igor Pechtchanski
2003-09-16  0:01   ` Vijay Kumar
2003-09-16  0:07     ` Vijay Kumar
2003-09-16  4:10 ` Alex Vinokur
2003-09-16 22:44   ` Brian Keener
2003-09-16 23:13     ` Robert Collins
2003-09-17 16:27       ` Hannu E K Nevalainen (garbage mail)
2003-09-17 17:04       ` Brian Keener
2003-09-17 17:18         ` Igor Pechtchanski [this message]
2003-09-17 23:49           ` Brian Keener
2003-09-17  6:21     ` Alex Vinokur

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=Pine.GSO.4.56.0309171306220.12411@slinky.cs.nyu.edu \
    --to=pechtcha@cs.nyu.edu \
    --cc=bkeener@thesoftwaresource.com \
    --cc=cygwin@cygwin.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).