Re: C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details.
- From: "Richard B. gilbert" <rgilbert88@xxxxxxxxxxx>
- Date: Mon, 26 Mar 2007 21:24:20 -0400
XNOR wrote:
On 25 Mart, 10:53, "ThanksButNo" <no.no.tha...@xxxxxxxxx> wrote:
On Mar 24, 8:07 pm, Rich Teer <rich.t...@xxxxxxxxxxxxxx> wrote:
On Sat, 24 Mar 2007, ThanksButNo wrote:
I generally set it in /etc/profile, unless you're using csh.
That's about the worst possible place you could put it! Bascially,
you're fscking up the environment of all your users. Putting it in
your .profile is almost as bad, but at least then only your user's
environment gets FUBARed.
--
Rich Teer, SCSA, SCNA, SCSECA, OpenSolaris CAB member
Sorry -- I'm not used to running heterogeneous development
environments.
I'm used to running a homogeneous customer environment, where each and
every user on the machine is there for exactly one purpose -- to run
the one or more applications provided for them by our company.
Indeed, under such circumstance, /etc/profile is the perfect place to
put controls for where to find things. When something changes, you
only have the one file that needs to be updated.
No, our users don't change their home .profile. We don't let them.
They don't have different values for LD_LIBRARY_PATH. There's no
need.
As a matter of fact, our developers don't change their own .profile
either. None of them care to learn more Unix than is necessary to get
their job done. So I set them all up with a global environment.
Within the global /etc/profile, no one needs to worry about where
Oracle is located, or Sybase, or TeleUSE, or gcc, or any of a dozen
other utilities we use. And if I need to move Sybase to a new
location, or upgrade everyone to a new version while keeping the old
one for historical or comparison purposes, again, I only need to
update the environment in a single location.
And if I do it right, no one is the wiser. Everybody's scripts,
everybody's programs, everything works just the way it did before,
even with half the planet moved.
Yah, if I do it wrong, then I "fsck it up" for everybody. But it
doesn't take long to discover the mistake and rectify it. Somebody
will try to run something and it will fail, and I'll get an
interesting batch of e-mails and phone calls.
As I said before -- I never thought something so simple could generate
so much controversy. Sheesh.
Hello All,
I read some words in your messages that you talk about "users".
Do you use Solaris on client computers on desktops ?
I am system engineer in Turkia and using many different systems here.
Solaris is never being used as user operating system on desktops here.
Solaris is used only for Oracle, storage/backup management, backup
library management or something like that.
Is it different in your countries?
Regards
Meliksah
Solaris is used as a desktop operating system in many places. It is also, of course, used as a server operating system for Oracle, Sybase,
etc. One of my former employers used Solaris 8 and Solaris 9 on desktop X86 systems that were running a typesetting application. The business sold stationery, business cards, checks, and anything else the could print your name and address on.
.
- References:
- C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details.
- From: XNOR
- Re: C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details.
- From: Oscar del Rio
- Re: C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details.
- From: Oscar del Rio
- Re: C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details.
- From: XNOR
- Re: C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details.
- From: Oscar del Rio
- Re: C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details.
- From: XNOR
- Re: C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details.
- From: ThanksButNo
- Re: C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details.
- From: XNOR
- Re: C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details.
- From: ThanksButNo
- Re: C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details.
- From: Rich Teer
- Re: C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details.
- From: ThanksButNo
- Re: C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details.
- From: XNOR
- C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details.
- Prev by Date: Re: C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details.
- Next by Date: Re: C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details.
- Previous by thread: Re: C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details.
- Next by thread: Solaris as a desktop system (was: Re: C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details.)
- Index(es):
Relevant Pages
|