From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/13940 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Nagakamira Newsgroups: gmane.linux.lib.musl.general Subject: Re: RISC-V port upstreaming status; Alpine Linux port Date: Fri, 8 Mar 2019 01:12:11 +0900 Message-ID: References: <20190107023631.GA3370@homura.localdomain> <20190307160619.GV23599@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000002302920583835fee" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="77830"; mail-complaints-to="usenet@blaine.gmane.org" To: musl@lists.openwall.com Original-X-From: musl-return-13956-gllmg-musl=m.gmane.org@lists.openwall.com Thu Mar 07 17:12:39 2019 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.89) (envelope-from ) id 1h1vdP-000K9O-7L for gllmg-musl@m.gmane.org; Thu, 07 Mar 2019 17:12:39 +0100 Original-Received: (qmail 20031 invoked by uid 550); 7 Mar 2019 16:12:37 -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 19985 invoked from network); 7 Mar 2019 16:12:36 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=N4KbJHDLY+RJtZgT+a64RU2I0YC0YFiQ2GmBbzWp21A=; b=Vl7eZAtkAXNNJbwIzboIePsVE/3ge6mx/XmTEifUaFUkdB/c6nP7rdbB/wwWLRLtR8 nhGqCYfmzT/8/qKjHciUzgwtdi9BccRBtYuOBxi0Ph3nFJe+HnIKnSGIkbo8Uwougrva 9/ObiAL7/mz/LJYJGq0CrOia2/ViKbVOfSsNhh26T1b/QYBMQwYr7p6jT07S1C8UKZ4j NkbbqVlYVsm0i7CSSK5zJoOv1CN2jgW0KX8h5MbQKaniJ7JFeZLq0KIvzXxV90lsSpAL kaxam6b0QfjKf7DDeDckJwj68EvJKgmx/0KQ0rgm9fBJkqUKmv5IyTX9Ui12Ay5QfLQ7 78KA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=N4KbJHDLY+RJtZgT+a64RU2I0YC0YFiQ2GmBbzWp21A=; b=Z407BYFCkQvAeDlF8b9RIQrdmNjHUzSIAbK94l6mIXR1hDA4AZhHXz3jBZ6IuIM0ks hdaVjZtwqS8AYB+b9fI8egS2IqvNg3rYjOOgejFdrjEcX/fbCigU1vAG0E+KyVG47tJK bpRq8ur0y4cSdehk38WEB0NP/7V8X/Oe3D0shT65+WGdrPVr9w9IWc9Hqa9BaCZRCaHt BIypc0i+E3np8/IWhrmMo16ySBBjsavRQKrAxxHeQ2gXcYXL7g1Uu6zU8ME5WEgY6mp5 Brfb+dqdN14rOuDgSsLG0uDWsF/Ufb+L8+P8x0AAX7ATyaHjJWRgdBPlVmF7/lHVgNkf mL4Q== X-Gm-Message-State: APjAAAVkx0NJD53ASzHEjD6ddXks+uJJWUe3upjUI88GCm/yxtZ6RUcP AdP0cUgZvX4R4ZhzUysMt5paqow2+oMmDrfpzrYSXw== X-Google-Smtp-Source: APXvYqxalB1xN1Uj9Aqweu3yODwj3HoXNvcWtM1WiioZr7yldYnJAVFTHuAYEe17bWAuaBkCbnP5avsQ9Ag6r72bPmk= X-Received: by 2002:aca:6046:: with SMTP id u67mr5181342oib.84.1551975143636; Thu, 07 Mar 2019 08:12:23 -0800 (PST) In-Reply-To: <20190307160619.GV23599@brightrain.aerifal.cx> Xref: news.gmane.org gmane.linux.lib.musl.general:13940 Archived-At: --0000000000002302920583835fee Content-Type: text/plain; charset="UTF-8" fix riscv32 because every dynamically linked program says: Not found. Statically linked programs work nice! On Fri, Mar 8, 2019, 01:06 Rich Felker wrote: > On Sun, Jan 06, 2019 at 09:36:31PM -0500, Drew DeVault wrote: > > Hiya folks! I'm a big fan of musl and I've been picking up the work to > > add RISC-V support while I work on porting Alpine Linux to RISC-V. > > I'm basing my work on the last patch we saw on this list, which is also > > mirrored here: > > > > https://github.com/riscv/riscv-musl > > > > I'm pretty confident in the port after writing 3 additional patches > > (some of which address feedback from the previous discussion on this > > list) and integrating another I found sitting on GitHub. You can see all > > four new patches here: > > > > https://github.com/riscv/riscv-musl/pulls > > > > I have a working self-hosted Alpine Linux system based on this port. The > > state of the Alpine port is summarized here: > > > > https://lists.alpinelinux.org/alpine-devel/6377.html > > > > I tried to get in touch with those who put in the intial footwork for > > this port, but haven't been entirely successful so far (and those who > > have responded said they were not able to commit any more time to the > > effort). I'm happy to volunteer to integrate upstream feedback on the > > patchset and take over any additional work necessary to complete the > > upstreaming of the port. What are the next steps? > > > > Thanks for everyone's hard work on this project! > > I just posted a followup on https://github.com/riscv/riscv-musl/pull/1 > -- right now, things are not in a good state for merging due to mess > with the generic fcntl.h. I'm working through the PRs and commits > there to see if things otherwise look okay now. > > Rich > --0000000000002302920583835fee Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
fix riscv32 because every dynamically linked program says= : Not found. Statically linked programs work nice!

On Fri, Mar 8, 2019, 01:0= 6 Rich Felker <dalias@libc.org>= ; wrote:
On Sun, Jan 06, 2019 at 09= :36:31PM -0500, Drew DeVault wrote:
> Hiya folks! I'm a big fan of musl and I've been picking up the= work to
> add RISC-V support while I work on porting Alpine Linux to RISC-V.
> I'm basing my work on the last patch we saw on this list, which is= also
> mirrored here:
>
> https://github.com/riscv/riscv-musl
>
> I'm pretty confident in the port after writing 3 additional patche= s
> (some of which address feedback from the previous discussion on this > list) and integrating another I found sitting on GitHub. You can see a= ll
> four new patches here:
>
> https://github.com/riscv/riscv-musl/pulls
>
> I have a working self-hosted Alpine Linux system based on this port. T= he
> state of the Alpine port is summarized here:
>
> https://lists.alpinelinux.org/= alpine-devel/6377.html
>
> I tried to get in touch with those who put in the intial footwork for<= br> > this port, but haven't been entirely successful so far (and those = who
> have responded said they were not able to commit any more time to the<= br> > effort). I'm happy to volunteer to integrate upstream feedback on = the
> patchset and take over any additional work necessary to complete the > upstreaming of the port. What are the next steps?
>
> Thanks for everyone's hard work on this project!

I just posted a followup on https://github.com/= riscv/riscv-musl/pull/1
-- right now, things are not in a good state for merging due to mess
with the generic fcntl.h. I'm working through the PRs and commits
there to see if things otherwise look okay now.

Rich
--0000000000002302920583835fee--