mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Shiz <hi@shiz.me>
To: musl@lists.openwall.com
Cc: alx.manpages@gmail.com
Subject: Re: [musl] [PATCH] memmem.3: Added list of known systems where this is available
Date: Wed, 23 Nov 2022 16:33:21 +0100	[thread overview]
Message-ID: <227F5B23-D17F-4675-B9CF-52BB5E4B7F34@shiz.me> (raw)
In-Reply-To: <50485f46-99d0-69ee-0882-7e403334080c@gmail.com>

Hi there,

> On 23 Nov Reiwa 4, at 14:16, Alejandro Colomar <alx.manpages@gmail.com> wrote:
> 
>>>> -  Android is not a real Unix system, in that you can't even program in C in
>>>> there, unless you're Google or have hacked your system.  It's not friendly
>>>> to us programmers, so we don't need to be friendly to it.  I don't want to
>>>> be cluttering the pages with information that is irrelevant to normal users.
>>> 
>>> I'm assuming bionic is being used in some of the Android free
>>> alternatives too, but then I'm not sure how usable for programming those
>>> are either. And, well musl libc is not a real Unix system you can program
>>> against either. :)
> 
> The difference is only that bionic is not in use in useful systems (AFAIK).  :)
> 
> So we have to do some decission here (and also about newlib, as reported by Brian).

I’d like to chime in here and note that, valuations of usefulness aside, it *is*
possible to develop in C against an Android device, without needing any hacks,
using the NDK[1]. As someone who has occasionally worked on big codebases written
in C and C++ for Android devices, I would argue there’s value to be had there. :-)

> Cheers,
> 
> Alex

- Shiz

[1]: https://developer.android.com/ndk

  parent reply	other threads:[~2022-11-23 15:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221110001318.10696-1-andrew@digital-domain.net>
     [not found] ` <853fa349-8e78-8ce8-f76f-79b4b9353913@gmail.com>
     [not found]   ` <Y31XOPOsB932l0cd@thunder.hadrons.org>
     [not found]     ` <CACKs7VAQsxDc2XrsAYSEbA9eqRnLHuXykVmNTit+tCFMyGLCwA@mail.gmail.com>
2022-11-23 13:16       ` [musl] " Alejandro Colomar
2022-11-23 14:55         ` Jeffrey Walton
2022-11-23 15:11           ` Alejandro Colomar
2022-11-23 15:33         ` Shiz [this message]
2022-11-30 19:39           ` [musl] " enh
2022-12-09 20:25             ` Alejandro Colomar
2022-11-24 18:57         ` [musl] " Stefan Puiu
2022-12-11 16:30           ` Alejandro Colomar

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=227F5B23-D17F-4675-B9CF-52BB5E4B7F34@shiz.me \
    --to=hi@shiz.me \
    --cc=alx.manpages@gmail.com \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).