From: Louis Marascio <lmarasci@stevens-tech.edu>
To: egcs@cygnus.com
Subject: Re: Environment variable to pass in options?
Date: Sun, 07 Dec 1997 19:22:00 -0000 [thread overview]
Message-ID: <XFMail.971207222330.lmarasci@stevens-tech.edu> (raw)
In-Reply-To: <19971207211054.34491@dgii.com>
>SCO has had a similar feature in their tools for a long time. You can
>stuff things in environmental flags or in /etc/default/cc.
>
>I thoroughly hate this feature for the very reason Jeff describes.
>I have people constantly asking me "why does the compiler do XXX"
>and I spend a while beating on it and say, "it doesn't". They
>send a test case and say, "does too". I test their test case and
>say, "does not". This is when they find out the system admin or
>some other coworker added '-Obazillion -UseSomeEsotericThing' to
>one of the above places and that's causing the wierdness.
>
>Yes, I sometimes wish my compile lines would fit on a single 80 column
>screen to increase the density of my 'make' output. But after a couple
>rounds of playing the above game, I get over it.
Chuckle, sounds like a pain. There are, however, some instances when it could
be helpful :) .. atleast from my perspective. Compile options might be making
my needs to generalized. What I really want is some way to specify a path or
set of paths that would have the same effect as having a bazillion -Isomedir in
my compile line. I tried each of these to no avail: CPATH, C_INCLUDE_PATH, and
CPLUS_INCLUDE_PATH. Anything else I could possibly try? :)
- - - - -
Louis R. Marascio A.K.A Louis Armistead and Jim McCraken
Email: lmarasci@stevens-tech.edu "We have plenty of psychological abuse
ICQ: 4270107 in stock" -- Ripped from jsm
next prev parent reply other threads:[~1997-12-07 19:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-07 13:35 Louis Marascio
1997-12-07 15:26 ` Weiwen Liu
1997-12-07 15:56 ` Louis Marascio
1997-12-07 16:45 ` Jeffrey A Law
1997-12-07 17:32 ` Louis Marascio
1997-12-07 17:45 ` Jeffrey A Law
1997-12-07 17:50 ` Louis Marascio
1997-12-07 19:12 ` Robert Lipe
1997-12-07 19:22 ` Louis Marascio [this message]
1997-12-07 20:11 ` Jeffrey A Law
1997-12-07 20:17 ` Louis Marascio
1997-12-07 20:24 ` Jeffrey A Law
1997-12-07 20:32 ` Louis Marascio
1997-12-07 21:22 ` Jeffrey A Law
1997-12-08 14:35 ` Richard Henderson
1997-12-07 20:32 ` Mark Mitchell
1997-12-07 20:32 ` Louis Marascio
1997-12-07 21:02 ` Weiwen Liu
1997-12-07 21:07 ` Louis Marascio
1997-12-08 6:48 meissner
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=XFMail.971207222330.lmarasci@stevens-tech.edu \
--to=lmarasci@stevens-tech.edu \
--cc=egcs@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).