elusive error in "make install" for Qt5-5.15.2-GCCcore-10.3.0.eb #16614
Comments
|
It seems like this problem only manifests when the build is done through the EESSI build container ( |
|
The patch from qt/qtbase@d34282d (which applies fine to Qt5 5.15.2) may reveal more information when the error occurs... |
|
Trying to build Especially since: The length of the path makes me wonder if we're hitting a magic limit of I've only seen this when using the EESSI build container, where we use Patch to reveal underlying problem: add underlying error message to errors produced by Qfile::copy;
see https://github.com/qt/qtbase/commit/d34282dba0ebe67c16c1ee6e25d85f019b48b615
and https://github.com/qt/qtbase/commit/f17648bf55c7bf5b43143bc529754ce125c60088
--- qt-everywhere-src-5.15.2/qtbase/src/corelib/io/qfile.cpp
+++ qt-everywhere-src-5.15.2/qtbase/src/corelib/io/qfile.cpp
@@ -817,7 +817,8 @@ QFile::copy(const QString &newName)
totalRead += in;
if (in != out.write(block, in)) {
close();
- d->setError(QFile::CopyError, tr("Failure to write block"));
+ d->setError(QFile::CopyError, tr("Failure to write block: %1")
+ .arg(out.errorString()));
error = true;
break;
}
@@ -837,7 +838,8 @@ QFile::copy(const QString &newName)
if (!out.rename(newName)) {
error = true;
close();
- d->setError(QFile::CopyError, tr("Cannot create %1 for output").arg(newName));
+ d->setError(QFile::CopyError, tr("Cannot create %1 for output: %2")
+ .arg(newName, out.errorString()));
}
}
#ifdef QT_NO_TEMPORARYFILE |
|
If I look into the From within the build container with the writable overlay, it's not there though: And I can create the file just fine: And then the file also looks like expected in the |
|
One more clue: the file being copied is a regular C source file, nothing special it seems: |
|
This problem doesn't present itself anymore when using an EESSI build container with more recent version of For completeness sake, some details on the local disk in the AWS VM: |
When trying to install
Qt5-5.15.2-GCCcore-10.3.0.eb, I'm running into a weird problem in the install step:I'm only seeing this on some systems, in particular VMs in AWS where
/tmpis on an NVMe block device (see also here):This same problem is also reported in various Qt bugs, see QTBUG-86592, QTBUG-63891, QTBUG-63193, but the underlying cause was never identified it seems (since the problem "just disappeared" for them)...
The text was updated successfully, but these errors were encountered: