On 02/08/2018 07:14 AM, Richard W.M. Jones wrote:
> Or when building glibc, use:
>
> ./configure --libdir=/usr/lib64 libc_cv_slibdir=/usr/lib64
> libc_cv_rtlddir=/usr/lib64
>
> which seems to be sufficent to override the default path choices,
> although maybe not completely.
This would be a m
On Thu, Feb 08, 2018 at 11:50:32AM -0800, Carlos O'Donell wrote:
> On 02/08/2018 06:51 AM, david.abdurachma...@gmail.com wrote:
> >> We could do a downstream patch.
> >
> > This would be a minimal patch based on quick look into glibc code. We
> > could force it to act as, e.g AArch64. I worry, tha
On 02/08/2018 06:51 AM, david.abdurachma...@gmail.com wrote:
>> We could do a downstream patch.
>
> This would be a minimal patch based on quick look into glibc code. We
> could force it to act as, e.g AArch64. I worry, that this would be
> custom from what is expected in RISC-V software ecosystem
On Thu, Feb 08, 2018 at 02:03:08PM +, Richard W.M. Jones wrote:
> It looks as if upstream RISC-V / glibc teams settled on some exciting
> new paths to use for libc.so.6:
>
> https://sourceware.org/ml/libc-alpha/2018-01/msg00969.html
>
> In short, on normal 64 bit hardware which is all we re
On Thu, Feb 08, 2018 at 09:08:59AM -0500, Neal Gompa wrote:
> On Thu, Feb 8, 2018 at 9:03 AM, Richard W.M. Jones wrote:
> > It looks as if upstream RISC-V / glibc teams settled on some exciting
> > new paths to use for libc.so.6:
> >
> > https://sourceware.org/ml/libc-alpha/2018-01/msg00969.html
On Thu, Feb 08, 2018 at 09:08:59AM -0500, Neal Gompa wrote:
> On Thu, Feb 8, 2018 at 9:03 AM, Richard W.M. Jones wrote:
> > It looks as if upstream RISC-V / glibc teams settled on some exciting
> > new paths to use for libc.so.6:
> >
> > https://sourceware.org/ml/libc-alpha/2018-01/msg00969.html
On Thu, Feb 8, 2018 at 9:03 AM, Richard W.M. Jones wrote:
> It looks as if upstream RISC-V / glibc teams settled on some exciting
> new paths to use for libc.so.6:
>
> https://sourceware.org/ml/libc-alpha/2018-01/msg00969.html
>
> In short, on normal 64 bit hardware which is all we really care a
It looks as if upstream RISC-V / glibc teams settled on some exciting
new paths to use for libc.so.6:
https://sourceware.org/ml/libc-alpha/2018-01/msg00969.html
In short, on normal 64 bit hardware which is all we really care about,
it'll use /lib64/lp64d/libc.so.6.
For Fedora we've settled on
