From: Jon Thackray <jont@harlequin.co.uk>
To: gnu-win32@cygnus.com
Subject: gcc problem
Date: Mon, 10 Mar 1997 04:11:00 -0000 [thread overview]
Message-ID: <4107.9703101210@dedekind.cam.harlequin.co.uk> (raw)
I am running gcc on two similar NT 3.51 machines. In each case, gcc is
invoked by a makefile line something like
.o.S
gcc -c $< -o $@
On one machine, it writes its object files to *.obj, and on the other,
it does as asked and writes to *.o
In both cases I'm using the beta-17 tools, indeed, one machine's
installation was produced by copying the other machine's. Any ideas
why I get this variation?
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next reply other threads:[~1997-03-10 4:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-10 4:11 Jon Thackray [this message]
1997-03-10 6:04 ` Jim Balter
1997-03-10 6:11 ` Jon Thackray
1997-10-20 3:21 Frank Packenham
1997-10-20 6:00 ` Fergus Henderson
1997-10-20 19:25 Colin Peters
1997-10-21 7:44 ` Steven J. Zeil
1997-10-23 7:26 Frank Packenham
2000-08-11 16:12 Consequator
2000-08-11 17:22 ` Chris Faylor
2000-08-12 3:37 ` Consequator
2001-07-27 10:14 gcc_Problem Mr.Serkan Gumusbicak
2001-07-27 11:50 ` gcc_Problem Carl Hetherington
2001-09-06 6:41 gcc problem Dominik Zalewski
2001-09-06 6:45 Peter Buckley
2001-09-06 7:17 ` Dominik Zalewski
2001-09-06 7:31 Peter Buckley
2001-09-06 7:36 ` Larry Hall (RFK Partners, Inc)
2001-12-14 11:11 GCC problem gahan
[not found] <Pine.LNX.4.33.0112142057150.7431-100000@heros.knurow.tpsa. pl>
2001-12-14 11:41 ` Larry Hall (RFK Partners, Inc)
2002-03-21 5:17 Mike Hayden
2002-03-21 5:26 ` David Starks-Browning
2002-03-21 5:39 Robert Collins
2003-09-14 21:00 gcc problem swa004
2004-03-02 12:49 Lauer Rainer
2004-03-02 12:53 ` Laurent Vaucher
2004-03-02 14:56 ` Gerrit P. Haase
2004-03-02 15:57 ` Gareth Pearce
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=4107.9703101210@dedekind.cam.harlequin.co.uk \
--to=jont@harlequin.co.uk \
--cc=gnu-win32@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).