From: Petr Vorel <petr.vorel@gmail.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Buildroot Mailing List <buildroot@buildroot.org>
Subject: Re: [Buildroot] [autobuild.buildroot.net] Your daily results for 2022-05-08
Date: Sun, 15 May 2022 15:56:45 +0200 [thread overview]
Message-ID: <YoEGnYusX1F5m+dK@pevik> (raw)
In-Reply-To: <CAPi7W81H7JAbL=8FGa3v0jFHyikEMStnpzApBt222JmZm1P60w@mail.gmail.com>
Hi Fabrice,
> Hi Petr,
> Le dim. 15 mai 2022 à 07:48, Petr Vorel <petr.vorel@gmail.com> a écrit :
> > Hi all,
> > > Autobuilder failures
> > > ====================
> > > arch | reason | url
> > > -------------+--------------------------------+---------------------------------------------------------------------------------
> > > mips64 | ltp-testsuite-20220121 | http://autobuild.buildroot.net/results/2dafec94b888960335115b44c281741dfd55840b
> > this uclibc 1.0.40 based toolchain is not able to detect fstatat() via configure, but
> > it's available:
> > configure:6615: checking for fstatat
> > configure:6615: buildroot/output/host/bin/mips64-buildroot-linux-uclibc-gcc -o conftest -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Os -g0 -Ibuildroot/output/host/bin/../mips64-buildroot-linux-uclibc/sysroot/usr/include/tirpc -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE conftest.c -Lbuildroot/output/host/bin/../mips64-buildroot-linux-uclibc/sysroot/usr/lib -ltirpc -lfts >&5
> > buildroot/output/host/lib/gcc/mips64-buildroot-linux-uclibc/10.3.0/../../../../mips64-buildroot-linux-uclibc/bin/ld: /tmp/ccFw53nU.o: in function `main':
> > conftest.c:(.text.startup+0x10): undefined reference to `fstatat'
> > buildroot/output/host/lib/gcc/mips64-buildroot-linux-uclibc/10.3.0/../../../../mips64-buildroot-linux-uclibc/bin/ld: conftest.c:(.text.startup+0x18): undefined reference to `fstatat'
> > But even if I change include/config.h to
> > - /* #undef HAVE_FSTATAT */
> > +#define HAVE_FSTATAT 1
> > it fails to build:
> > output/build/ltp-testsuite-20220121/testcases/kernel/syscalls/fstatat/fstatat01.c:100: undefined reference to `fstatat'
> > That's strange, isn't it a bug in the toolchain?
> > Or is it really LTP bug? What would be missing then? If yes, it'd be nice to fix
> > it before upcoming LTP release (2 weeks).
> I dig into this issue a while ago without finding a solution. Here is
> what I found.
> First the build failure is only raised with uclibc-ng on mips64.
> Secondly, fstatat is defined as extern if __USE_FILE_OFFSET64 is not
> defined [1] however its implementation is protected by "ifdef
> __NR_fstatat64" [2]
> __NR_fstatat64 is defined by:
> #if __WORDSIZE == 64 && defined __NR_newfstatat
> # define __NR_fstatat64 __NR_newfstatat
> #endif
> So, for an unknown reason, I assume that __NR_newfstatat is not defined.
> In this case, uclibc-ng doesn't define any fallback [3] resulting in
> the build failure.
Thanks for confirming that it's bug/issue on uclibc-ng on mips64.
It'd be worth to at least report it to them.
Kind regards,
Petr
> > Kind regards,
> > Petr
> Best Regards,
> Fabrice
> [1] https://github.com/wbx-github/uclibc-ng/blob/ab1dd83bec59c9e65c31efd6e887182948f627be/include/sys/stat.h#L241
> [2] https://github.com/wbx-github/uclibc-ng/blob/ab1dd83bec59c9e65c31efd6e887182948f627be/libc/sysdeps/linux/common/fstatat.c#L18
> [3] https://github.com/wbx-github/uclibc-ng/blob/ab1dd83bec59c9e65c31efd6e887182948f627be/libc/sysdeps/linux/common/fstatat.c#L34
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-05-15 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <62789f76.1c69fb81.8311.5ad0SMTPIN_ADDED_MISSING@mx.google.com>
2022-05-15 5:48 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2022-05-08 Petr Vorel
2022-05-15 10:51 ` Fabrice Fontaine
2022-05-15 13:56 ` Petr Vorel [this message]
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=YoEGnYusX1F5m+dK@pevik \
--to=petr.vorel@gmail.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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