public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/26209] Compiling Glibc-2.11.1 on Raspberrypi4 fails as config.guess returns armv7l unknown
Date: Mon, 06 Jul 2020 18:04:05 +0000 [thread overview]
Message-ID: <bug-26209-131-jlZKyjrXGm@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26209-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26209
Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |adhemerval.zanella at linaro dot o
| |rg
--- Comment #3 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
(In reply to Rob Hookham from comment #2)
> (In reply to Andreas Schwab from comment #1)
> > Before 2.17, armv7l was part of the ports repository.
>
> I am not sure I understand, are you telling me that I cannot compile this if
> I specify a Kernel below 2.17 ?
>
> If so as I am trying to fix an embedded linux system that has no compiler
> and has glibc 2.11.1 that is damaged. (It does howver have a compatible arm
> processor.)
>
> I thought that if I compile for a later kernel will it will be rejected by
> the embedded system.
>
> Maybe I am misssing something simple here ?
> Rgaqrds
> Rob
What Andreas noted is arm used to be part of glibc-ports [1] before its
inclusing on generic tree on glibc 2.17. The ports used be a add-on on glibc,
so you need to check out this on the glibc tree and use the --enable-add-ons to
enable it.
[1] git://sourceware.org/git/glibc-ports.git
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-07-06 18:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 15:52 [Bug libc/26209] New: " rh100605 at aol dot com
2020-07-06 17:13 ` [Bug libc/26209] " schwab@linux-m68k.org
2020-07-06 17:49 ` rh100605 at aol dot com
2020-07-06 18:04 ` adhemerval.zanella at linaro dot org [this message]
2020-07-06 21:10 ` rh100605 at aol dot com
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=bug-26209-131-jlZKyjrXGm@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).