public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Johannes Lorenz" <johannes89@mailueberfall.de>
To: gcc-help@gcc.gnu.org
Cc: "Andrew Haley" <aph@redhat.com>
Subject: Re: Aw: Re: How to compile gcc toolchain with special sysroot correctly?
Date: Thu, 28 Nov 2013 09:36:00 -0000	[thread overview]
Message-ID: <trinity-1064dd6c-b8da-43a0-b900-8f74cb0921e2-1385585048914@3capp-gmx-bs06> (raw)

> 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?

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? A combination of "--sysroot" and "-L" does not seem to do the job, I think.

Many thanks on advance.

-- 
Diese E-Mail wurde aus dem Sicherheitsverbund E-Mail made in
Germany versendet: http://www.gmx.net/e-mail-made-in-germany

             reply	other threads:[~2013-11-27 20:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-28  9:36 Johannes Lorenz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-12-01  8:27 Johannes Lorenz
2013-11-27 15:17 Johannes Lorenz
2013-11-27 19:10 ` Andrew Haley
2013-11-27  9:07 Johannes Lorenz
2013-11-27  9:11 ` Andrew Haley
2013-11-27 10:02   ` Aw: " Johannes Lorenz
2013-11-27 11:35     ` Andrew Haley

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=trinity-1064dd6c-b8da-43a0-b900-8f74cb0921e2-1385585048914@3capp-gmx-bs06 \
    --to=johannes89@mailueberfall.de \
    --cc=aph@redhat.com \
    --cc=gcc-help@gcc.gnu.org \
    /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).