Re: gcc-12/mips64el FTBFS during sbuild chown

Jeffrey Walton <[email protected]>
Newsgroups gmane.linux.debian.ports.mips,gmane.linux.debian.devel.wb-team
Message-ID <CAH8yC8=j1BeKOTJBtFHOytZoCHW3OgE7aNPM1zSdF2YK1yx50w@mail.gmail.com>
On Fri, Oct 28, 2022 at 2:05 PM Aurelien Jarno <[email protected]> wrote:
>
> On 2022-10-28 08:59, Adrian Bunk wrote:
> > On Thu, Oct 27, 2022 at 07:50:17PM +0800, YunQiang Su wrote:
> > > YunQiang Su <[email protected]> 于2022年10月26日周三 01:56写道:
> > > >
> > > > Adrian Bunk <[email protected]> 于2022年10月25日周二 21:50写道:
> > > > >
> > > > > https://buildd.debian.org/status/logs.php?pkg=gcc-12&arch=mips64el
> > > > >
> > > > > ...
> > > > > Finished
> > > > > --------
> > > > >
> > > > > I: Built successfully
> > > > > chmod: cannot access '/<<PKGBUILDDIR>>/build/mips64el-linux-gnuabi64/libstdc++-v3/testsuite/normal3/filesystem-test.FSLTZS-last_write_time': Value too large for defined data type
> > > > > chmod: cannot access '/<<PKGBUILDDIR>>/build/mips64el-linux-gnuabi64/libstdc++-v3/testsuite/normal2/filesystem-test.5zDnmX-last_write_time': Value too large for defined data type
> > >
> > > I cannot reproduce this problem on my local machines.
> > > Can you help to try to reproduce this problem on buildd nodes?
> > >...
> >
> > Not from me, if I had a way to reproduce I would have debugged further
> > from that.
>
> I have been able to reproduce by building gcc-12 on the eller.d.o
> porterbox. It can be reduced to this simple test:
>
> (sid_mips64el-dchroot)aurel32@eller:~$ touch -d 20390101 t
> (sid_mips64el-dchroot)aurel32@eller:~$ chmod +x t
> chmod: cannot access 't': Value too large for defined data type
> (sid_mips64el-dchroot)aurel32@eller:~$
>
> It seems related to the y2038 support in either coreutils or glibc.

There's a thread going on over at debian-arm that might provide some
insight: https://lists.debian.org/debian-arm/2022/10/msg00020.html . I
don't think it will be helpful to fix this problem, however.

Jeff
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.