Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 24 Jun 2020 18:39:17 -0400
From: Jeffrey Walton <>
Subject: Re: Release prep for 1.2.1, and afterwards

On Wed, Jun 24, 2020 at 4:58 PM Rich Felker <> 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)
> - 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.


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.