On Sat, Mar 28, 2020 at 06:46:54PM +, Maciej W. Rozycki wrote:
>I think being software developers we are in this comfortable position
>that we can actually make changes to software ourselves if we find
>problems or usability issues...
>
>For example I found it useful on a couple of occasions t
Snapshot gcc-9-20200328 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/9-20200328/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 9 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
On Fri, 27 Mar 2020, Jeff Law via Gcc wrote:
> As an ex IT guy, I've gone both directions depending on the project I was
> supporting and certainly see the pros and cons of going highly customized vs
> as
> generic as possible. In my opinion Chris & Frank are doing the right thing
> here
> and
On Sat, 28 Mar 2020 11:35:36 +0100
Andreas Schwab wrote:
> On Mär 28 2020, Sergei Trofimovich via Gcc wrote:
>
> > x86_64-linux-musl targets do not support multilib layout as-is
> > and usually expects libdir=lib. glibc target usually uses libdir=lib64.
>
> If x86_64-linux-musl doesn't suppor
On Mär 28 2020, Sergei Trofimovich via Gcc wrote:
> x86_64-linux-musl targets do not support multilib layout as-is
> and usually expects libdir=lib. glibc target usually uses libdir=lib64.
If x86_64-linux-musl doesn't support multilib then it should not use
i386/t-linux64 as tmake_file.
Andreas.
x86_64-linux-musl targets do not support multilib layout as-is
and usually expects libdir=lib. glibc target usually uses libdir=lib64.
In https://bugs.gentoo.org/675954 (also touched on https://gcc.gnu.org/PR90077)
Gentoo discovered the following discrepancy when gcc is built with
--disable-multi
