[Bug libstdc++/88749] New: Failure while building libstdc++-v3/src/filesystem/ops.cc on trunk

[romain.geissler at amadeus dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88749

            Bug ID: 88749
           Summary: Failure while building
                    libstdc++-v3/src/filesystem/ops.cc on trunk
           Product: gcc
           Version: 9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: romain.geissler at amadeus dot com
  Target Milestone: ---

Hi,

With the latest move of libstdc++fs.so in libstdc++.so, I am seeing these new
build errors:

/workdir/src/gcc-9.0.0/libstdc++-v3/src/filesystem/ops.cc: In function 'void
std::experimental::filesystem::v1::last_write_time(const
std::experimental::filesystem::v1::path&,
std::experimental::filesystem::v1::file_time_type, std::error_code&)':

/workdir/src/gcc-9.0.0/libstdc++-v3/src/filesystem/ops.cc:913:10: error:
'utimbuf' is not a member of 'posix'; did you mean 'utimbuf'?

  913 |   posix::utimbuf times;

      |          ^~~~~~~

In file included from
/workdir/src/gcc-9.0.0/libstdc++-v3/src/filesystem/ops.cc:50,

                 from
/workdir/src/gcc-9.0.0/libstdc++-v3/src/filesystem/cow-ops.cc:26:

/home/jenkins/workspace/OTF_Toolchain_release_20.0-GWCRYYLPVAZ3GI64ZF43J2FVALYHUCNKGFBXVRTH6NJF73DCK7SQ/output/build/temporary-system/install/include/utime.h:36:8:
note: 'utimbuf' declared here

   36 | struct utimbuf

      |        ^~~~~~~

In file included from
/workdir/src/gcc-9.0.0/libstdc++-v3/src/filesystem/cow-ops.cc:26:

/workdir/src/gcc-9.0.0/libstdc++-v3/src/filesystem/ops.cc:914:3: error: 'times'
was not declared in this scope; did you mean 'time'?

  914 |   times.modtime = s.count();

      |   ^~~~~

      |   time

/workdir/src/gcc-9.0.0/libstdc++-v3/src/filesystem/ops.cc:917:14: error:
'utime' is not a member of 'posix'; did you mean 'utime'?

  917 |   if (posix::utime(p.c_str(), &times))

      |              ^~~~~



So there may need some fixes around things like _GLIBCXX_USE_UTIMENSAT or
_GLIBCXX_HAVE_UTIME_H.

Cheers,
Romain