|
From: | Paul Eggert |
Subject: | Re: Testing gnulib on riscv64 - replacement modules |
Date: | Fri, 9 Mar 2018 12:28:53 -0800 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 |
On 03/08/2018 01:19 AM, Richard W.M. Jones wrote:
$ (cd gllib; ls -1 $(${GNULIB_CHECKOUT}/posix-modules | sed -e 's|-posix$||' | sort -u | grep -v 'nonblocking' | sed -e 's|$|.o|') 2>/dev/null ) fclose.o ..."if so, this indicates problems in the libc."So I suppose there is a problem with glibc. We're running glibc 2.27 (from Fedora Rawhide). What could be the problem?
You can look at the build log and Gnulib source to get an idea. For example, for fclose.o, gnulib/modules/fclose suggests that REPLACE_FCLOSE seems to be 1, and gnulib/m4/fclose.m4 says that it is 1 if either gl_cv_func_fflush_stdin ends in "yes" or if REPLACE_CLOSE is 1, and your log says "checking whether fflush works on input streams... no" so it sounds like this is the problem. Look in gnulib/m4/fflush.m4 to find the program that failed.
Similarly for the other .o files. Good luck.
[Prev in Thread] | Current Thread | [Next in Thread] |