public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <andreas.huettel@ur.de>
To: Carlos O'Donell <carlos@redhat.com>,
	libc-alpha <libc-alpha@sourceware.org>
Cc: Xi Ruoyao <xry111@xry111.site>
Subject: Re: Monday Patch Queue Review update (2024-01-29)
Date: Mon, 29 Jan 2024 17:41:01 +0100	[thread overview]
Message-ID: <4474598.kQq0lBPeGt@kona> (raw)
In-Reply-To: <a207c58acb8abbfad516a069b7fa11c9cdc21591.camel@xry111.site>

[-- Attachment #1: Type: text/plain, Size: 2194 bytes --]

Am Montag, 29. Januar 2024, 17:35:33 CET schrieb Xi Ruoyao:
> On Mon, 2024-01-29 at 23:54 +0800, Xi Ruoyao wrote:
> > On Mon, 2024-01-29 at 09:49 -0500, Carlos O'Donell wrote:
> > >  * Andreas: Added loongarch failures. There are a lot of them.
> > >  * Carlos: I wouldn't hold up the release for the failures seen on one
> > > specific Loongarch system e.g. gcc401.
> > 
> > These seem caused by the Debian-specific "multiarch" directory layout:
> > 
> > xry111@gcc401:~/git-repos/glibc-build$ make test t=misc/tst-gettid-kill
> > (... ...)
> > libgcc_s.so.1 must be installed for pthread_cancel to work
> > make[2]: Leaving directory '/home/xry111/git-repos/glibc/misc'
> > FAIL: misc/tst-gettid-kill
> > original exit status 1
> > Didn't expect signal from child: got `Aborted'
> > 
> > libgcc_s.so.1 is in the "multiarch directory" /usr/lib/loongarch64-
> > linux-gnu.  With --libdir=/usr/lib/loongarch64-linux-gnu and
> > libc_cv_slibdir=/usr/lib/loongarch64-linux-gnu this test passes.

Ah. I see.

> > 
> > Now running make check -j32...
> 
> Only one test failure with those:

OK thanks a lot, much better.

> FAIL: misc/tst-glibcsyscalls
> original exit status 1
> info: glibc syscall 'cachestat' not known to kernel
> info: glibc syscall 'futex_requeue' not known to kernel
> info: glibc syscall 'fchmodat2' not known to kernel
> info: glibc syscall 'futex_wake' not known to kernel
> info: glibc syscall 'map_shadow_stack' not known to kernel
> info: glibc syscall 'futex_wait' not known to kernel
> error: kernel syscall 'fstat' (80) not known to glibc
> error: kernel syscall 'newfstatat' (79) not known to glibc
> info: glibc tables are based on kernel version 6.7
> info: installed kernel headers are version 6.4
> 
> I suppose there is something wrong with Debian-shipped kernel headers
> (Debian on LoongArch is still WIP).

That's also a 6.1 kernel on the machine, so ancient for loong ...

> 
> 


-- 
PD Dr. Andreas K. Huettel
Institute for Experimental and Applied Physics
University of Regensburg
93040 Regensburg
Germany

tel. +49 151 241 67748 (mobile)
tel. +49 941 943 1618 (office)
e-mail andreas.huettel@ur.de
https://www.akhuettel.de/
https://www.akhuettel.de/group/

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29 14:49 Carlos O'Donell
2024-01-29 15:54 ` Xi Ruoyao
2024-01-29 16:35   ` Xi Ruoyao
2024-01-29 16:41     ` Andreas K. Huettel [this message]
2024-01-29 17:47       ` Xi Ruoyao

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=4474598.kQq0lBPeGt@kona \
    --to=andreas.huettel@ur.de \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=xry111@xry111.site \
    /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).