From: Dorian ROSSE <dorianbrice@hotmail.fr>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Abhishek Kumar <Abhishek.kumar@exaleapsemi.com>,
"libc-help@sourceware.org" <libc-help@sourceware.org>
Subject: Re: glibc with kernel-4.14 headers on riscv
Date: Wed, 1 Jun 2022 20:56:13 +0000 [thread overview]
Message-ID: <DB7P193MB0346BC59C137DB82193D79C9DADF9@DB7P193MB0346.EURP193.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <198a8b67-bc76-b781-95e1-794feb4c3d07@linaro.org>
Dear worker IT,
I wait again a good tutorial for glibc,
I need it for systemd 251,
Each time I read the documentation glibc I fall on to problems after,
Thanks you in advance for your answer (I use this system only the weekend),
Have a nice night from the France it is twenty three to four here,
Regards.
Dorian Rosse.
________________________________
From: Libc-help <libc-help-bounces+dorianbrice=hotmail.fr@sourceware.org> on behalf of Adhemerval Zanella via Libc-help <libc-help@sourceware.org>
Sent: Wednesday, June 1, 2022 9:40:37 PM
To: Abhishek Kumar <Abhishek.kumar@exaleapsemi.com>; libc-help@sourceware.org <libc-help@sourceware.org>
Subject: Re: glibc with kernel-4.14 headers on riscv
On 27/05/2022 05:54, Abhishek Kumar wrote:
>
> I want to port glibc for my custome kernel-4.14 for riscv64 but I want to get some Idea which files I need to change in glibc side so that I can start and try, please guide me.
>
Now that master does not have the kernel check, you can just use the next
2.36 release or backport to the version you want. The commits are:
b46d250656794e63a2946c481fda29271342dd1a (Remove kernel version check)
c628c2296392ed3bf2cb8d8470668e64fe53389f (elf: Remove ldconfig kernel version check)
d2db60d8d830ef68c8d20a77ac3572d610aa40b1 (Remove dl-librecon.h header.)
Although you probably would only need b46d250656794e63a2946c481fda29271342dd1a.
> Thanks
> Abhishek Kumar
> ________________________________
> From: Florian Weimer <fweimer@redhat.com>
> Sent: 27 April 2022 13:20
> To: Abhishek Kumar <Abhishek.kumar@exaleapsemi.com>
> Cc: libc-help@sourceware.org <libc-help@sourceware.org>
> Subject: Re: glibc with kernel-4.14 headers on riscv
>
> * Abhishek Kumar:
>
>> I am woking on kernel-4.14 to give support for riscv (fu540 plateform)
>> ,I am using glibc2.27 for my kernel after build the kernel when
>> booting it at boot time it is giving me error "FATAL: kernel too old",
>> so please suggest me which glibc version I should use for my
>> kernel-4.14 so that it will be compatible for riscv.
>
> Kernel support was added to mainline Linux in version 4.15, so that's
> the baseline that glibc supports. You'll either have to use a mainline
> kernel, or port glibc to the custom kernel.
>
> Thanks,
> Florian
>
> [EXT]
prev parent reply other threads:[~2022-06-01 20:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 7:11 Abhishek Kumar
2022-04-27 7:50 ` Florian Weimer
2022-04-27 18:55 ` Adhemerval Zanella
2022-05-27 8:54 ` Abhishek Kumar
2022-06-01 19:40 ` Adhemerval Zanella
2022-06-01 20:56 ` Dorian ROSSE [this message]
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=DB7P193MB0346BC59C137DB82193D79C9DADF9@DB7P193MB0346.EURP193.PROD.OUTLOOK.COM \
--to=dorianbrice@hotmail.fr \
--cc=Abhishek.kumar@exaleapsemi.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-help@sourceware.org \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).