[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <4C408453-CDE5-4564-8D22-E59296F2045C@gmail.com>
Date: Mon, 9 Nov 2015 22:52:32 +0800
From: pinskia@...il.com
To: Arnd Bergmann <arnd@...db.de>
Cc: Andreas Schwab <schwab@...e.de>,
linux-arm-kernel@...ts.infradead.org,
Yury Norov <ynorov@...iumnetworks.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH v6 00/17] ILP32 for ARM64
> On Nov 9, 2015, at 10:36 PM, Arnd Bergmann <arnd@...db.de> wrote:
>
>> On Monday 09 November 2015 15:33:51 Andreas Schwab wrote:
>> Arnd Bergmann <arnd@...db.de> writes:
>>
>>>> On Monday 09 November 2015 14:23:59 Andreas Schwab wrote:
>>>> Yury Norov <ynorov@...iumnetworks.com> writes:
>>>>
>>>>> This is what I run:
>>>>> https://github.com/norov/glibc/tree/thunderx-ilp32-32time_toff_t
>>>>
>>>> That doesn't work for me:
>>>>
>>>> ../sysdeps/unix/sysv/linux/generic/sysdep.h:24:22: error: ‘__NR_llseek’ undeclar
>>>> ed (first use in this function)
>>>> ../sysdeps/unix/sysv/linux/aarch64/sysdep.h:41:32: error: ‘__NR_fcntl64’ undeclared (first use in this function)
>>>
>>> Did you re-export the kernel headers that you use as the base?
>>
>> I'm using the patched 4.3 kernel headers.
>
> Ok.
>
>> Why is <asm/bitsperlong.h> defining __BITS_PER_LONG to 64 unconditionally?
>
> It should not, that is a bug. I don't know how Yury built his glibc,
> but it can't work if __BITS_PER_LONG is wrong.
Looks like I had changed the header file manually for building glibc and Yury and myself missed that when he updated the patches.
Thanks,
Andrew
>
> Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists