public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: "Carlos O'Donell" <carlos@systemhalted.org>
To: Bill Cunningham <bill.cu1234@gmail.com>
Cc: libc-help <libc-help@sourceware.org>
Subject: Re: gcc and glibc problems
Date: Mon, 31 Jan 2022 10:31:37 -0500	[thread overview]
Message-ID: <CAE2sS1jmF7Tt+35qWksto4eWw=X5A8wkSiZ-7TL6NFVENeatKw@mail.gmail.com> (raw)
In-Reply-To: <aad8a52f-f858-bbc0-bd21-99dd397db353@gmail.com>

On Tue, Jan 25, 2022 at 10:23 PM Bill Cunningham via Libc-help
<libc-help@sourceware.org> wrote:
> I compiled a new gcc from my system gcc and glibc. Now to link a new gcc
> and the glibc. I have not attached any copies of errors and will try to
> explain the problems and will attach copies if necessary.

You need to use a sysroot to do this reliably:
https://sourceware.org/glibc/wiki/Testing/Builds#Compile_against_glibc_in_an_installed_location

Cheers,
Carlos.

      reply	other threads:[~2022-01-31 15:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26  3:23 Bill Cunningham
2022-01-31 15:31 ` Carlos O'Donell [this message]

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='CAE2sS1jmF7Tt+35qWksto4eWw=X5A8wkSiZ-7TL6NFVENeatKw@mail.gmail.com' \
    --to=carlos@systemhalted.org \
    --cc=bill.cu1234@gmail.com \
    --cc=libc-help@sourceware.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).