home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!att-out!rutgers!uwm.edu!wupost!sdd.hp.com!swrinde!network.ucsd.edu!sdcrsi!equalizer!timbuk.cray.com!shamash!ems!ems.cdc.com!dmcpheet
- From: dmcpheet@ems.cdc.com (Dennis McPheeters)
- Newsgroups: comp.unix.aix
- Subject: Re: xlc -M (or cc -M)
- Keywords: xlc cc -M
- Message-ID: <22125@nntp_server.ems.cdc.com>
- Date: 4 Sep 92 15:43:21 GMT
- References: <1992Sep3.203512.3164@unlinfo.unl.edu>
- Sender: sys@ems.ems.cdc.com
- Reply-To: dmcpheet@ems.cdc.com
- Organization: Empros Systems International, a division of CDC
- Lines: 25
- Nntp-Posting-Host: eurydice.ems.cdc.com
-
- In article <1992Sep3.203512.3164@unlinfo.unl.edu>, james@engrs.unl.edu (James Nau) writes:
- |> Does anyone know if cc -M is supposed to actually compile a
- |> program? I was building some software which has a "cc -M x.c y.c
- |> z.c >> Makefile" in it to build dependencies. It died a horrible
- |> death, and complained that it couldn't find .main (actually, this
- |> was in the Makefile since stdout was there).
- |> "cc -E -M x.c y.c z.c >/dev/null" seemed to work fairly well.
- |>
- |> Also, cc -M does not write to stdout as this Configure script
- |> expected (cc on Sun, and gcc write the dependencies to stdout) but
- |> writes to .u files. (This is documented in the help file.)
- |>
- |> James
- |> james@engrs.unl.edu
-
- I'm rather fond of the -M option, but I don't use it the way you do. I simply
- have an "include x.u" in my Makefile (I "touch" x.u when I add the include),
- and haven't had problems actually compiling. The -E option does produce stdout,
- but, as you noticed, -M doesn't.
-
- --
- Dennis R. McPheeters dmcpheet@ems.cdc.com >>>
- Empros Systems International __o (612) 553-4768 <<<
- 2300 Berkshire Lane North -\<, fax: (612) 553-4018 >>>
- Plymouth, MN 55441-3694 O/ O Software Tools <<<
-