#1002699 libc6: m68k,s390 readdir not returning filled in dirent pointer

Package:
src:glibc
Source:
glibc
Submitter:
Camm Maguire
Date:
2022-01-28 16:48:03 UTC
Severity:
normal
Tags:
#1002699#5
Date:
2021-12-27 17:49:46 UTC
From:
To:
With a file "configure" in the current directory, the following fails
(only in the autobuilder) on m68k and s390.

=============================================================================

#include <dirent.h>
#include <string.h>

int main() {
  struct dirent *d;
  DIR *r=opendir("./");

  for (;(d=readdir(r)) && strcmp("configure",d->d_name););
  return d && d->d_type==DT_REG ? 0 : -1;
}
=============================================================================
#1002699#10
Date:
2021-12-28 18:20:52 UTC
From:
To:
Correction, that is current autobuilders on 68k and sh4.

Take care,

Camm Maguire <camm@debian.org> writes:
#1002699#15
Date:
2021-12-28 18:52:00 UTC
From:
To:
Hello Camm!

That's a known issue, see [1]. I will patch the glibc packages for m68k
and sh4 again to address this issue.

Adrian
#1002699#20
Date:
2021-12-29 09:50:32 UTC
From:
To:
Hi Camm!

I have uploaded patched versions of glibc for m68k and sh4 and blocked the
autobuild for glibc on the buildds.

You may want to merge the bug with the existing bug report [1] and adjust the
severity to normal.

Adrian
#1002699#39
Date:
2021-12-30 19:33:01 UTC
From:
To:
severity 1002699 normal
merge 1002699 916276
thanks

Thank you so much!

John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> writes:
#1002699#48
Date:
2021-12-30 20:18:06 UTC
From:
To:
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> writes:

Greetings!  I think you meant blocked autobuild for gcl....  In any
case, after a delay, gcl just attempted autobuild on sh4 and failed the
same way.

Take care,
#1002699#53
Date:
2021-12-30 21:05:42 UTC
From:
To:
Hello!

No, I didn't. I meant glibc such that the autobuilders are not building the
glibc package without the patches I mentioned.

Well, on sh4, it failed with linker errors. Seems to be a different problem then
what I previously assumed. Not sure what the problem is then.

Adrian
#1002699#58
Date:
2021-12-30 21:36:15 UTC
From:
To:
The buildd hasn't picked up the updated glibc package yet [1]:

I will regenerate the chroots.

Adrian
#1002699#63
Date:
2021-12-31 15:14:01 UTC
From:
To:
Greetings!

John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> writes:

OK, thanks!  Assuing the patches are now installed...

... this is the exact same failure.  The code in question compiles .c files
discovered by a call to lisp #'directory which in turn loops over
readdir.  It found no files to compile, hence the undefined symbols.
You can also look at the d_type configure test earlier in the build,
which returns "no".  Suggestions?

Take care,
#1002699#68
Date:
2022-01-28 14:48:57 UTC
From:
To:
Greetings, and once again, thanks for all you do for Debian!  No rush on
this item at all, needless to say.

Problem persists.  What package versions should I watch for to see that
the fix has been installed?

Take care,

John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> writes:
#1002699#73
Date:
2022-01-28 16:45:11 UTC
From:
To:
Hello Camm!

If the current package versions don't address this issue, it's a different bug
and needs to be reported against qemu or glibc.

Adrian