From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Richard Bump <Richard_Bump@hotmail.com>,
"libc-help@sourceware.org" <libc-help@sourceware.org>
Subject: Re: glibc for the MAC M1
Date: Tue, 10 Oct 2023 11:52:28 -0300 [thread overview]
Message-ID: <76141f98-a977-487d-bf46-a4805a168597@linaro.org> (raw)
In-Reply-To: <3584DF47-6C33-4FD1-B2E2-3F8D1F4A4ECF@hotmail.com>
On 10/10/23 10:53, Richard Bump via Libc-help wrote:
> I receive this error when attempting to configure and install glibc-2.38:
> configure: error:
>
> *** The GNU C library is currently unavailable for this platform.
>
> *** If you are interested in seeing glibc on this platform visit
>
> *** the "How to submit a new port" in the wiki:
>
> *** https://sourceware.org/glibc/wiki/#Development
>
> *** and join the community!
>
>
> I am not a developer as far as I know, just a user trying to get Jupyterlab to run my NodeJS kernel which it has done for years on my previous MACs. I do remember installing glibc on my intel MACs to get various programs to run. I have dabbled in the C language, but I am not a C or C++ developer or programmer, so, although I have reviewed your contents for a port submission, frankly I’m clueless.
>
>
> Any suggestions or help would be appreciated. Thank you.
The glibc currently only supports Linux and GNU Hurd. It is highly unlikely
that you have installed glibc on an Intel MACs. The macOS/darwin has a
complete different libc implementation, so you will need to check if
Jupyterlab has support for it and follow the instructions to install and
run on macOS/darwin.
next prev parent reply other threads:[~2023-10-10 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 13:53 Richard Bump
2023-10-10 14:52 ` Adhemerval Zanella Netto [this message]
2023-10-14 14:14 ` Christer Solskogen
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=76141f98-a977-487d-bf46-a4805a168597@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=Richard_Bump@hotmail.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).