public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: lrtaylor@micron.com
To: <janvier_anonical@yahoo.com>, <gcc-help@gcc.gnu.org>
Subject: RE: Two gcc Installations: conflict in library?
Date: Tue, 24 Aug 2004 18:27:00 -0000	[thread overview]
Message-ID: <363801FFD7B74240A329CEC3F7FE4CC40309610B@ntxboimbx07.micron.com> (raw)

Mostly likely, when you compile, the new libraries and headers will get
picked up.  However, depending on how your LD_LIBRARY_PATH (or
ld.so.conf on Linux) is set up, you may not get the right libraries - it
will depend on whether /usr/lib is search before /usr/local/lib.  I
would suspect that /usr/local/lib is searched first, but it just depends
on how your system is set up.

Thanks,
Lyle

-----Original Message-----
From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org] On
Behalf Of Janvier D. Anonical
Sent: Monday, August 23, 2004 11:23 PM
To: gcc-help@gcc.gnu.org
Subject: Two gcc Installations: conflict in library?

Hello!

Currently, my gcc (3.3.3) is installed in /usr. I have installed a new
gcc (3.4.1) in /usr/local. Now, whenever I do 'gcc --version' the
compiler being used is the new one (3.4.1). My questions is this. Which
header files (e.g., stdio.h, iostream, etc.) and libraries (e.g.,
libstdc++, libgcc, etc.) lib will be used by default? Is it the one in
/usr/local or the one in /usr?

Thanks!


=====
Last night as I lay in bed looking
      at the stars I thought:
  'Where the hell is ceiling?'

________________________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping" 
your friends today! Download Messenger Now 
http://uk.messenger.yahoo.com/download/index.html

             reply	other threads:[~2004-08-24 16:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24 18:27 lrtaylor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-24 10:47 Janvier D. Anonical
2004-08-24 10:54 ` Eljay Love-Jensen

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=363801FFD7B74240A329CEC3F7FE4CC40309610B@ntxboimbx07.micron.com \
    --to=lrtaylor@micron.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=janvier_anonical@yahoo.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).