From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/13084 Path: news.gmane.org!.POSTED!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: musl "Linux-dependencies" info [was Re: [musl] Timeline for 1.1.20?] Date: Sun, 29 Jul 2018 11:49:53 -0400 Message-ID: <20180729154953.GA1392@brightrain.aerifal.cx> References: <20180716172023.GM1392@brightrain.aerifal.cx> <9155e3b7-6bbc-e9cc-331a-9514d18023c0@landley.net> <20180728195537.GZ1392@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: blaine.gmane.org 1532879283 26398 195.159.176.226 (29 Jul 2018 15:48:03 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 29 Jul 2018 15:48:03 +0000 (UTC) User-Agent: Mutt/1.5.21 (2010-09-15) To: musl@lists.openwall.com Original-X-From: musl-return-13100-gllmg-musl=m.gmane.org@lists.openwall.com Sun Jul 29 17:47:59 2018 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1fjnvL-0006m1-90 for gllmg-musl@m.gmane.org; Sun, 29 Jul 2018 17:47:59 +0200 Original-Received: (qmail 10171 invoked by uid 550); 29 Jul 2018 15:50:07 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 10119 invoked from network); 29 Jul 2018 15:50:06 -0000 Content-Disposition: inline In-Reply-To: Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:13084 Archived-At: On Sun, Jul 29, 2018 at 07:40:25AM -0400, Christopher Friedt wrote: > On Sat, Jul 28, 2018 at 3:55 PM Rich Felker wrote: > > Yes, but I don't know how to set it up, and any proper approach to > > setting it up really shouldn't require the project maintainer to know > > how, since it should revolve around a separate CI project pulling > > musl, libc-test, and possibly other sources (e.g. mcm) as either > > subrepos or part of the build scripts, then evaluating the resutls. > > I'll set up a .gitlab-ci.yml file - likely will use one 'pipelilne' to > trigger other pipelines that exercise all combinations here: > > https://github.com/richfelker/musl-cross-make#supported-targets > > Speaking of which, one of my eventual use-cases is an rtos that uses > the same syscall numbers as linux for each arch. Originally I was > using bionic libc, but it's just difficult to maintain a permanent > fork. Beyond syscall numbers, is there any specific reason that musl > requires linux? The other "Linux" interfaces it uses are parts of /proc (needed for filling in gaps of some syscalls' functionality), some netlink functionality (for network interface enumeration interfaces), and some ioctls (for determining if something is a tty, some socket operations, etc.). There are also some de facto standard pathnames used for configuration (resolv.conf, passwd, etc.) on top of the standard ones specified by POSIX (/dev/null, etc.). Some details are in the (incomplete, outdated, but IMO very good on what it does have) musl documentation: https://www.musl-libc.org/manual.html Rich