From: Jeffrey Walton <noloader@gmail.com>
To: musl@lists.openwall.com
Subject: Re: [musl] Release prep for 1.2.1, and afterwards
Date: Wed, 24 Jun 2020 18:39:17 -0400 [thread overview]
Message-ID: <CAH8yC8k8gGoQGsB-Nth6B34pxcT2VYNW6U4vhk3AwjS+-rWzVA@mail.gmail.com> (raw)
In-Reply-To: <20200624204243.GL6430@brightrain.aerifal.cx>
On Wed, Jun 24, 2020 at 4:58 PM Rich Felker <dalias@libc.org> wrote:
>
> I'm about to do last work of merging mallocng, followed soon by
> release. Is there anything in the way of overlooked bug reports or
> patches that should still be addressed in this release cycle?
>
> Things I'm aware of:
>
> - "Proposal to match behaviour of gethostbyname to glibc". Latest
> patch is probably ok, but could be deferred to after release.
>
> - nsz's new sqrt{,f,l}. I'm hesitant to do all three right away
> without time to test, but replacing sqrtl.c could be appropriate
> since the current one is badly broken on archs with ld wider than
> double. However it would need to accept ld80 in order not to be
> build-breaking on m68k, or m68k would need an alternative.
>
> and some more with open questions or work to be done that can't be
> finished now but should be revisited after release:
>
> - fenv overhaul (sorry for dropping this, Damian)
> - PTHREAD_RWLOCK_PREFER_WRITER_NONRECURSIVE_NP
> - _SC_NPROCESSORS_{CONF,ONLN} behavior
> - hexagon port
> - rv32 port
> - arm fdpic (newly revived interest from users on list)
> - dni (dynamic linking without PT_INTERP absolute path) & related ldso
> work by rcombs
> - "lutimes: Add checks for input parameters"
It would be nice to see runpath logic loosened up a bit. That is,
don't reject multiple runpaths if one is bad.
This is needed for packages like Perl. Perls screws up rpaths and
runpaths badly. Perl does not escape origin-based paths properly when
setting them in a makefile. Worse, Perl builds makefiles on the fly,
so we cannot manually fix the makefiles after configure.
Jeff
next prev parent reply other threads:[~2020-06-24 22:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 20:42 Rich Felker
2020-06-24 22:39 ` Jeffrey Walton [this message]
2020-06-25 8:15 ` Szabolcs Nagy
2020-06-25 15:39 ` Rich Felker
2020-06-25 17:31 ` Szabolcs Nagy
2020-06-25 20:50 ` Rich Felker
2020-06-25 21:15 ` Rich Felker
2020-06-26 1:20 ` Rich Felker
2020-06-26 8:40 ` Szabolcs Nagy
2020-07-06 22:12 ` Rich Felker
2020-07-07 15:00 ` Szabolcs Nagy
2020-07-07 17:22 ` Rich Felker
2020-07-07 18:20 ` Szabolcs Nagy
2020-06-25 21:43 ` Andre McCurdy
2020-06-25 21:51 ` Rich Felker
2020-06-25 22:03 ` Andre McCurdy
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=CAH8yC8k8gGoQGsB-Nth6B34pxcT2VYNW6U4vhk3AwjS+-rWzVA@mail.gmail.com \
--to=noloader@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).