public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: Johannes Lorenz <johannes89@mailueberfall.de>
Cc: gcc-help@gcc.gnu.org
Subject: Re:
Date: Thu, 28 Nov 2013 10:30:00 -0000	[thread overview]
Message-ID: <52970E9D.6040305@redhat.com> (raw)
In-Reply-To: <trinity-20d6279f-4e28-4ae0-9933-b45cc20447c8-1385584973099@3capp-gmx-bs06>

On 11/27/2013 08:42 PM, Johannes Lorenz wrote:
>> I didn't say that you should compile a new glibc.  I assumed that was
>> your goal.  It is an eccentric thing to be doing.
> 
> Ok, so one possibility would be to use a new gcc + ld on an old
> glibc, correct?

Yes.  I'd use the system's binutils if they work.

> What would be the correct way to do that? If a library is found in
> the local installation, it was from our gcc (e.g.:
> ~/local/lib/gcc...), so we use it, but if it was not found, get it
> from the system, i.e. /usr/lib. The same for the headers. How to
> tell gcc to behave like that?

That's what it does by default.  Just configure, build, and install
GCC, and programs will use its libraries.  You might need to use
ldconfig to configure the system to use the new libaries, but this
needs to be done with great care.  It's better to set a default
LD_LIBRARY_PATH.

Andrew.

       reply	other threads:[~2013-11-28  9:36 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <trinity-20d6279f-4e28-4ae0-9933-b45cc20447c8-1385584973099@3capp-gmx-bs06>
2013-11-28 10:30 ` Andrew Haley [this message]
2024-03-26  6:15 Jerress Mejado
2024-03-26  7:37 ` Jonathan Wakely
  -- strict thread matches above, loose matches on Subject: below --
2024-03-01 22:26 Sunandha Sunandha
2024-03-02  8:37 ` Jonathan Wakely
2023-09-03  9:27 Adminn
2023-09-02  6:37 Nathan
2023-09-03  8:15 ` Jonathan Wakely
2023-09-03 10:13   ` Re: Jonathan Wakely
2023-07-17  2:46 Budi
2023-07-17  3:40 ` Xi Ruoyao
2023-07-17  7:23   ` Re: Jonathan Wakely
2023-04-04  3:13 Sanniddha Chakrabarti
2023-04-04  8:59 ` Jonathan Wakely
2023-04-04  9:13   ` Re: Sanniddha Chakrabarti
2023-01-13  2:32 Re: father.dominic
2022-12-04  8:48 hongjie wu
2022-12-04 13:07 ` Jonathan Wakely
     [not found] <7879ed669a3b4fedb95df2ba8608dbc4@auswideservices.net>
2022-10-13  0:50 ` Development - AuswideServices
2022-01-10 12:03 Manuel Lauss
2022-01-10 12:10 ` Jonathan Wakely
2022-01-10 12:12   ` Re: Manuel Lauss
2022-01-10 12:15     ` Re: Jonathan Wakely
2021-10-05  7:38 Jyothi Pattamshetty
2021-10-05  7:57 ` Jonathan Wakely
2020-10-05 18:16 Jennie Pabuaya
2020-10-05 18:41 ` Dan Kegel
2020-06-04 17:07 Rajat Dahiya
2020-06-04 22:04 ` Jim Wilson
     [not found] <CAM=QvqcYCATx8uWeMPJrh=Zgt6OMFYwy04n_w4uDe9K-a7oHGw@mail.gmail.com>
2012-12-04  7:14 ` Fwd: dhinesh someone
2012-12-04  7:40   ` Ian Lance Taylor
2011-12-07  1:26 Re: Daniel Rangel
2011-12-03 17:12 Re: Daniel Rangel
2011-11-14  0:59 Re: none none
2011-11-09 17:43 Re: none none
2011-10-01 18:07 Re: none none
2011-06-07  0:37 Re: none none
2006-12-07 19:12 Re: ravandale
2006-02-22  5:21 Re: Cora T. Baez
2004-12-11  3:38 Re: Валентина Брониславовна
2004-12-11  3:38 Re: Валентина Брониславовна
2004-11-29  4:39 Re: Лора Устиновна
2004-11-29  4:39 Re: Лора Устиновна
     [not found] <20040913111103.77851.qmail@web52901.mail.yahoo.com>
2004-09-13 11:20 ` Re: Ron Michael Khu
2004-09-14  3:43   ` Re: zippo
2004-09-14 15:25 ` Re: Ron Michael Khu
     [not found] <200304071521.h37FLUg6026247@smtp-relay-2.adobe.com>
2003-04-07 15:41 ` Re: John 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=52970E9D.6040305@redhat.com \
    --to=aph@redhat.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=johannes89@mailueberfall.de \
    /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).