public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: "Andreas K. Huettel" <dilfridge@gentoo.org>
Cc: libc-alpha@sourceware.org,  Jan Henrik Weinstock <jan@mwa.re>,
	Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: Re: [PATCH v3] Always define __USE_TIME_BITS64 when 64 bit time_t is used
Date: Mon, 29 Jan 2024 17:40:34 +0100	[thread overview]
Message-ID: <87o7d4drel.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <2445957.jE0xQCEvom@pinacolada> (Andreas K. Huettel's message of "Sat, 27 Jan 2024 14:54:35 +0100")

* Andreas K. Huettel:

> When rebuilding a riscv32 qemu chroot with this patch I get errors similar to
>
> (python)
> ceval.c:(.text+0x272a): undefined reference to `__pthread_cond_timedwait64'
> collect2: error: ld returned 1 exit status
>
> (gnupg)
> /usr/lib/gcc/riscv32-unknown-linux-gnu/13/../../../../riscv32-unknown-linux-gnu/bin/ld: /usr/lib32/ilp32d/libnpth.so: undefined reference to `__pthread_mutex_timedlock64'

This could happen if you build against a mixed of old and new headers.
(Old headers which check __USE_TIME_BITS64, but a new header that
defines __USE_TIME_BITS64 because the architecture has time64.)

Thanks,
Florian


  parent reply	other threads:[~2024-01-29 16:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 13:18 Adhemerval Zanella
2024-01-27 13:54 ` Andreas K. Huettel
2024-01-29 16:29   ` Adhemerval Zanella Netto
2024-01-29 16:37     ` Andreas K. Huettel
2024-01-29 16:40   ` Florian Weimer [this message]
2024-01-31 12:34 ` Jonathan Wakely
2024-01-31 17:48   ` Adhemerval Zanella Netto
2024-03-15  2:23 ` DJ Delorie

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=87o7d4drel.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=dilfridge@gentoo.org \
    --cc=jan@mwa.re \
    --cc=libc-alpha@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).