All of lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: Romain Naour <romain.naour@smile.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/uclibc: disable SSP support for riscv32
Date: Sat, 15 Aug 2026 21:21:51 +0200	[thread overview]
Message-ID: <aoC8T910-K9DIofo@waldemar-brodkorb.de> (raw)
In-Reply-To: <20260815121004.2036403-1-romain.naour@smile.fr>

Hi Romain,
Romain Naour wrote,

> On modern 32-bit architectures like RISC-V (riscv32), legacy 32-bit
> time syscalls like __NR_gettimeofday are intentionally omitted because
> RV32 implements a strict time64-only ABI to avoid the Year 2038 bug.
> 
> But uclibc-ng code [1] is using a direct __NR_gettimeofday syscall that
> is not defined for riscv32.
> 
> [1] https://github.com/wbx-github/uclibc-ng/blob/ae4a98f9612c7050b1bceb9c8340fe5ef9345e22/ldso/include/dl-syscall.h#L263
> 
> As a workaround, we have to disable the SSP support for uclibc-ng
> toolchain on riscv32 for now.

Thanks for your patch.

I would rather like to fix it inside uClibc-ng like suggested here:
https://lists.buildroot.org/pipermail/buildroot/2026-August/807581.html
https://mailman.openadk.org/mailman3/hyperkitty/list/devel@uclibc-ng.org/thread/WIKMWPXJYAPTVVZ2MMZINUJNPIJXBMOE/

best regards
 Waldemar
 
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-08-15 19:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-15 12:10 [Buildroot] [PATCH] package/uclibc: disable SSP support for riscv32 Romain Naour via buildroot
2026-08-15 19:21 ` Waldemar Brodkorb [this message]
2026-08-15 20:25   ` Romain Naour via buildroot

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=aoC8T910-K9DIofo@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --cc=buildroot@buildroot.org \
    --cc=romain.naour@smile.fr \
    --cc=thomas.petazzoni@bootlin.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.